Re: Wheezy - External HDD Not Mounting
Hello again, and thanks again Camaleón for responding.
> On Wed, Oct 12, 2011 at 1:26 PM, Camaleón <noelamac@gmail.com> wrote:
> >
> > On Wed, 12 Oct 2011 12:57:15 -0400, k s wrote:
> >
> > The one i am having a problem with is the WD My Book, also using a NTFS
> > filesystem, and has AC Power. It holds 2TB. I just wanted to say that
> > again because my syslog may be mentioning both.
>
> NTFS also? Then run an complete scan disk and defrag from a windows
> machine.
As stated earlier, i do not use Windows, and don't own a Windows box.
However, i do use the NTFS Filesystem on certain disks as there are
devices i use which will only read from NTFS or FAT, and from those
choices NTFS is optimal.
Moving forward with this... I unplugged all of my other external USB
hard drives, and completely shut down my computer.
I booted back into Wheezy, inserted the problematic USB Hard Drive and
Nautilus popped up with the contents open for me to explore.
As soon as i tried to open a folder through Nautilus, the window
closed and no errors were given.
dmesg gave me this -
[ 2367.212026] usb 1-1: new high speed USB device number 4 using ehci_hcd
[ 2367.909457] usb 1-1: New USB device found, idVendor=1058, idProduct=1130
[ 2367.909463] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2367.909467] usb 1-1: Product: My Book 1130
[ 2367.909471] usb 1-1: Manufacturer: Western Digital
[ 2367.909474] usb 1-1: SerialNumber: 5743415A4138383736343733
[ 2368.187556] usbcore: registered new interface driver uas
[ 2368.201946] Initializing USB Mass Storage driver...
[ 2368.202173] scsi4 : usb-storage 1-1:1.0
[ 2368.202364] usbcore: registered new interface driver usb-storage
[ 2368.202369] USB Mass Storage support registered.
[ 2369.201116] scsi 4:0:0:0: Direct-Access WD My Book 1130
1012 PQ: 0 ANSI: 6
[ 2369.201855] scsi 4:0:0:1: Enclosure WD SES Device
1012 PQ: 0 ANSI: 6
[ 2369.254705] sd 4:0:0:0: Attached scsi generic sg3 type 0
[ 2369.255276] scsi 4:0:0:1: Attached scsi generic sg4 type 13
[ 2382.450611] sd 4:0:0:0: [sdc] 3906963456 512-byte logical blocks:
(2.00 TB/1.81 TiB)
[ 2382.451097] sd 4:0:0:0: [sdc] Write Protect is off
[ 2382.451102] sd 4:0:0:0: [sdc] Mode Sense: 47 00 10 08
[ 2382.451596] sd 4:0:0:0: [sdc] No Caching mode page present
[ 2382.451602] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[ 2382.453719] sd 4:0:0:0: [sdc] No Caching mode page present
[ 2382.453724] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[ 2382.470253] sdc: sdc1
[ 2382.474851] sd 4:0:0:0: [sdc] No Caching mode page present
[ 2382.474858] sd 4:0:0:0: [sdc] Assuming drive cache: write through
[ 2382.474863] sd 4:0:0:0: [sdc] Attached SCSI disk
[ 2382.552376] ses 4:0:0:1: Attached Enclosure device
[ 2446.660037] usb 1-1: reset high speed USB device number 4 using ehci_hcd
[ 2461.772031] usb 1-1: device descriptor read/64, error -110
[ 2476.988028] usb 1-1: device descriptor read/64, error -110
[ 2477.204072] usb 1-1: reset high speed USB device number 4 using ehci_hcd
[ 2477.340272] usb 1-1: USB disconnect, device number 4
[ 2477.340290] sd 4:0:0:0: Device offlined - not ready after error recovery
[ 2477.340308] sd 4:0:0:0: [sdc] Unhandled error code
[ 2477.340313] sd 4:0:0:0: [sdc] Result: hostbyte=DID_ERROR
driverbyte=DRIVER_OK
[ 2477.340319] sd 4:0:0:0: [sdc] CDB: Read(10): 28 00 00 60 16 80 00 00 08 00
[ 2477.340336] end_request: I/O error, dev sdc, sector 6297216
[ 2477.340345] Buffer I/O error on device sdc1, logical block 786896
[ 2477.340400] sd 4:0:0:0: [sdc] Unhandled error code
[ 2477.340404] sd 4:0:0:0: [sdc] Result: hostbyte=DID_NO_CONNECT
driverbyte=DRIVER_OK
[ 2477.340410] sd 4:0:0:0: [sdc] CDB: Read(10): 28 00 00 60 16 90 00 00 50 00
[ 2477.340425] end_request: I/O error, dev sdc, sector 6297232
[ 2477.340431] Buffer I/O error on device sdc1, logical block 786898
[ 2477.340438] Buffer I/O error on device sdc1, logical block 786899
[ 2477.340444] Buffer I/O error on device sdc1, logical block 786900
[ 2477.340450] Buffer I/O error on device sdc1, logical block 786901
[ 2477.340456] Buffer I/O error on device sdc1, logical block 786902
[ 2477.340461] Buffer I/O error on device sdc1, logical block 786903
[ 2477.340468] Buffer I/O error on device sdc1, logical block 786904
[ 2477.340474] Buffer I/O error on device sdc1, logical block 786905
[ 2477.340480] Buffer I/O error on device sdc1, logical block 786906
[ 2478.484033] usb 1-1: new high speed USB device number 5 using ehci_hcd
[ 2479.181497] usb 1-1: New USB device found, idVendor=1058, idProduct=1130
[ 2479.181504] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2479.181508] usb 1-1: Product: My Book 1130
[ 2479.181511] usb 1-1: Manufacturer: Western Digital
[ 2479.181514] usb 1-1: SerialNumber: 5743415A4138383736343733
[ 2479.182194] scsi5 : usb-storage 1-1:1.0
[ 2482.340920] scsi 5:0:0:0: Direct-Access WD My Book 1130
1012 PQ: 0 ANSI: 6
[ 2482.341648] scsi 5:0:0:1: Enclosure WD SES Device
1012 PQ: 0 ANSI: 6
[ 2482.386528] sd 5:0:0:0: Attached scsi generic sg3 type 0
[ 2482.386758] ses 5:0:0:1: Attached Enclosure device
[ 2482.387115] ses 5:0:0:1: Attached scsi generic sg4 type 13
[ 2482.389164] ses 5:0:0:1: Failed to get diagnostic page 0x8000002
[ 2482.389175] ses 5:0:0:1: Failed to bind enclosure -19
[ 2482.390150] sd 5:0:0:0: [sdc] Test WP failed, assume Write Enabled
[ 2482.391145] sd 5:0:0:0: [sdc] Asking for cache data failed
[ 2482.391151] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[ 2482.398267] sd 5:0:0:0: [sdc] Test WP failed, assume Write Enabled
[ 2482.399271] sd 5:0:0:0: [sdc] Asking for cache data failed
[ 2482.399280] sd 5:0:0:0: [sdc] Assuming drive cache: write through
[ 2482.399287] sd 5:0:0:0: [sdc] Attached SCSI disk
A little worried, i took the drive to a friend's house & plugged it
into his Windows machine...
& all worked well. I even COPIED all 500Gigs off the drive in the
event that it might fail.
It's been plugged into his machine, which was shut down and booted up
three times in the last few hours and there have been no issues.
lol, so sad. Wish Microsoft would make it easier to work with NTFS.
Has anyone had any similar issues? Or found a way to get around this?
Is this a bug i should file?
Again, any and all help is greatly appreciated.
Best,
shuttah
Reply to: