[gentoo-user] USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[gentoo-user] USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Fatih Tümen]

Hi,

When I ran eix hdf command, all of a sudden my usb drive started
making weird noises. I only have ccache, distfiles and packaes
directories on sda2, the usb disk partition. I don't know why eix
waked up the disk. Eix hung there non-responding for a moment as the
disk kept making noises, so I interrupted the task. Immediately
checked the logs[0] and umounted the device as a reflex.

The time 20:38 in [0] corresponds to the time I issues eix. There was
nothing in the logs for 8 minutes. The last operation I had on the
disk was fetching kde updates which finished at about 19:00.

I wanted to fsck the device and got:
# fsck.ext3 -pvf /dev/sda2
fsck.ext3: Attempt to read block from filesystem resulted in short
read while trying to open /dev/sda2
Could this be a zero-length partition?

fdisk -l was not showing the device anymore. I could not mounted it back.

Googling the subject brought some unsolved threads so far. There were
some similar issues, one with ext4, one with ipod. But in all those
cases they still had their device alive whereas I seem to completely
lost it. Here is what smartmontools says:

# smartctl -d /dev/sda
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

=======> INVALID ARGUMENT TO -d: /dev/sda
=======> VALID ARGUMENTS ARE: ata, scsi, marvell, sat, 3ware,N,
hpt,L/M/N cciss,N <=======

Use smartctl -h to get a usage summary

21:08:23 | log # smartctl -a /dev/sda
smartctl version 5.38 [i686-pc-linux-gnu] Copyright (C) 2002-8 Bruce Allen
Home page is http://smartmontools.sourceforge.net/

Device: WD        Version: 1.02
>> Terminate command early due to bad response to IEC mode page
A mandatory SMART command failed: exiting. To continue, add one or
more '-T permissive' options.
21:08:31 | log # fdisk /dev/sda

Unable to read /dev/sda
21:14:33 | log # ll /dev/sda
brw-rw---- 1 root disk 8, 0 Oct  9 21:14 /dev/sda

I tried to plug it in a ubuntu box on a different machine, the result was same.
And this is the messages I get upon plugging[1]. For comparison here
is usual message I got last time mounted[2]

I am not sure what may have caused the issue but there are two things
I suspect that may have caused this.
1. I usually forget the device is mounted and sda1 partition swappedon
while suspending/sleeping the system. I run fsck.ext3 on the
complaining dirty partitions.
2. I accidentally ran grub-install /dev/sda instead of /dev/hda last
week and interrupted immediately. There is no sign of a problem in the
logs for a week. I had install grub on sda couple of years ago  but
hadnt used it for a long time.

I thought this may be related because interrupting the grub-install
left in complete mbr. So I ran grub-install on sda again but it could
not find the disk[3].

I cannot think of anything else to try. I hope you can suggest me a
way to recover the device or to extract data from it.


