@Andrey and linuxdev, thanks for the tips.
The SD card is in ext4 format. I have a host PC pretty much doing nothing but to flash the DTB for TX2. It doesn’t come with SD reader, so I plug the SD into a USB3 card reader.
Here are the output for some commands on the host PC.
‘sudo lsblk -l’
sdb 8:16 1 29.5G 0 disk
sdb1 8:17 1 29.5G 0 part
sr0 11:0 1 1024M 0 rom
sda 8:0 0 232.9G 0 disk
sda2 8:2 0 1K 0 part
sda5 8:5 0 7.9G 0 part [SWAP]
sda1 8:1 0 225G 0 part /
‘sudo e2fsck /dev/sdb1’ (took a few minutes to respond)
e2fsck 1.42.13 (17-May-2015)
/dev/sdb1: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? yes
e2fsck: unable to set superblock flags on /dev/sdb1
/dev/sdb1: ********** WARNING: Filesystem still has errors **********
‘sudo fsck.ext4 /dev/sdb1’ (similar result as to ‘e2fsck’)
e2fsck 1.42.13 (17-May-2015)
/dev/sdb1: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? yes
fsck.ext4: unable to set superblock flags on /dev/sdb1
/dev/sdb1: ********** WARNING: Filesystem still has errors **********
The ‘gdisk’ command, however gives some interesting report. I don’t know how to decipher it though.
‘sudo gdisk -l /dev/sdb’
GPT fdisk (gdisk) version 1.0.1
Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present
***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************
Warning! Secondary partition table overlaps the last partition by
33 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/sdb: 61896704 sectors, 29.5 GiB
Logical sector size: 512 bytes
Disk identifier (GUID): C9E1BD58-1391-4ED3-AFC6-787226044014
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 61896670
Partitions will be aligned on 2048-sector boundaries
Total free space is 8158 sectors (4.0 MiB)
Number Start (sector) End (sector) Size Code Name
1 8192 61896703 29.5 GiB 0700 Microsoft basic data
Looks like I have to give up, doesn’t it?
P.S.
Here are the ‘dmesg --follow’ output (pretty much repeating the same message)
[ 1495.382862] sd 6:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 1495.382866] sd 6:0:0:0: [sdb] tag#0 Sense Key : Hardware Error [current]
[ 1495.382868] sd 6:0:0:0: [sdb] tag#0 Add. Sense: No additional sense information
[ 1495.382871] sd 6:0:0:0: [sdb] tag#0 CDB: Write(10) 2a 00 01 c4 20 00 00 00 08 00
[ 1495.382873] blk_update_request: I/O error, dev sdb, sector 29630464
[ 1495.382879] Buffer I/O error on dev sdb1, logical block 3702784, lost async page write
[ 1495.424934] VFS: Dirty inode writeback failed for block device sdb1 (err=-5).
[ 1546.822406] sdb: sdb1