Re: crash
- From: "gypsy3001@xxxxxxxxx" <gypsy3001@xxxxxxxxx>
- Date: 24 Jul 2006 20:56:39 -0700
Try looking in the log. That should reveal the device names (sda1, sda2,
...) of the partitions and of course the entire drive. You could then
try mounting or fsck'ing them to try to fix the errors or extract the
data.
Thanks for the tip, I put the drive back into the USB enclosure and
connected to my Ubuntu notebook through the USB port. I looked at the
syslog and retrieved the following messages. Ubuntu seem to recognize
hardware just fine through SCSI emulation at sda. However, it tried to
mount it as a FAT file system. I suspect the drive is formated as ext3
under Linux. But mounting it or running fsck on it as ext3 doesn't
work. Not sure if it is because the SCSI emulation is hiding the drive
behind a FAT translation service. Any ideas?
-----
chieh@porta:~$ fsck.ext3 -n sda
e2fsck 1.38 (30-Jun-2005)
fsck.ext3: No such file or directory while trying to open sda
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate
superblock:
e2fsck -b 8193 <device>
-----
Jul 24 20:33:05 localhost kernel: [4295532.549000] usb 1-1: new full
speed USB device using uhci_hcd and address 2
Jul 24 20:33:08 localhost kernel: [4295535.400000] SCSI subsystem
initialized
Jul 24 20:33:08 localhost kernel: [4295535.471000] Initializing USB
Mass Storage driver...
Jul 24 20:33:08 localhost kernel: [4295535.508000] scsi0 : SCSI
emulation for USB Mass Storage devices
Jul 24 20:33:08 localhost kernel: [4295535.637000] usb-storage: device
found at 2
Jul 24 20:33:08 localhost kernel: [4295535.637000] usb-storage: waiting
for device to settle before scanning
Jul 24 20:33:08 localhost kernel: [4295535.638000] usbcore: registered
new driver usb-storage
Jul 24 20:33:08 localhost kernel: [4295535.638000] USB Mass Storage
support registered.
Jul 24 20:33:08 localhost usb.agent[6917]: usb-storage: loaded
successfully
Jul 24 20:33:13 localhost kernel: [4295540.641000] Vendor: WDC WD12
Model: 00JB-00DUA3 Rev: 75.1
Jul 24 20:33:13 localhost kernel: [4295540.642000] Type:
Direct-Access ANSI SCSI revision: 00
Jul 24 20:33:13 localhost kernel: [4295540.779000] usb-storage: device
scan complete
Jul 24 20:33:14 localhost kernel: [4295541.362000] SCSI device sda:
234441648 512-byte hdwr sectors (120034 MB)
Jul 24 20:33:14 localhost kernel: [4295541.362000] sda: assuming drive
cache: write through
Jul 24 20:33:14 localhost kernel: [4295541.427000] SCSI device sda:
234441648 512-byte hdwr sectors (120034 MB)
Jul 24 20:33:14 localhost kernel: [4295541.427000] sda: assuming drive
cache: write through
Jul 24 20:33:14 localhost kernel: [4295541.427000]
/dev/scsi/host0/bus0/target0/lun0: p1 p2 < p5 >
Jul 24 20:33:14 localhost kernel: [4295541.630000] Attached scsi disk
sda at scsi0, channel 0, id 0, lun 0
Jul 24 20:33:14 localhost scsi.agent[6984]: sd_mod: loaded
sucessfully (for disk)
Jul 24 20:33:20 localhost kernel: [4295547.882000] FAT: utf8 is not a
recommended IO charset for FAT filesystems, filesystem will be case
sensitive!
Jul 24 20:33:20 localhost kernel: [4295547.895000] FAT: Did not find
valid FSINFO signature.
Jul 24 20:33:20 localhost kernel: [4295547.895000] Found
signature1 0x00000000 signature2 0x00000000 (sector = 1)
Jul 24 20:33:21 localhost kernel: [4295548.230000] FAT: Filesystem
panic (dev sda1)
Jul 24 20:33:21 localhost kernel: [4295548.230000] invalid access
to FAT (entry 0x00c0000a)
Jul 24 20:33:21 localhost kernel: [4295548.231000] File system has
been set read-only
Chieh
--
Camera Hacker - http://www.CameraHacker.com/
.
- Prev by Date: Re: crash
- Next by Date: Re: usb-storage and ub, data damaged
- Previous by thread: Re: crash
- Next by thread: How to set regional options
- Index(es):
Relevant Pages
|