[0]
Oct  9 20:30:01 elsewhere cron[3670]: (root) CMD (test -x
/usr/sbin/run-crons && /usr/sbin/run-crons )
Oct  9 20:38:00 elsewhere kernel: [265616.964879] sd 8:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:38:00 elsewhere kernel: [265616.964893] sd 8:0:0:0: [sda]
Sense Key : 0x5 [current]
Oct  9 20:38:00 elsewhere kernel: [265616.964904] Info fld=0x0
Oct  9 20:38:00 elsewhere kernel: [265616.964909] sd 8:0:0:0: [sda]
ASC=0x21 ASCQ=0x0
Oct  9 20:38:00 elsewhere kernel: [265616.964918] sd 8:0:0:0: [sda]
CDB: cdb[0]=0x28: 28 00 00 19 b6 78 00 00 08 00
Oct  9 20:38:00 elsewhere kernel: [265616.964938] end_request: I/O
error, dev sda, sector 1685112
Oct  9 20:38:00 elsewhere kernel: [265616.964972] EXT3-fs error
(device sda2): ext3_find_entry: reading directory #8238 offset 0
Oct  9 20:38:20 elsewhere kernel: [265637.556176] sd 8:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:38:20 elsewhere kernel: [265637.556190] sd 8:0:0:0: [sda]
Sense Key : 0x5 [current]
Oct  9 20:38:20 elsewhere kernel: [265637.556200] Info fld=0x0
Oct  9 20:38:20 elsewhere kernel: [265637.556206] sd 8:0:0:0: [sda]
ASC=0x21 ASCQ=0x0
Oct  9 20:38:20 elsewhere kernel: [265637.556214] sd 8:0:0:0: [sda]
CDB: cdb[0]=0x28: 28 00 00 1d c6 60 00 00 08 00
Oct  9 20:38:20 elsewhere kernel: [265637.556234] end_request: I/O
error, dev sda, sector 1951328
Oct  9 20:38:20 elsewhere kernel: [265637.556281] EXT3-fs error
(device sda2): ext3_get_inode_loc: unable to read inode block -
inode=24579, block=99331
Oct  9 20:38:20 elsewhere kernel: [265637.558297] sd 8:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:38:20 elsewhere kernel: [265637.558310] sd 8:0:0:0: [sda]
Sense Key : 0x5 [current]
Oct  9 20:38:20 elsewhere kernel: [265637.558320] Info fld=0x0
Oct  9 20:38:20 elsewhere kernel: [265637.558325] sd 8:0:0:0: [sda]
ASC=0x21 ASCQ=0x0
Oct  9 20:38:20 elsewhere kernel: [265637.558333] sd 8:0:0:0: [sda]
CDB: cdb[0]=0x2a: 2a 00 00 11 a6 48 00 00 08 00
Oct  9 20:38:20 elsewhere kernel: [265637.558352] end_request: I/O
error, dev sda, sector 1156680
Oct  9 20:38:20 elsewhere kernel: [265637.558363] Buffer I/O error on
device sda2, logical block 0
Oct  9 20:38:20 elsewhere kernel: [265637.558370] lost page write due
to I/O error on sda2
Oct  9 20:39:25 elsewhere kernel: [265702.325405] sd 8:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:39:25 elsewhere kernel: [265702.325419] sd 8:0:0:0: [sda]
Sense Key : 0x5 [current]
Oct  9 20:39:25 elsewhere kernel: [265702.325430] Info fld=0x0
Oct  9 20:39:25 elsewhere kernel: [265702.325435] sd 8:0:0:0: [sda]
ASC=0x21 ASCQ=0x0
Oct  9 20:39:25 elsewhere kernel: [265702.325444] sd 8:0:0:0: [sda]
CDB: cdb[0]=0x2a: 2a 00 00 11 ce 90 00 00 08 00
Oct  9 20:39:25 elsewhere kernel: [265702.325464] end_request: I/O
error, dev sda, sector 1166992
Oct  9 20:39:25 elsewhere kernel: [265702.325475] Buffer I/O error on
device sda2, logical block 1289
Oct  9 20:39:25 elsewhere kernel: [265702.325482] lost page write due
to I/O error on sda2
Oct  9 20:39:25 elsewhere kernel: [265702.325533] ------------[ cut
here ]------------
Oct  9 20:39:25 elsewhere kernel: [265702.325547] WARNING: at
fs/buffer.c:1151 mark_buffer_dirty+0x23/0x6b()
Oct  9 20:39:25 elsewhere kernel: [265702.325554] Hardware name: Amilo A1640
Oct  9 20:39:25 elsewhere kernel: [265702.325563] Pid: 3711, comm:
umount Not tainted 2.6.35-gentoo-r4 #1
Oct  9 20:39:25 elsewhere kernel: [265702.325569] Call Trace:
Oct  9 20:39:25 elsewhere kernel: [265702.325584]  [<c1031c61>]
warn_slowpath_common+0x60/0x75
Oct  9 20:39:25 elsewhere kernel: [265702.325593]  [<c10b3012>] ?
mark_buffer_dirty+0x23/0x6b
Oct  9 20:39:25 elsewhere kernel: [265702.325604]  [<c1031c85>]
warn_slowpath_null+0xf/0x13
Oct  9 20:39:25 elsewhere kernel: [265702.325612]  [<c10b3012>]
mark_buffer_dirty+0x23/0x6b
Oct  9 20:39:25 elsewhere kernel: [265702.325624]  [<c1133e7b>]
journal_update_superblock+0x62/0xab
Oct  9 20:39:25 elsewhere kernel: [265702.325634]  [<c1132a38>]
cleanup_journal_tail+0xd2/0xdb
Oct  9 20:39:25 elsewhere kernel: [265702.325643]  [<c1132efa>]
log_do_checkpoint+0x41d/0x431
Oct  9 20:39:25 elsewhere kernel: [265702.325653]  [<c102c6e9>] ?
update_curr+0x161/0x169
Oct  9 20:39:25 elsewhere kernel: [265702.325663]  [<c102c9ed>] ?
dequeue_entity+0xb4/0x226
Oct  9 20:39:25 elsewhere kernel: [265702.325672]  [<c1025c3d>] ?
__dequeue_entity+0x23/0x27
Oct  9 20:39:25 elsewhere kernel: [265702.325684]  [<c100832b>] ?
__switch_to_xtra+0xe4/0x101
Oct  9 20:39:25 elsewhere kernel: [265702.325696]  [<c13f112f>] ?
_raw_spin_unlock_irq+0x15/0x20
Oct  9 20:39:25 elsewhere kernel: [265702.325706]  [<c10297e8>] ?
finish_task_switch+0x34/0x52
Oct  9 20:39:25 elsewhere kernel: [265702.325717]  [<c1024b04>] ?
need_resched+0x14/0x1e
Oct  9 20:39:25 elsewhere kernel: [265702.325726]  [<c13efd4d>] ?
schedule+0x4f9/0x509
Oct  9 20:39:25 elsewhere kernel: [265702.325737]  [<c13f110f>] ?
_raw_spin_unlock_irqrestore+0x16/0x21
Oct  9 20:39:25 elsewhere kernel: [265702.325747]  [<c10424af>] ?
spin_unlock_irqrestore+0x8/0xa
Oct  9 20:39:25 elsewhere kernel: [265702.325756]  [<c1134166>]
journal_destroy+0xe3/0x18f
Oct  9 20:39:25 elsewhere kernel: [265702.325765]  [<c1042441>] ?
autoremove_wake_function+0x0/0x2f
Oct  9 20:39:25 elsewhere kernel: [265702.325777]  [<c1101918>]
ext3_put_super+0x3a/0x1e5
Oct  9 20:39:25 elsewhere kernel: [265702.325786]  [<c109a7c9>]
generic_shutdown_super+0x42/0xb3
Oct  9 20:39:25 elsewhere kernel: [265702.325795]  [<c109a857>]
kill_block_super+0x1d/0x31
Oct  9 20:39:25 elsewhere kernel: [265702.325803]  [<c1099ee7>]
deactivate_locked_super+0x1a/0x36
Oct  9 20:39:25 elsewhere kernel: [265702.325811]  [<c109a29b>]
deactivate_super+0x32/0x36
Oct  9 20:39:25 elsewhere kernel: [265702.325820]  [<c10aa185>]
mntput_no_expire+0x85/0xa8
Oct  9 20:39:25 elsewhere kernel: [265702.325828]  [<c10aa609>]
sys_umount+0x26e/0x293
Oct  9 20:39:25 elsewhere kernel: [265702.325837]  [<c10aa63b>]
sys_oldumount+0xd/0xf
Oct  9 20:39:25 elsewhere kernel: [265702.325845]  [<c100270c>]
sysenter_do_call+0x12/0x22
Oct  9 20:39:25 elsewhere kernel: [265702.325852] ---[ end trace
113c73c40a67cbb5 ]---
Oct  9 20:39:25 elsewhere kernel: [265702.327279] sd 8:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:39:25 elsewhere kernel: [265702.327292] sd 8:0:0:0: [sda]
Sense Key : 0x5 [current]
Oct  9 20:39:25 elsewhere kernel: [265702.327302] Info fld=0x0
Oct  9 20:39:25 elsewhere kernel: [265702.327307] sd 8:0:0:0: [sda]
ASC=0x21 ASCQ=0x0
Oct  9 20:39:25 elsewhere kernel: [265702.327316] sd 8:0:0:0: [sda]
CDB: cdb[0]=0x2a: 2a 00 00 11 ce 90 00 00 08 00
Oct  9 20:39:25 elsewhere kernel: [265702.327335] end_request: I/O
error, dev sda, sector 1166992
Oct  9 20:39:25 elsewhere kernel: [265702.327346] Buffer I/O error on
device sda2, logical block 1289
Oct  9 20:39:25 elsewhere kernel: [265702.327352] lost page write due
to I/O error on sda2
Oct  9 20:39:25 elsewhere kernel: [265702.327408] Aborting journal on
device sda2.
Oct  9 20:39:25 elsewhere kernel: [265702.328790] sd 8:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:39:25 elsewhere kernel: [265702.328804] sd 8:0:0:0: [sda]
Sense Key : 0x5 [current]
Oct  9 20:39:25 elsewhere kernel: [265702.328814] Info fld=0x0
Oct  9 20:39:25 elsewhere kernel: [265702.328819] sd 8:0:0:0: [sda]
ASC=0x21 ASCQ=0x0
Oct  9 20:39:25 elsewhere kernel: [265702.328827] sd 8:0:0:0: [sda]
CDB: cdb[0]=0x2a: 2a 00 00 11 ce 90 00 00 08 00
Oct  9 20:39:25 elsewhere kernel: [265702.328847] end_request: I/O
error, dev sda, sector 1166992
Oct  9 20:39:25 elsewhere kernel: [265702.328857] Buffer I/O error on
device sda2, logical block 1289
Oct  9 20:39:25 elsewhere kernel: [265702.328864] lost page write due
to I/O error on sda2
Oct  9 20:39:25 elsewhere kernel: [265702.328929] EXT3-fs (sda2):
error: ext3_put_super: Couldn't clean up the journal
Oct  9 20:39:25 elsewhere kernel: [265702.328938] EXT3-fs (sda2):
error: remounting filesystem read-only
Oct  9 20:39:25 elsewhere kernel: [265702.367778] sd 8:0:0:0: [sda]
Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:39:25 elsewhere kernel: [265702.367792] sd 8:0:0:0: [sda]
Sense Key : 0x5 [current]
Oct  9 20:39:25 elsewhere kernel: [265702.367802] Info fld=0x0
.... [goes like this for hundreds of lines]....

[1]
Oct  9 20:56:10 elsewhere kernel: [266707.674053] usb 1-2: new high
speed USB device using ehci_hcd and address 33
Oct  9 20:56:11 elsewhere kernel: [266707.789928] usb 1-2: New USB
device found, idVendor=1058, idProduct=0702
Oct  9 20:56:11 elsewhere kernel: [266707.789940] usb 1-2: New USB
device strings: Mfr=1, Product=2, SerialNumber=3
Oct  9 20:56:11 elsewhere kernel: [266707.789948] usb 1-2: Product:
External HDD
Oct  9 20:56:11 elsewhere kernel: [266707.789954] usb 1-2:
Manufacturer: Western Digital
Oct  9 20:56:11 elsewhere kernel: [266707.789961] usb 1-2:
SerialNumber: <U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF>
<U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF>
Oct  9 20:56:11 elsewhere kernel: [266707.795512] scsi10 : usb-storage 1-2:1.0
Oct  9 20:56:12 elsewhere kernel: [266708.825857] scsi 10:0:0:0:
Direct-Access     WD                        1.02 PQ: 0 ANSI: 0
Oct  9 20:56:12 elsewhere kernel: [266708.826235] sd 10:0:0:0:
Attached scsi generic sg0 type 0
Oct  9 20:56:12 elsewhere kernel: [266708.860619] sd 10:0:0:0: [sda]
Too big for this kernel. Use a kernel compiled with support for large
block devices.
Oct  9 20:56:12 elsewhere kernel: [266708.860634] sd 10:0:0:0: [sda]
Unsupported sector size -75.
Oct  9 20:56:12 elsewhere kernel: [266708.860647] sd 10:0:0:0: [sda] 0
512-byte logical blocks: (0 B/0 B)
Oct  9 20:56:12 elsewhere kernel: [266708.860655] sd 10:0:0:0: [sda]
0-byte physical blocks
Oct  9 20:56:12 elsewhere kernel: [266708.862230] sd 10:0:0:0: [sda]
Write Protect is off
Oct  9 20:56:12 elsewhere kernel: [266708.862241] sd 10:0:0:0: [sda]
Mode Sense: 00 00 00 00
Oct  9 20:56:12 elsewhere kernel: [266708.862249] sd 10:0:0:0: [sda]
Assuming drive cache: write through
Oct  9 20:56:12 elsewhere kernel: [266708.865587] sd 10:0:0:0: [sda]
Too big for this kernel. Use a kernel compiled with support for large
block devices.
Oct  9 20:56:12 elsewhere kernel: [266708.865601] sd 10:0:0:0: [sda]
Unsupported sector size -75.
Oct  9 20:56:12 elsewhere kernel: [266708.867487] sd 10:0:0:0: [sda]
Assuming drive cache: write through
Oct  9 20:56:12 elsewhere kernel: [266708.867499] sd 10:0:0:0: [sda]
Attached SCSI disk

