hard disk errors on boot up
in [Suse]
|
Prev: libwx_baseu-2.6.so.0
Next: CODEC32 installation error
From: David Cowie on 10 Nov 2005 13:09 I sometimes see disk errors reported when I turn my PC on. Here's a typical one: ReiserFS: warning: is_tree_node: node level 13079 does not match to the extended one 2 ReiserFS:hdc2: warning: vs-5150: search_by_key: invalid format found in block 7012460: Fsck? ReiserFS:hdc2:warning: vs-13070: reiserfs_read_locked_inode: i/o failure occurred trying to find start data of [49164 49163 0x 0 SD] followed a few lines later by hdc: dma_timer_expiry : dma status == 0x61 dma timeout error: status = 0x58 followed by the boot process freezing. I've run reiserfsck --check twice so far, on different days, with no errors reported each time. If the boot freezes, a reboot will start the PC up without hanging (so far). Two questions: 1) what do the reiserfs warnings mean? If google knows the answer, I don't know the question. 2) am I going to have to get a new hard disk, and sooner rather than later? I'm running SuSE 10, on an upgrade installation from 9.2 -- David Cowie Containment Failure + 17449:08
From: ray on 10 Nov 2005 16:40 On Thu, 10 Nov 2005 18:09:16 +0000, David Cowie wrote: > I sometimes see disk errors reported when I turn my PC on. > > Here's a typical one: > ReiserFS: warning: is_tree_node: node level 13079 does not match to the > extended one 2 > ReiserFS:hdc2: warning: vs-5150: search_by_key: invalid format found in > block 7012460: Fsck? > ReiserFS:hdc2:warning: vs-13070: reiserfs_read_locked_inode: i/o failure > occurred trying to find start data of [49164 49163 0x 0 SD] > > followed a few lines later by > > hdc: dma_timer_expiry : dma status == 0x61 > dma timeout error: status = 0x58 > > followed by the boot process freezing. > > I've run reiserfsck --check twice so far, on different days, with no > errors reported each time. > If the boot freezes, a reboot will start the PC up without hanging (so far). > > Two questions: > 1) what do the reiserfs warnings mean? If google knows the answer, I don't > know the question. > 2) am I going to have to get a new hard disk, and sooner rather than > later? > > I'm running SuSE 10, on an upgrade installation from 9.2 I suggest you run 'badblocks' to see if you have a hard drive going south.
From: Lars Ljung on 10 Nov 2005 16:57 David Cowie <me(a)privacy.net> writes: > hdc: dma_timer_expiry : dma status == 0x61 > dma timeout error: status = 0x58 It could be a problem with the IDE/SCSI driver, is your chipset fully supported by Linux? Some hdparm settings can also cause errors like this. -- Lars
From: David Cowie on 11 Nov 2005 12:24 On Thu, 10 Nov 2005 14:40:59 -0700, ray wrote: > I suggest you run 'badblocks' to see if you have a hard drive going south. Does badblocks support reiserfs? I had a look at the manpage, and it only referred to e2fs. -- David Cowie Containment Failure + 17472:47
From: Gordon Henderson on 11 Nov 2005 13:31
In article <pan.2005.11.11.17.24.14.461921(a)privacy.net>, David Cowie <me(a)privacy.net> wrote: >On Thu, 10 Nov 2005 14:40:59 -0700, ray wrote: > >> I suggest you run 'badblocks' to see if you have a hard drive going south. > >Does badblocks support reiserfs? I had a look at the manpage, and it only >referred to e2fs. Badblocks runs on a partition and doesn't really care what the underlying filesystem is. It can generate a badblock list for input to mke2fs, but lets face it, if you have bad blocks that badblocks reports, throw the disk in the bin and buy a new one (or warranty repair, but you get the jist!) Gordon |