On Mon, Jun 08, 2015 at 01:53:52PM -0400, Haines Brown wrote: > I hosed a USB key, probably by pulling it out while files still being > copied to it. I'd like to recover the files. > > Dmesg: > ... > [6990701.755708] sd 23:0:0:0: [sdc] Attached SCSI removable disk > [6990702.003269] EXT3-fs (sdc1): error: unrecognized mount option > "gid=100" or missing value > > Mount: > # mount -o gid=users -t ext3 /dev/sdc1 /media > mount: wrong fs type, bad option, bad superblock on /dev/sdc1, etc. The "unrecognised mount option" could be a symptom of the invalid file system. If the filesystem isn't (valid) ext3, then you can't supply ext3 options to it. > > > syslog: > > usb 3-1.5: new high-speed USB device number 23 using ehci_hcd > usb 3-1.5: New USB device found, idVendor=0951, idProduct=1666 > ... > mtp-probe: checking bus 3, device 23: "/sys/devices/pci0000:00/ \ > 0000:00:1a.0/usb3/3-1/3-1.5" > mtp-probe: bus: 3, device: 23 was not an MTP device > ... > sd 18:0:0:0: [sdc] Write Protect is off > kernel: [6988616.449126] sd 18:0:0:0: [sdc] Mode Sense: 23 00 00 00 > sd 18:0:0:0: [sdc] No Caching mode page found > kernel: [6988616.449717] sd 18:0:0:0: [sdc] Assuming drive cache: > write through > > FDISK: > # fdisk -l /dev/sda1 > Disk /dev/sdc1: 7862 MB, 7862452224 bytes > 243 heads, 62 sectors/track, 1019 cylinders, total 15356352 > sectors > Units = sectors of 1 * 512 = 512 bytes > Sector size (logical/physical): 512 bytes / 512 bytes > I/O size (minimum/optimal): 512 bytes / 512 bytes > Disk identifier: 0x00000000 > > Disk /dev/sdc1 doesn't contain a valid partition table You probably wanted to fdisk /dev/sdc. > > > Replace superblock: > > # mkfs.ext3 -n /dev/sdc1 > ... > Superblock backups stored on blocks: > 32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632 > > # fsck.ext3 -yb 98304 /dev/sdc1 >> /home/haines/mkfs > /dev/sdc1 was not cleanly unmounted, check forced. > ... > Pass 5: Checking group summary information > Free blocks count wrong for group #0 (31781, counted=26187). > Fix? yes > Free blocks count wrong for group #1 (31787, counted=25642). > Fix? yes > ... > Free inodes count wrong for group #58 (8144, counted=8023). > Fix? yes > Directories count wrong for group #58 (0, counted=11). > Fix? yes > > But nothing fixed. Dmesg returns same error. Does wrong value for gid > indicate bad superblock or something else? Nothing fixed? What does a second fsck (perhaps on the main superblock) yield? The same errors (in which case yes, nothing was fixed and perhaps your device is read-only), different errors (in which case your device is probably fatally broken) or no errors? > > Haines Brown > > > -- > To UNSUBSCRIBE, email to debian-user-REQUEST@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org > Archive: [🔎] 20150608175352.GB23142@engels.historicalmaterialism.info">https://lists.debian.org/[🔎] 20150608175352.GB23142@engels.historicalmaterialism.info > -- For more information, please reread.
Attachment:
signature.asc
Description: Digital signature