[2]
Oct  9 06:55:30 elsewhere kernel: [216267.317041] usb 1-2: new high
speed USB device using ehci_hcd and address 31
Oct  9 06:55:30 elsewhere kernel: [216267.432928] usb 1-2: New USB
device found, idVendor=1058, idProduct=0702
Oct  9 06:55:30 elsewhere kernel: [216267.432939] usb 1-2: New USB
device strings: Mfr=1, Product=2, SerialNumber=3
Oct  9 06:55:30 elsewhere kernel: [216267.432947] usb 1-2: Product: External HDD
Oct  9 06:55:30 elsewhere kernel: [216267.432953] usb 1-2:
Manufacturer: Western Digital
Oct  9 06:55:30 elsewhere kernel: [216267.432959] usb 1-2:
SerialNumber: 575845343037323832333437
Oct  9 06:55:30 elsewhere kernel: [216267.437545] scsi8 : usb-storage 1-2:1.0
Oct  9 06:55:31 elsewhere kernel: [216268.447876] scsi 8:0:0:0:
Direct-Access     WD       1600BEVExternal  1.02 PQ: 0 ANSI: 0
Oct  9 06:55:31 elsewhere kernel: [216268.448238] sd 8:0:0:0: Attached
scsi generic sg0 type 0
Oct  9 06:55:31 elsewhere kernel: [216268.481955] sd 8:0:0:0: [sda]
312581808 512-byte logical blocks: (160 GB/149 GiB)
Oct  9 06:55:31 elsewhere kernel: [216268.483225] sd 8:0:0:0: [sda]
Write Protect is off
Oct  9 06:55:31 elsewhere kernel: [216268.483238] sd 8:0:0:0: [sda]
Mode Sense: 00 00 00 00
Oct  9 06:55:31 elsewhere kernel: [216268.483246] sd 8:0:0:0: [sda]
Assuming drive cache: write through
Oct  9 06:55:31 elsewhere kernel: [216268.484846] sd 8:0:0:0: [sda]
Assuming drive cache: write through
Oct  9 06:55:31 elsewhere kernel: [216268.484864]  sda: sda1 sda2 sda3
sda4 < sda5 >
Oct  9 06:55:31 elsewhere kernel: [216268.558235] sd 8:0:0:0: [sda]
Assuming drive cache: write through
Oct  9 06:55:31 elsewhere kernel: [216268.558248] sd 8:0:0:0: [sda]
Attached SCSI disk
Oct  9 06:55:33 elsewhere kernel: [216270.550685] EXT3-fs: barriers not enabled
Oct  9 06:55:33 elsewhere kernel: [216270.566936] kjournald starting.
Commit interval 5 seconds
Oct  9 06:55:33 elsewhere kernel: [216270.567529] EXT3-fs (sda2):
using internal journal
Oct  9 06:55:33 elsewhere kernel: [216270.567545] EXT3-fs (sda2):
mounted filesystem with writeback data mode
Oct  9 06:55:34 elsewhere kernel: [216270.898980] EXT3-fs: barriers not enabled
Oct  9 06:55:34 elsewhere kernel: [216270.910455] kjournald starting.
Commit interval 5 seconds
Oct  9 06:55:34 elsewhere kernel: [216270.911421] EXT3-fs (sda5):
using internal journal
Oct  9 06:55:34 elsewhere kernel: [216270.911437] EXT3-fs (sda5):
mounted filesystem with writeback data mode

[3]
# grub-install --no-floppy /dev/sda


    GNU GRUB  version 0.97  (640K lower / 5120K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]
grub> root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83
grub> setup  --stage2=/boot/grub/stage2 --prefix=/grub (hd1)
 Checking if "/grub/stage1" exists... yes
 Checking if "/grub/stage2" exists... yes
 Checking if "/grub/e2fs_stage1_5" exists... yes
 Running "embed /grub/e2fs_stage1_5 (hd1)"... failed (this is not fatal)
 Running "embed /grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal)
 Running "install --stage2=/boot/grub/stage2 /grub/stage1 d (hd1)
/grub/stage2 p /grub/menu.lst "... failed

Error 21: Selected disk does not exist
grub> quit


--
    Fatih

[gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Fatih Tümen]

