Re: [gentoo-user] repair FAT-fs
On 03/02/2018 11:01 PM, Grant Taylor wrote: > On 03/02/2018 10:34 PM, the...@sys-concept.com wrote: >> No, my system is not recognizing "sdb" > > Hum. :-/ > > Your original dmesg output showed that the kernel detected sdb. > > What does lsblk (?) show? > > Does your system detect USB flash drives properly? (USB Mass Storage) I think, I got confused by those messages. Maybe the message I was getting: FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. was referring to another an earlier device :-/ I re-install a new firmware on that android tv box and it installed OK now. And I was afraid that I bricked that TV "T95Z plus" device. But it works now.
Re: [gentoo-user] repair FAT-fs
On 03/02/2018 10:24 PM, Grant Taylor wrote: > On 03/02/2018 10:17 PM, the...@sys-concept.com wrote: >> I've tried: >> fsck.vfat -v -a -w /dev/sdb1 >> fsck.fat 4.0 (2016-05-06) >> open: No such file or directory >> >> This doesn't work either: >> fdisk /dev/sdb >> >> Welcome to fdisk (util-linux 2.28.2). >> Changes will remain in memory only, until you decide to write them. >> Be careful before using the write command. >> >> fdisk: cannot open /dev/sdb: No such file or directory > > I think that the "No such file or directory" is quite literally telling > you that you don't have a /dev/sdb (device) file. > > Please try "ls -l /dev/sd*" > > I'm sort of guessing that you're missing the device nodes. Without > them, fsck and fdisk won't be able to work. When I mount standard usb the nodes are detected: ls -l /dev/sd* brw-rw 1 root disk 8, 0 Dec 31 17:20 /dev/sda brw-rw 1 root disk 8, 1 Dec 31 17:20 /dev/sda1 brw-rw 1 root disk 8, 2 Dec 31 17:20 /dev/sda2 brw-rw 1 root disk 8, 3 Dec 31 17:20 /dev/sda3 brw-rw 1 root disk 8, 4 Dec 31 17:20 /dev/sda4 brw-rw 1 root disk 8, 5 Dec 31 17:20 /dev/sda5 brw-rw 1 root disk 8, 16 Mar 2 22:46 /dev/sdb brw-rw 1 root disk 8, 17 Mar 2 22:46 /dev/sdb1 But the TV Box (T95Z Plus) is not recognized and dmesg is only showing: [10936422.554836] usb 3-2: new high-speed USB device number 23 using ehci-pci [10936422.676557] usb 3-2: New USB device found, idVendor=1b8e, idProduct=c003 [10936422.676559] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Re: [gentoo-user] repair FAT-fs
On 03/02/2018 10:34 PM, the...@sys-concept.com wrote: No, my system is not recognizing "sdb" Hum. :-/ Your original dmesg output showed that the kernel detected sdb. What does lsblk (?) show? Does your system detect USB flash drives properly? (USB Mass Storage) -- Grant. . . . unix || die
Re: [gentoo-user] repair FAT-fs
On 03/02/2018 10:24 PM, Grant Taylor wrote: > On 03/02/2018 10:17 PM, the...@sys-concept.com wrote: >> I've tried: >> fsck.vfat -v -a -w /dev/sdb1 >> fsck.fat 4.0 (2016-05-06) >> open: No such file or directory >> >> This doesn't work either: >> fdisk /dev/sdb >> >> Welcome to fdisk (util-linux 2.28.2). >> Changes will remain in memory only, until you decide to write them. >> Be careful before using the write command. >> >> fdisk: cannot open /dev/sdb: No such file or directory > > I think that the "No such file or directory" is quite literally telling > you that you don't have a /dev/sdb (device) file. > > Please try "ls -l /dev/sd*" > > I'm sort of guessing that you're missing the device nodes. Without > them, fsck and fdisk won't be able to work. On my other system I'm getting from "dmesg" [ 82.144011] usb 1-1: new high-speed USB device number 3 using ehci-pci [ 82.265345] usb 1-1: New USB device found, idVendor=1b8e, idProduct=c003 [ 82.265348] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Re: [gentoo-user] repair FAT-fs
On 03/02/2018 10:24 PM, Grant Taylor wrote: > On 03/02/2018 10:17 PM, the...@sys-concept.com wrote: >> I've tried: >> fsck.vfat -v -a -w /dev/sdb1 >> fsck.fat 4.0 (2016-05-06) >> open: No such file or directory >> >> This doesn't work either: >> fdisk /dev/sdb >> >> Welcome to fdisk (util-linux 2.28.2). >> Changes will remain in memory only, until you decide to write them. >> Be careful before using the write command. >> >> fdisk: cannot open /dev/sdb: No such file or directory > > I think that the "No such file or directory" is quite literally telling > you that you don't have a /dev/sdb (device) file. > > Please try "ls -l /dev/sd*" > > I'm sort of guessing that you're missing the device nodes. Without > them, fsck and fdisk won't be able to work. No, my system is not recognizing "sdb" ls -l /dev/sd* brw-rw 1 root disk 8, 0 Dec 31 17:20 /dev/sda brw-rw 1 root disk 8, 1 Dec 31 17:20 /dev/sda1 brw-rw 1 root disk 8, 2 Dec 31 17:20 /dev/sda2 brw-rw 1 root disk 8, 3 Dec 31 17:20 /dev/sda3 brw-rw 1 root disk 8, 4 Dec 31 17:20 /dev/sda4 brw-rw 1 root disk 8, 5 Dec 31 17:20 /dev/sda5 I've try to connect that box to another system and same thing: ls -l /dev/sd* brw-rw 1 root disk 8, 0 Mar 2 22:31 /dev/sda brw-rw 1 root disk 8, 1 Mar 2 22:31 /dev/sda1 brw-rw 1 root disk 8, 2 Mar 2 22:31 /dev/sda2 brw-rw 1 root disk 8, 3 Mar 2 22:31 /dev/sda3 brw-rw 1 root disk 8, 4 Mar 2 22:31 /dev/sda4
Re: [gentoo-user] repair FAT-fs
On 03/02/2018 10:17 PM, the...@sys-concept.com wrote: I've tried: fsck.vfat -v -a -w /dev/sdb1 fsck.fat 4.0 (2016-05-06) open: No such file or directory This doesn't work either: fdisk /dev/sdb Welcome to fdisk (util-linux 2.28.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. fdisk: cannot open /dev/sdb: No such file or directory I think that the "No such file or directory" is quite literally telling you that you don't have a /dev/sdb (device) file. Please try "ls -l /dev/sd*" I'm sort of guessing that you're missing the device nodes. Without them, fsck and fdisk won't be able to work. -- Grant. . . . unix || die
Re: [gentoo-user] repair FAT-fs
On 03/02/2018 09:40 PM, Paul Colquhoun wrote: > On Saturday, 3 March 2018 3:24:32 PM AEDT the...@sys-concept.com wrote: >> I've an android TV box (T95Z Plus) that has a corrupted File System. >> dmes is showing : >> >> usb-storage 8-1:1.0: USB Mass Storage device detected >> scsi host8: usb-storage 8-1:1.0 >> scsi 8:0:0:0: Direct-Access Kingston DataTraveler G3 PMAP PQ: 0 ANSI: 4 >> sd 8:0:0:0: Attached scsi generic sg2 type 0 >> sd 8:0:0:0: [sdb] 30489408 512-byte logical blocks: (15.6 GB/14.5 GiB) >> sd 8:0:0:0: [sdb] Write Protect is off >> sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 >> sd 8:0:0:0: [sdb] No Caching mode page found >> sd 8:0:0:0: [sdb] Assuming drive cache: write through >> sdb: sdb1 >> sd 8:0:0:0: [sdb] Attached SCSI removable disk >> FAT-fs (sdb1): Volume was not properly unmounted. Some data may be >> corrupt. Please run fsck. >> >> I 've "dosfstools" installed but I can not run: dosfsck - it doesn't exist. > > > Try 'fsck.vfat' instead. There is also 'fsck.fat' or 'fsck.exfat', at least > on my installation. I've tried: fsck.vfat -v -a -w /dev/sdb1 fsck.fat 4.0 (2016-05-06) open: No such file or directory This doesn't work either: fdisk /dev/sdb Welcome to fdisk (util-linux 2.28.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. fdisk: cannot open /dev/sdb: No such file or directory Here is a dmesg: [10930879.950647] usb-storage 8-1:1.0: USB Mass Storage device detected [10930879.950742] scsi host8: usb-storage 8-1:1.0 [10930881.068652] scsi 8:0:0:0: Direct-Access Kingston DataTraveler G3 PMAP PQ: 0 ANSI: 4 [10930881.068839] sd 8:0:0:0: Attached scsi generic sg2 type 0 [10930882.544966] sd 8:0:0:0: [sdb] 30489408 512-byte logical blocks: (15.6 GB/14.5 GiB) [10930882.545153] sd 8:0:0:0: [sdb] Write Protect is off [10930882.545155] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 [10930882.545283] sd 8:0:0:0: [sdb] No Caching mode page found [10930882.545284] sd 8:0:0:0: [sdb] Assuming drive cache: write through [10930882.567263] sdb: sdb1 [10930882.568351] sd 8:0:0:0: [sdb] Attached SCSI removable disk [10930887.640395] FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. [10930894.488038] sd 8:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE [10930894.488041] sd 8:0:0:0: [sdb] tag#0 Sense Key : Hardware Error [current] [10930894.488043] sd 8:0:0:0: [sdb] tag#0 Add. Sense: No additional sense information [10930894.488045] sd 8:0:0:0: [sdb] tag#0 CDB: Synchronize Cache(10) 35 00 00 00 00 00 00 00 00 00 [10930894.497472] usb 8-1: USB disconnect, device number 106 [10932073.936844] usb 3-1: USB disconnect, device number 19 [10932092.353300] usb 3-1: new high-speed USB device number 20 using ehci-pci [10932092.473483] usb 3-1: New USB device found, idVendor=1043, idProduct=8012 [10932092.473486] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [10932092.473487] usb 3-1: Product: Flash Disk [10932092.473488] usb 3-1: Manufacturer: Generic -- Thelma
Re: [gentoo-user] repair FAT-fs
On Saturday, 3 March 2018 3:24:32 PM AEDT the...@sys-concept.com wrote: > I've an android TV box (T95Z Plus) that has a corrupted File System. > dmes is showing : > > usb-storage 8-1:1.0: USB Mass Storage device detected > scsi host8: usb-storage 8-1:1.0 > scsi 8:0:0:0: Direct-Access Kingston DataTraveler G3 PMAP PQ: 0 ANSI: 4 > sd 8:0:0:0: Attached scsi generic sg2 type 0 > sd 8:0:0:0: [sdb] 30489408 512-byte logical blocks: (15.6 GB/14.5 GiB) > sd 8:0:0:0: [sdb] Write Protect is off > sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 > sd 8:0:0:0: [sdb] No Caching mode page found > sd 8:0:0:0: [sdb] Assuming drive cache: write through > sdb: sdb1 > sd 8:0:0:0: [sdb] Attached SCSI removable disk > FAT-fs (sdb1): Volume was not properly unmounted. Some data may be > corrupt. Please run fsck. > > I 've "dosfstools" installed but I can not run: dosfsck - it doesn't exist. Try 'fsck.vfat' instead. There is also 'fsck.fat' or 'fsck.exfat', at least on my installation. -- Reverend Paul Colquhoun, ULC. http://andor.dropbear.id.au/ Asking for technical help in newsgroups? Read this first: http://catb.org/~esr/faqs/smart-questions.html#intro
[gentoo-user] repair FAT-fs
I've an android TV box (T95Z Plus) that has a corrupted File System. dmes is showing : usb-storage 8-1:1.0: USB Mass Storage device detected scsi host8: usb-storage 8-1:1.0 scsi 8:0:0:0: Direct-Access Kingston DataTraveler G3 PMAP PQ: 0 ANSI: 4 sd 8:0:0:0: Attached scsi generic sg2 type 0 sd 8:0:0:0: [sdb] 30489408 512-byte logical blocks: (15.6 GB/14.5 GiB) sd 8:0:0:0: [sdb] Write Protect is off sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00 sd 8:0:0:0: [sdb] No Caching mode page found sd 8:0:0:0: [sdb] Assuming drive cache: write through sdb: sdb1 sd 8:0:0:0: [sdb] Attached SCSI removable disk FAT-fs (sdb1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck. I 've "dosfstools" installed but I can not run: dosfsck - it doesn't exist. -- Thelma