[-- Attachment #1: Type: text/plain, Size: 965 bytes --]

2010/10/9 Fatih Tümen <fthtmn+gentoo@gmail.com>:
> I am not sure what may have caused the issue but there are two things
> I suspect that may have caused this.
> 1. I usually forget the device is mounted and sda1 partition swappedon
> while suspending/sleeping the system. I run fsck.ext3 on the
> complaining dirty partitions.
> 2. I accidentally ran grub-install /dev/sda instead of /dev/hda last
> week and interrupted immediately. There is no sign of a problem in the
> logs for a week. I had install grub on sda couple of years ago  but
> hadnt used it for a long time.
>
> I thought this may be related because interrupting the grub-install
> left in complete mbr. So I ran grub-install on sda again but it could
> not find the disk[3].
>
> I cannot think of anything else to try. I hope you can suggest me a
> way to recover the device or to extract data from it.

The attached file should be better for viewing the logs.

--
    Fatih

[-- Attachment #2: messages_usb_disk_failure_20101009_2038.txt --]
[-- Type: text/plain, Size: 13886 bytes --]

[0]
Oct  9 20:30:01 elsewhere cron[3670]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Oct  9 20:38:00 elsewhere kernel: [265616.964879] sd 8:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:38:00 elsewhere kernel: [265616.964893] sd 8:0:0:0: [sda] Sense Key : 0x5 [current]
Oct  9 20:38:00 elsewhere kernel: [265616.964904] Info fld=0x0
Oct  9 20:38:00 elsewhere kernel: [265616.964909] sd 8:0:0:0: [sda] ASC=0x21 ASCQ=0x0
Oct  9 20:38:00 elsewhere kernel: [265616.964918] sd 8:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 19 b6 78 00 00 08 00
Oct  9 20:38:00 elsewhere kernel: [265616.964938] end_request: I/O error, dev sda, sector 1685112
Oct  9 20:38:00 elsewhere kernel: [265616.964972] EXT3-fs error (device sda2): ext3_find_entry: reading directory #8238 offset 0
Oct  9 20:38:20 elsewhere kernel: [265637.556176] sd 8:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:38:20 elsewhere kernel: [265637.556190] sd 8:0:0:0: [sda] Sense Key : 0x5 [current]
Oct  9 20:38:20 elsewhere kernel: [265637.556200] Info fld=0x0
Oct  9 20:38:20 elsewhere kernel: [265637.556206] sd 8:0:0:0: [sda] ASC=0x21 ASCQ=0x0
Oct  9 20:38:20 elsewhere kernel: [265637.556214] sd 8:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 00 1d c6 60 00 00 08 00
Oct  9 20:38:20 elsewhere kernel: [265637.556234] end_request: I/O error, dev sda, sector 1951328
Oct  9 20:38:20 elsewhere kernel: [265637.556281] EXT3-fs error (device sda2): ext3_get_inode_loc: unable to read inode block - inode=24579, block=99331
Oct  9 20:38:20 elsewhere kernel: [265637.558297] sd 8:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:38:20 elsewhere kernel: [265637.558310] sd 8:0:0:0: [sda] Sense Key : 0x5 [current]
Oct  9 20:38:20 elsewhere kernel: [265637.558320] Info fld=0x0
Oct  9 20:38:20 elsewhere kernel: [265637.558325] sd 8:0:0:0: [sda] ASC=0x21 ASCQ=0x0
Oct  9 20:38:20 elsewhere kernel: [265637.558333] sd 8:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 11 a6 48 00 00 08 00
Oct  9 20:38:20 elsewhere kernel: [265637.558352] end_request: I/O error, dev sda, sector 1156680
Oct  9 20:38:20 elsewhere kernel: [265637.558363] Buffer I/O error on device sda2, logical block 0
Oct  9 20:38:20 elsewhere kernel: [265637.558370] lost page write due to I/O error on sda2
Oct  9 20:39:25 elsewhere kernel: [265702.325405] sd 8:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:39:25 elsewhere kernel: [265702.325419] sd 8:0:0:0: [sda] Sense Key : 0x5 [current]
Oct  9 20:39:25 elsewhere kernel: [265702.325430] Info fld=0x0
Oct  9 20:39:25 elsewhere kernel: [265702.325435] sd 8:0:0:0: [sda] ASC=0x21 ASCQ=0x0
Oct  9 20:39:25 elsewhere kernel: [265702.325444] sd 8:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 11 ce 90 00 00 08 00
Oct  9 20:39:25 elsewhere kernel: [265702.325464] end_request: I/O error, dev sda, sector 1166992
Oct  9 20:39:25 elsewhere kernel: [265702.325475] Buffer I/O error on device sda2, logical block 1289
Oct  9 20:39:25 elsewhere kernel: [265702.325482] lost page write due to I/O error on sda2
Oct  9 20:39:25 elsewhere kernel: [265702.325533] ------------[ cut here ]------------
Oct  9 20:39:25 elsewhere kernel: [265702.325547] WARNING: at fs/buffer.c:1151 mark_buffer_dirty+0x23/0x6b()
Oct  9 20:39:25 elsewhere kernel: [265702.325554] Hardware name: Amilo A1640
Oct  9 20:39:25 elsewhere kernel: [265702.325563] Pid: 3711, comm: umount Not tainted 2.6.35-gentoo-r4 #1
Oct  9 20:39:25 elsewhere kernel: [265702.325569] Call Trace:
Oct  9 20:39:25 elsewhere kernel: [265702.325584]  [<c1031c61>] warn_slowpath_common+0x60/0x75
Oct  9 20:39:25 elsewhere kernel: [265702.325593]  [<c10b3012>] ? mark_buffer_dirty+0x23/0x6b
Oct  9 20:39:25 elsewhere kernel: [265702.325604]  [<c1031c85>] warn_slowpath_null+0xf/0x13
Oct  9 20:39:25 elsewhere kernel: [265702.325612]  [<c10b3012>] mark_buffer_dirty+0x23/0x6b
Oct  9 20:39:25 elsewhere kernel: [265702.325624]  [<c1133e7b>] journal_update_superblock+0x62/0xab
Oct  9 20:39:25 elsewhere kernel: [265702.325634]  [<c1132a38>] cleanup_journal_tail+0xd2/0xdb
Oct  9 20:39:25 elsewhere kernel: [265702.325643]  [<c1132efa>] log_do_checkpoint+0x41d/0x431
Oct  9 20:39:25 elsewhere kernel: [265702.325653]  [<c102c6e9>] ? update_curr+0x161/0x169
Oct  9 20:39:25 elsewhere kernel: [265702.325663]  [<c102c9ed>] ? dequeue_entity+0xb4/0x226
Oct  9 20:39:25 elsewhere kernel: [265702.325672]  [<c1025c3d>] ? __dequeue_entity+0x23/0x27
Oct  9 20:39:25 elsewhere kernel: [265702.325684]  [<c100832b>] ? __switch_to_xtra+0xe4/0x101
Oct  9 20:39:25 elsewhere kernel: [265702.325696]  [<c13f112f>] ? _raw_spin_unlock_irq+0x15/0x20
Oct  9 20:39:25 elsewhere kernel: [265702.325706]  [<c10297e8>] ? finish_task_switch+0x34/0x52
Oct  9 20:39:25 elsewhere kernel: [265702.325717]  [<c1024b04>] ? need_resched+0x14/0x1e
Oct  9 20:39:25 elsewhere kernel: [265702.325726]  [<c13efd4d>] ? schedule+0x4f9/0x509
Oct  9 20:39:25 elsewhere kernel: [265702.325737]  [<c13f110f>] ? _raw_spin_unlock_irqrestore+0x16/0x21
Oct  9 20:39:25 elsewhere kernel: [265702.325747]  [<c10424af>] ? spin_unlock_irqrestore+0x8/0xa
Oct  9 20:39:25 elsewhere kernel: [265702.325756]  [<c1134166>] journal_destroy+0xe3/0x18f
Oct  9 20:39:25 elsewhere kernel: [265702.325765]  [<c1042441>] ? autoremove_wake_function+0x0/0x2f
Oct  9 20:39:25 elsewhere kernel: [265702.325777]  [<c1101918>] ext3_put_super+0x3a/0x1e5
Oct  9 20:39:25 elsewhere kernel: [265702.325786]  [<c109a7c9>] generic_shutdown_super+0x42/0xb3
Oct  9 20:39:25 elsewhere kernel: [265702.325795]  [<c109a857>] kill_block_super+0x1d/0x31
Oct  9 20:39:25 elsewhere kernel: [265702.325803]  [<c1099ee7>] deactivate_locked_super+0x1a/0x36
Oct  9 20:39:25 elsewhere kernel: [265702.325811]  [<c109a29b>] deactivate_super+0x32/0x36
Oct  9 20:39:25 elsewhere kernel: [265702.325820]  [<c10aa185>] mntput_no_expire+0x85/0xa8
Oct  9 20:39:25 elsewhere kernel: [265702.325828]  [<c10aa609>] sys_umount+0x26e/0x293
Oct  9 20:39:25 elsewhere kernel: [265702.325837]  [<c10aa63b>] sys_oldumount+0xd/0xf
Oct  9 20:39:25 elsewhere kernel: [265702.325845]  [<c100270c>] sysenter_do_call+0x12/0x22
Oct  9 20:39:25 elsewhere kernel: [265702.325852] ---[ end trace 113c73c40a67cbb5 ]---
Oct  9 20:39:25 elsewhere kernel: [265702.327279] sd 8:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:39:25 elsewhere kernel: [265702.327292] sd 8:0:0:0: [sda] Sense Key : 0x5 [current]
Oct  9 20:39:25 elsewhere kernel: [265702.327302] Info fld=0x0
Oct  9 20:39:25 elsewhere kernel: [265702.327307] sd 8:0:0:0: [sda] ASC=0x21 ASCQ=0x0
Oct  9 20:39:25 elsewhere kernel: [265702.327316] sd 8:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 11 ce 90 00 00 08 00
Oct  9 20:39:25 elsewhere kernel: [265702.327335] end_request: I/O error, dev sda, sector 1166992
Oct  9 20:39:25 elsewhere kernel: [265702.327346] Buffer I/O error on device sda2, logical block 1289
Oct  9 20:39:25 elsewhere kernel: [265702.327352] lost page write due to I/O error on sda2
Oct  9 20:39:25 elsewhere kernel: [265702.327408] Aborting journal on device sda2.
Oct  9 20:39:25 elsewhere kernel: [265702.328790] sd 8:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:39:25 elsewhere kernel: [265702.328804] sd 8:0:0:0: [sda] Sense Key : 0x5 [current]
Oct  9 20:39:25 elsewhere kernel: [265702.328814] Info fld=0x0
Oct  9 20:39:25 elsewhere kernel: [265702.328819] sd 8:0:0:0: [sda] ASC=0x21 ASCQ=0x0
Oct  9 20:39:25 elsewhere kernel: [265702.328827] sd 8:0:0:0: [sda] CDB: cdb[0]=0x2a: 2a 00 00 11 ce 90 00 00 08 00
Oct  9 20:39:25 elsewhere kernel: [265702.328847] end_request: I/O error, dev sda, sector 1166992
Oct  9 20:39:25 elsewhere kernel: [265702.328857] Buffer I/O error on device sda2, logical block 1289
Oct  9 20:39:25 elsewhere kernel: [265702.328864] lost page write due to I/O error on sda2
Oct  9 20:39:25 elsewhere kernel: [265702.328929] EXT3-fs (sda2): error: ext3_put_super: Couldn't clean up the journal
Oct  9 20:39:25 elsewhere kernel: [265702.328938] EXT3-fs (sda2): error: remounting filesystem read-only
Oct  9 20:39:25 elsewhere kernel: [265702.367778] sd 8:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08
Oct  9 20:39:25 elsewhere kernel: [265702.367792] sd 8:0:0:0: [sda] Sense Key : 0x5 [current]
Oct  9 20:39:25 elsewhere kernel: [265702.367802] Info fld=0x0
.... [goes like this for hundreds of lines]....

[1]
Oct  9 20:56:10 elsewhere kernel: [266707.674053] usb 1-2: new high speed USB device using ehci_hcd and address 33
Oct  9 20:56:11 elsewhere kernel: [266707.789928] usb 1-2: New USB device found, idVendor=1058, idProduct=0702
Oct  9 20:56:11 elsewhere kernel: [266707.789940] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  9 20:56:11 elsewhere kernel: [266707.789948] usb 1-2: Product: External HDD    
Oct  9 20:56:11 elsewhere kernel: [266707.789954] usb 1-2: Manufacturer: Western Digital 
Oct  9 20:56:11 elsewhere kernel: [266707.789961] usb 1-2: SerialNumber: <U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF>
<U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF><U+FFFF>
Oct  9 20:56:11 elsewhere kernel: [266707.795512] scsi10 : usb-storage 1-2:1.0
Oct  9 20:56:12 elsewhere kernel: [266708.825857] scsi 10:0:0:0: Direct-Access     WD                        1.02 PQ: 0 ANSI: 0
Oct  9 20:56:12 elsewhere kernel: [266708.826235] sd 10:0:0:0: Attached scsi generic sg0 type 0
Oct  9 20:56:12 elsewhere kernel: [266708.860619] sd 10:0:0:0: [sda] Too big for this kernel. Use a kernel compiled with support for large block devices.
Oct  9 20:56:12 elsewhere kernel: [266708.860634] sd 10:0:0:0: [sda] Unsupported sector size -75.
Oct  9 20:56:12 elsewhere kernel: [266708.860647] sd 10:0:0:0: [sda] 0 512-byte logical blocks: (0 B/0 B)
Oct  9 20:56:12 elsewhere kernel: [266708.860655] sd 10:0:0:0: [sda] 0-byte physical blocks
Oct  9 20:56:12 elsewhere kernel: [266708.862230] sd 10:0:0:0: [sda] Write Protect is off
Oct  9 20:56:12 elsewhere kernel: [266708.862241] sd 10:0:0:0: [sda] Mode Sense: 00 00 00 00
Oct  9 20:56:12 elsewhere kernel: [266708.862249] sd 10:0:0:0: [sda] Assuming drive cache: write through
Oct  9 20:56:12 elsewhere kernel: [266708.865587] sd 10:0:0:0: [sda] Too big for this kernel. Use a kernel compiled with support for large block devices.
Oct  9 20:56:12 elsewhere kernel: [266708.865601] sd 10:0:0:0: [sda] Unsupported sector size -75.
Oct  9 20:56:12 elsewhere kernel: [266708.867487] sd 10:0:0:0: [sda] Assuming drive cache: write through
Oct  9 20:56:12 elsewhere kernel: [266708.867499] sd 10:0:0:0: [sda] Attached SCSI disk

[2]
Oct  9 06:55:30 elsewhere kernel: [216267.317041] usb 1-2: new high speed USB device using ehci_hcd and address 31
Oct  9 06:55:30 elsewhere kernel: [216267.432928] usb 1-2: New USB device found, idVendor=1058, idProduct=0702
Oct  9 06:55:30 elsewhere kernel: [216267.432939] usb 1-2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Oct  9 06:55:30 elsewhere kernel: [216267.432947] usb 1-2: Product: External HDD
Oct  9 06:55:30 elsewhere kernel: [216267.432953] usb 1-2: Manufacturer: Western Digital
Oct  9 06:55:30 elsewhere kernel: [216267.432959] usb 1-2: SerialNumber: 575845343037323832333437
Oct  9 06:55:30 elsewhere kernel: [216267.437545] scsi8 : usb-storage 1-2:1.0
Oct  9 06:55:31 elsewhere kernel: [216268.447876] scsi 8:0:0:0: Direct-Access     WD       1600BEVExternal  1.02 PQ: 0 ANSI: 0
Oct  9 06:55:31 elsewhere kernel: [216268.448238] sd 8:0:0:0: Attached scsi generic sg0 type 0
Oct  9 06:55:31 elsewhere kernel: [216268.481955] sd 8:0:0:0: [sda] 312581808 512-byte logical blocks: (160 GB/149 GiB)
Oct  9 06:55:31 elsewhere kernel: [216268.483225] sd 8:0:0:0: [sda] Write Protect is off
Oct  9 06:55:31 elsewhere kernel: [216268.483238] sd 8:0:0:0: [sda] Mode Sense: 00 00 00 00
Oct  9 06:55:31 elsewhere kernel: [216268.483246] sd 8:0:0:0: [sda] Assuming drive cache: write through
Oct  9 06:55:31 elsewhere kernel: [216268.484846] sd 8:0:0:0: [sda] Assuming drive cache: write through
Oct  9 06:55:31 elsewhere kernel: [216268.484864]  sda: sda1 sda2 sda3 sda4 < sda5 >
Oct  9 06:55:31 elsewhere kernel: [216268.558235] sd 8:0:0:0: [sda] Assuming drive cache: write through
Oct  9 06:55:31 elsewhere kernel: [216268.558248] sd 8:0:0:0: [sda] Attached SCSI disk
Oct  9 06:55:33 elsewhere kernel: [216270.550685] EXT3-fs: barriers not enabled
Oct  9 06:55:33 elsewhere kernel: [216270.566936] kjournald starting.  Commit interval 5 seconds
Oct  9 06:55:33 elsewhere kernel: [216270.567529] EXT3-fs (sda2): using internal journal
Oct  9 06:55:33 elsewhere kernel: [216270.567545] EXT3-fs (sda2): mounted filesystem with writeback data mode
Oct  9 06:55:34 elsewhere kernel: [216270.898980] EXT3-fs: barriers not enabled
Oct  9 06:55:34 elsewhere kernel: [216270.910455] kjournald starting.  Commit interval 5 seconds
Oct  9 06:55:34 elsewhere kernel: [216270.911421] EXT3-fs (sda5): using internal journal
Oct  9 06:55:34 elsewhere kernel: [216270.911437] EXT3-fs (sda5): mounted filesystem with writeback data mode

[3]
# grub-install --no-floppy /dev/sda


    GNU GRUB  version 0.97  (640K lower / 5120K upper memory)

 [ Minimal BASH-like line editing is supported.  For the first word, TAB
   lists possible command completions.  Anywhere else TAB lists the possible
   completions of a device/filename. ]
grub> root (hd0,0)
 Filesystem type is ext2fs, partition type 0x83
grub> setup  --stage2=/boot/grub/stage2 --prefix=/grub (hd1)
 Checking if "/grub/stage1" exists... yes
 Checking if "/grub/stage2" exists... yes
 Checking if "/grub/e2fs_stage1_5" exists... yes
 Running "embed /grub/e2fs_stage1_5 (hd1)"... failed (this is not fatal)
 Running "embed /grub/e2fs_stage1_5 (hd0,0)"... failed (this is not fatal)
 Running "install --stage2=/boot/grub/stage2 /grub/stage1 d (hd1) /grub/stage2 p /grub/menu.lst "... failed

Error 21: Selected disk does not exist
grub> quit

[gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[walt]

On 10/09/2010 12:36 PM, Fatih Tümen wrote:

>> 2. I accidentally ran grub-install /dev/sda instead of /dev/hda

If you still actually have an 'hda' then you should start using the new
disk drivers in the kernel "CONFIG_ATA" section rather than the older
and deprecated "CONFIG_IDE" section.

That will make all of your /dev/hd* devices become /dev/sd* instead.  This
may have nothing to do with your current problem, but it's time to make the
change in any case.  (You will need to make appropriate changes in fstab.)

> grub>  setup  --stage2=/boot/grub/stage2 --prefix=/grub (hd1)
> Error 21: Selected disk does not exist

What choices does grub show you when you type "root (hd" and then hit
TAB?  That should list all hard disks that your BIOS knows about.  The
list will change, of course, depending on whether your USB disk is plugged
in (and working) or not.  (grub always refers to 'hd' and never 'sd', which
I'm sure you already know :)

I'm not using the dreaded 'hardware' word yet, though I'm suspicious.

When you tested the drive on the other machine, did you use a different
USB cable?

Will fdisk read and recognize the partition table on the USB disk? If fdisk
results in disk read errors then I'd begin to think more about 'hardware' :(

Re: [gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Fatih Tümen]

On Sun, Oct 10, 2010 at 12:15 AM, walt <w41ter@gmail.com> wrote:
> On 10/09/2010 12:36 PM, Fatih Tümen wrote:
>
>>> 2. I accidentally ran grub-install /dev/sda instead of /dev/hda
>
> If you still actually have an 'hda' then you should start using the new
> disk drivers in the kernel "CONFIG_ATA" section rather than the older
> and deprecated "CONFIG_IDE" section.
>
I was happy with the distinction between local and external disk. But
thanks for the advice.

> That will make all of your /dev/hd* devices become /dev/sd* instead.  This
> may have nothing to do with your current problem, but it's time to make the
> change in any case.  (You will need to make appropriate changes in fstab.)
>
>> grub>  setup  --stage2=/boot/grub/stage2 --prefix=/grub (hd1)
>> Error 21: Selected disk does not exist
>
> What choices does grub show you when you type "root (hd" and then hit
> TAB?  That should list all hard disks that your BIOS knows about.  The
> list will change, of course, depending on whether your USB disk is plugged
> in (and working) or not.  (grub always refers to 'hd' and never 'sd', which
> I'm sure you already know :)
>
Grub currently know only  about hd0, hd1 was what grub called the usb disk.

> I'm not using the dreaded 'hardware' word yet, though I'm suspicious.
>
If you heard the noise coming from the drive when plugged in you be
more than suspicious I think.

> When you tested the drive on the other machine, did you use a different
> USB cable?
>
No but I will do, as soon as I find the other cable.But as I just
noted, drive makes some noise when plugged in. The noise is similar
but less worrying that the one it make first time I ran eix.

> Will fdisk read and recognize the partition table on the USB disk? If fdisk
> results in disk read errors then I'd begin to think more about 'hardware' :(
>
No "Unable to read /dev/sda" is what fdisk says. I never had a disk
(hardware) failure before. Is there no way to extract data from it?

--
    Fatih

Re: [gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Stroller]

On 10 Oct 2010, at 04:58, Fatih Tümen wrote:
> ...
>> I'm not using the dreaded 'hardware' word yet, though I'm suspicious.
>> 
> If you heard the noise coming from the drive when plugged in you be
> more than suspicious I think.


So what's the problem? Bin or warranty the drive - you already told us, I think, there's no important data on there.

Messages like this:

   Oct  9 20:38:20 elsewhere kernel: [265637.556281] EXT3-fs error (device sda2): ext3_get_inode_loc: unable to read inode block - inode=24579, block=99331
   Oct  9 20:38:20 elsewhere kernel: [265637.558352] end_request: I/O error, dev sda, sector 1156680
   Oct  9 20:38:20 elsewhere kernel: [265637.558363] Buffer I/O error on device sda2, logical block 0
   Oct  9 20:38:20 elsewhere kernel: [265637.558370] lost page write due to I/O error on sda2
   Oct  9 20:39:25 elsewhere kernel: [265702.325464] end_request: I/O error, dev sda, sector 1166992

most likely indicate physical failure of the drive. If it's making noises then it *definitely* means the bearings have gone, guv.

If you need to get data off this disk then we can advise (but search the archives for GNU dd_rescue, or just read its manual) but apart from that there's nothing we can do for this drive.

Stroller.

Re: [gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Fatih Tümen]

On Sun, Oct 10, 2010 at 12:23 PM, Stroller
<stroller@stellar.eclipse.co.uk> wrote:
>
> On 10 Oct 2010, at 04:58, Fatih Tümen wrote:
>> ...
>>> I'm not using the dreaded 'hardware' word yet, though I'm suspicious.
>>>
>> If you heard the noise coming from the drive when plugged in you be
>> more than suspicious I think.
>
>
> So what's the problem? Bin or warranty the drive - you already told us, I think, there's no important data on there.
>
There problem is I have two more partition with about 80GB of data.

> Messages like this:
>
>   Oct  9 20:38:20 elsewhere kernel: [265637.556281] EXT3-fs error (device sda2): ext3_get_inode_loc: unable to read inode block - inode=24579, block=99331
>   Oct  9 20:38:20 elsewhere kernel: [265637.558352] end_request: I/O error, dev sda, sector 1156680
>   Oct  9 20:38:20 elsewhere kernel: [265637.558363] Buffer I/O error on device sda2, logical block 0
>   Oct  9 20:38:20 elsewhere kernel: [265637.558370] lost page write due to I/O error on sda2
>   Oct  9 20:39:25 elsewhere kernel: [265702.325464] end_request: I/O error, dev sda, sector 1166992
>
> most likely indicate physical failure of the drive. If it's making noises then it *definitely* means the bearings have gone, guv.
>
> If you need to get data off this disk then we can advise (but search the archives for GNU dd_rescue, or just read its manual) but apart from that there's nothing we can do for this drive.
>

I will that a look at dd_rescue, thanks.

--
    Fatih

Re: [gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Stroller]

On 10 Oct 2010, at 17:21, Fatih Tümen wrote:
> There problem is I have two more partition with about 80GB of data.
> 
>> ....
>> If you need to get data off this disk then we can advise (but search the archives for GNU dd_rescue, or just read its manual) but apart from that there's nothing we can do for this drive.
> 
> I will that a look at dd_rescue, thanks.


My previous spelling was wrong - the GNU version is without the underscore. You want ddrescue NOT dd_rescue.

$ eix -I rescue
[I] sys-fs/ddrescue
     Available versions:  1.9 1.11 ~1.12
     Installed versions:  1.11(12:52:56 05/03/10)
     Homepage:            http://www.gnu.org/software/ddrescue/ddrescue.html
     Description:         Copies data from one file or block device to another with read-error recovery

$

I have found it very useful. From my previous casual glance at your logs you have some hopes - you may not be able to read block 1289,  but you may well be able to get blocks 1288 & 1290. My (limited) experience has been that even with a *really* badly failing hard-drive, over 99% of the blocks are recoverable. 

Confer with the manual <http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html#Examples> and then do something like:

  ddrescue -f -n /dev/sda2 /mnt/volumes/my_disk/recovered.img recovery.log
  <wait a day or two>
  ddrescue -d -f -r3 /dev/sda2 /mnt/volumes/my_disk/recovered.img recovery.log

(where /dev/sda2 is the partition containing the data you want to recover).

Keep running `ddrescue -r X` (where X is a number) for as many passes as you can. If you get data off on one pass, then another one may get more, if you have the time for it. If you're really lucky then you'll find that only a block or two are unrecoverable, if you're unlucky then the unrecoverable blocks will be measured in megabytes.

If you have multiple partitions then post back here (with their sizes and the total size of the disk). You'll need to have at least enough empty space (on a single usable partition) for the whole partition that you want to recover. Ideally you'll have twice that much space, or even three times - this is not the time to skimp on hard-drive capacity. Ideally what you want to do when the above commands have finished is make a copy of recovered.img, so that if one method of recovery doesn't work, you can try another.

I'm not sure what will happen if you simply tried to loopback mount recovered.img - hopefully fsck would run on it automagically, but I suspect that would be too easy. You might have to use losetup to treat the .img as a block device, and then run fsck on /dev/loop0, or something like that. <http://tinyurl.com/2bllb25>

If the disk / partition image fscks without toooooo many errors (and a page or two of them would probably be quite acceptable - expect one error per unrecoverable block) then you still need enough free disk space for all the files you intend to copy off. 

Keep posting your progress back here, so we can advise further.

Stroller.

Re: [gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Fatih Tümen]

On Mon, Oct 11, 2010 at 1:02 AM, Stroller
<stroller@stellar.eclipse.co.uk> wrote:
>
> On 10 Oct 2010, at 17:21, Fatih Tümen wrote:
>> There problem is I have two more partition with about 80GB of data.
>>
>>> ....
>>> If you need to get data off this disk then we can advise (but search the archives for GNU dd_rescue, or just read its manual) but apart from that there's nothing we can do for this drive.
>>
>> I will that a look at dd_rescue, thanks.
>
>
> My previous spelling was wrong - the GNU version is without the underscore. You want ddrescue NOT dd_rescue.
>
> $ eix -I rescue
> [I] sys-fs/ddrescue
>     Available versions:  1.9 1.11 ~1.12
>     Installed versions:  1.11(12:52:56 05/03/10)
>     Homepage:            http://www.gnu.org/software/ddrescue/ddrescue.html
>     Description:         Copies data from one file or block device to another with read-error recovery
>
> $
>
> I have found it very useful. From my previous casual glance at your logs you have some hopes - you may not be able to read block 1289,  but you may well be able to get blocks 1288 & 1290. My (limited) experience has been that even with a *really* badly failing hard-drive, over 99% of the blocks are recoverable.
>
> Confer with the manual <http://www.gnu.org/software/ddrescue/manual/ddrescue_manual.html#Examples> and then do something like:
>
>  ddrescue -f -n /dev/sda2 /mnt/volumes/my_disk/recovered.img recovery.log
>  <wait a day or two>
>  ddrescue -d -f -r3 /dev/sda2 /mnt/volumes/my_disk/recovered.img recovery.log
>
> (where /dev/sda2 is the partition containing the data you want to recover).
>
> Keep running `ddrescue -r X` (where X is a number) for as many passes as you can. If you get data off on one pass, then another one may get more, if you have the time for it. If you're really lucky then you'll find that only a block or two are unrecoverable, if you're unlucky then the unrecoverable blocks will be measured in megabytes.
>
> If you have multiple partitions then post back here (with their sizes and the total size of the disk). You'll need to have at least enough empty space (on a single usable partition) for the whole partition that you want to recover. Ideally you'll have twice that much space, or even three times - this is not the time to skimp on hard-drive capacity. Ideally what you want to do when the above commands have finished is make a copy of recovered.img, so that if one method of recovery doesn't work, you can try another.
>
> I'm not sure what will happen if you simply tried to loopback mount recovered.img - hopefully fsck would run on it automagically, but I suspect that would be too easy. You might have to use losetup to treat the .img as a block device, and then run fsck on /dev/loop0, or something like that. <http://tinyurl.com/2bllb25>
>
> If the disk / partition image fscks without toooooo many errors (and a page or two of them would probably be quite acceptable - expect one error per unrecoverable block) then you still need enough free disk space for all the files you intend to copy off.
>
> Keep posting your progress back here, so we can advise further.
>
> Stroller.
>
>
>

Thank you very much for sharing your experience.

ddrescue sounds quiet promising. The disk was of 160GB I think. Right
now I wont have enough space for recovery until I will order a new
disk. I will post the result here as soon as I am done.

P.S. Would you recommend against 7200rpm usb 2.5" disks?

--
    Fatih

Re: [gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Stroller]

On 11 Oct 2010, at 12:51, Fatih Tümen wrote:
> ...
> P.S. Would you recommend against 7200rpm usb 2.5" disks?

I'm aware of no reason to do so.

Typically usb 2.5" disks can be powered off the USB cable, which is much more portable than the PSU required by external USB 3.5" drives.

I would guess that most drives are generally about as reliable as each other. They are inherently at risk from mechanical failure, but some succumb within weeks of purchase, others not after a decade - it's just a matter of pot luck (which is why backups are so important). 

Stroller.

Re: [gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Fatih Tümen]

On Mon, Oct 11, 2010 at 3:33 PM, Stroller
<stroller@stellar.eclipse.co.uk> wrote:
>
> On 11 Oct 2010, at 12:51, Fatih Tümen wrote:
>> ...
>> P.S. Would you recommend against 7200rpm usb 2.5" disks?
>
> I'm aware of no reason to do so.
>
> Typically usb 2.5" disks can be powered off the USB cable, which is much more portable than the PSU required by external USB 3.5" drives.
>

Perhaps there a bit noisier and shortening battery life?

> I would guess that most drives are generally about as reliable as each other. They are inherently at risk from mechanical failure, but some succumb within weeks of purchase, others not after a decade - it's just a matter of pot luck (which is why backups are so important).
>

I would love to see a decade. This one could not make it 5, but the
other one I got is alive for 7 years.

--
    Fatih

Re: [gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1316 bytes --]

On Sunday 10 October 2010 04:58:04 Fatih Tümen wrote:
> On Sun, Oct 10, 2010 at 12:15 AM, walt <w41ter@gmail.com> wrote:

> > Will fdisk read and recognize the partition table on the USB disk? If
> > fdisk results in disk read errors then I'd begin to think more about
> > 'hardware' :(
> 
> No "Unable to read /dev/sda" is what fdisk says. I never had a disk
> (hardware) failure before. Is there no way to extract data from it?

The noise you're describing is indicative of mechanical failure.

Unless your PC can access the drive (dmesg will show what the kernel sees) 
then there is no easy way of getting the data out of it.

I have heard of people opening the USB enclosure of external drives and 
removing the drive, which they then installed in a laptop.  However, these 
were cases where the USB controller was faulty, rather than the moving 
elements of the drive itself.

If you had access to a forensics lab you could even take the platters out of 
the drive itself and read them on platter reader.  On the other hand, if you 
only had ccache, distfiles and packages a resync with a new external drive 
will get you a working system again.

Before you head for the shops you would at least want to try another USB cable 
as Walter suggested, just in case.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Fatih Tümen]

On Sun, Oct 10, 2010 at 1:01 PM, Mick <michaelkintzios@gmail.com> wrote:
> On Sunday 10 October 2010 04:58:04 Fatih Tümen wrote:
>> On Sun, Oct 10, 2010 at 12:15 AM, walt <w41ter@gmail.com> wrote:
>
>> > Will fdisk read and recognize the partition table on the USB disk? If
>> > fdisk results in disk read errors then I'd begin to think more about
>> > 'hardware' :(
>>
>> No "Unable to read /dev/sda" is what fdisk says. I never had a disk
>> (hardware) failure before. Is there no way to extract data from it?
>
> The noise you're describing is indicative of mechanical failure.
>

That I was fearing but I cant understand how it can fail all of a
sudden. I did not drop it or something. Just ran eix and boom. Would
you call it a coincidence of running eix with the best before date of
the disk?

> Unless your PC can access the drive (dmesg will show what the kernel sees)
> then there is no easy way of getting the data out of it.
>
> I have heard of people opening the USB enclosure of external drives and
> removing the drive, which they then installed in a laptop.  However, these
> were cases where the USB controller was faulty, rather than the moving
> elements of the drive itself.
>

I tried that to a friend laptop's dead drive. It Didt work. I am
afraid im in a similar situation here.

> If you had access to a forensics lab you could even take the platters out of
> the drive itself and read them on platter reader.  On the other hand, if you
> only had ccache, distfiles and packages a resync with a new external drive
> will get you a working system again.
>

I actually thought about that too. There is a forensic lab quite close
to me but I doubt that they would bother with this or whether it would
worth the effort.

> Before you head for the shops you would at least want to try another USB cable
> as Walter suggested, just in case.

I found the cable and tried. Same!
Anyway thanks for the suggestion.

[gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[walt]

On 10/10/2010 09:28 AM, Fatih Tümen wrote:

> That I was fearing but I cant understand how it can fail all of a
> sudden. I did not drop it or something. Just ran eix and boom...

My favorite disk failure story:  I made a backup copy of my boot
sector with 'dd if=/dev/hda of=bootblock.bak bs=512 count=1'.

That disk started giving hardware read/write errors immediately
after that, and never again booted successfully.

I was afraid to use dd for at least a year :/

Re: [gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[James Wall]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/10/2010 01:49 PM, walt wrote:
> On 10/10/2010 09:28 AM, Fatih Tümen wrote:
> 
>> That I was fearing but I cant understand how it can fail all of a
>> sudden. I did not drop it or something. Just ran eix and boom...
> 
> My favorite disk failure story:  I made a backup copy of my boot
> sector with 'dd if=/dev/hda of=bootblock.bak bs=512 count=1'.
> 
> That disk started giving hardware read/write errors immediately
> after that, and never again booted successfully.
> 
> I was afraid to use dd for at least a year :/
> 
> 
I recently had a drive from a computer that I had picked up and was told
that it probably had a virus slowing down Windoze. I started to back up
the drive before cleaning it up and discovered bad blocks all over the
drive. when scanning the surface with MHDD from sysresccd the drive
looked like swiss cheese with about 300 Uncorrectable bad blocks and the
bios on that machine would have warned if SMART wasn't turned off...

Too bad I hadn't heard of ddrescue. I might have been able to pull off
more data. :/


- -- 
No trees were harmed in the sending of this message. However, a large
number of electrons were terribly inconvenienced.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJMst4YAAoJEISPTA/exVD8ar4H/3YzX/5OitxNTIszUIXwolmy
o9viGXLVH8KLbrzvk8nMq5YzjUPkKQ6h9WDGS0zuXhesIP2OqoWYeDHXHYVcou8z
i6kXwBld+eOODZnSbHUgyji00uSYyy0YqhkN2QHzc1+FbSGs8x+JV/h0Hje+bX+H
n0PhvnUCJeBNQZ6KvaZ0SRe50RqJ3rWJL/Qm8mCY0bS7g6bE1r7r6jxHordpXlOR
Wm8oAi6TYR/do9IfYnGyqYROMh21hQ4Fj6YYDKqeIFsNNjY0J7ElO2TSLDjwrk2D
nAWn+AhNhJnR40yqoECgbz3QE3PN/zmrZoaRWKT2qmg3+k46OjAwfPU7mp5pvtY=
=PJoA
-----END PGP SIGNATURE-----

Re: [gentoo-user] Re: USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Stroller]

On 10 Oct 2010, at 17:28, Fatih Tümen wrote:
>> ...
>> The noise you're describing is indicative of mechanical failure.
> 
> That I was fearing but I cant understand how it can fail all of a
> sudden. I did not drop it or something. Just ran eix and boom. Would
> you call it a coincidence of running eix with the best before date of
> the disk?

Total coincidence. It has nothing to do with eix - you'll likely be running something on the drive when it fails, that's not what causes the problem.

Most hard-drive failures have nothing to do with being dropped. It's simply that hard-drives spin at 5,000 - 10,000 rpm, about the same speed as a car engine, but unlike a car engine they don't have an oil pump and a radiator and all that stuff to lubricate them.

Hard-drives are simply prone to mechanical failure - wearing out, in other words,

> There is a forensic lab quite close
> to me but I doubt that they would bother with this or whether it would
> worth the effort.

They would probably bother if you paid them enough. I would probably consider $500 cheap, and might well expect to pay twice or several times that. In the cases of clicking drives I've had quite some success with ddrescue for no cost.

Stroller.

Re: [gentoo-user] USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Paul Hartman]

2010/10/9 Fatih Tümen <fthtmn+gentoo@gmail.com>:
> Hi,
>
> When I ran eix hdf command, all of a sudden my usb drive started
> making weird noises. I only have ccache, distfiles and packaes
> directories on sda2, the usb disk partition. I don't know why eix
> waked up the disk. Eix hung there non-responding for a moment as the
> disk kept making noises, so I interrupted the task. Immediately
> checked the logs[0] and umounted the device as a reflex.

Hi,

I recently had USB external hdd that started to make clicking noises
and beeping sounds and I couldn't access it at all anymore. I thought
"oh no, click of death"... but I also noticed very faint high-pitch
sound coming from the power supply. I contacted the hdd manufacturer
and they sent me a new power supply for free. Everything worked
perfectly after replacing it.

In the past, with the same drive in fact, I also had problem with the
USB link dropping, which was causing disk corruption. I tried a
different USB cable but same problem persisted. Who knows if this was
also caused by the bad power supply, or USB hub overload on my
computer. I had about 10 USB devices attached at the time. I removed
some and moved around to spread the load out a bit and it worked fine
after that.

Since replacing the power supply, I've used the same hdd with 2 other
computers and haven't have any issues so far.

FWIW

Re: [gentoo-user] USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Daniel da Veiga]

On Tue, Oct 12, 2010 at 13:41, Paul Hartman
<paul.hartman+gentoo@gmail.com> wrote:
> 2010/10/9 Fatih Tümen <fthtmn+gentoo@gmail.com>:
>> Hi,
>>
>> When I ran eix hdf command, all of a sudden my usb drive started
>> making weird noises. I only have ccache, distfiles and packaes
>> directories on sda2, the usb disk partition. I don't know why eix
>> waked up the disk. Eix hung there non-responding for a moment as the
>> disk kept making noises, so I interrupted the task. Immediately
>> checked the logs[0] and umounted the device as a reflex.
>
> Hi,
>
> I recently had USB external hdd that started to make clicking noises
> and beeping sounds and I couldn't access it at all anymore. I thought
> "oh no, click of death"... but I also noticed very faint high-pitch
> sound coming from the power supply. I contacted the hdd manufacturer
> and they sent me a new power supply for free. Everything worked
> perfectly after replacing it.
>
> In the past, with the same drive in fact, I also had problem with the
> USB link dropping, which was causing disk corruption. I tried a
> different USB cable but same problem persisted. Who knows if this was
> also caused by the bad power supply, or USB hub overload on my
> computer. I had about 10 USB devices attached at the time. I removed
> some and moved around to spread the load out a bit and it worked fine
> after that.
>
> Since replacing the power supply, I've used the same hdd with 2 other
> computers and haven't have any issues so far.
>

Also had PSU problems with external drives a while ago, I asked a
friend to modidy a full ATX computer PSU for me so it could power two
drives, never had problems again (the psu that comes with those things
is just too cheap, tend to overheat and fail a lot).

I never use 2.5 HDD USB enclosures for constant workload with no
cooling at all (most cases for 2.5 drives have no cooler and rely on
heat transfer from an aluminum body, wich is simply unreliable).

On the other hand, I had a new, cooled 3.5 HDD fail on me after two
days operation. It was promptly replaced by Seagate. The dread click
of death... Of course I tested it on a SATA controller before calling
it dead.

Funny story. I had one drive that failed once (clicking) and I read
somewhere to "cool" it. So I put the damn thing on the refrigerator,
took it out after a while (it was so cold!), plugged in, and what the
heck, it started working again and I was able to backup all of the
data. After that it worked for a long time before failing again, lol.
Now I always "cool" a clicking drive before replacing it. True story.

-- 
Daniel da Veiga

Re: [gentoo-user] USB Disk failure - Buffer I/O error on device sda2, logical block 1289 lost page write due to I/O error on sda2

[Alan McKinnon]

Apparently, though unproven, at 03:13 on Friday 15 October 2010, Daniel da 
Veiga did opine thusly:

> Funny story. I had one drive that failed once (clicking) and I read
> somewhere to "cool" it. So I put the damn thing on the refrigerator,
> took it out after a while (it was so cold!), plugged in, and what the
> heck, it started working again and I was able to backup all of the
> data. After that it worked for a long time before failing again, lol.
> Now I always "cool" a clicking drive before replacing it. True story.

Another completely off-topic funny story:

I used to fix TVs a long time ago. Putting the TV in a freezer to find heat-
sensitive faults was reasonably common. Customers would think I was nuts 
hauling a set out the freezer and sticking it on the bench....

Then they started making those gigantic sets that don't fit into freezers; 
cold rooms maybe but not freezers. Yet another diagnostic technique that went 
the way of the dinosaur...

-- 
alan dot mckinnon at gmail dot com