Re: [gentoo-user] hd problem
Le Lundi 8 Septembre 2003 17:18, Christian Schäfer a écrit : > >> First, backup the data on hda. Then, try a different IDE cable. If that > >> doesn't work, try putting a spare drive (if you have one) on that > >> particular cable in place of the screwy one. If it still acts up then > >> its the controller. If you plug the IDE cable directly into the > >> motherboard, your motherboard is dying. > > > > I got a disk in hdb, same cable, same controller. Can I conclude the > > cable and the controller are ok? > > And what does 2xbeep means in BIOS? I searched in the error codes but > > couldn't find it. (I've got an asus7v) > > a little while ago I encountered similar problems on an asus board. > those were caused by faulty ram. in my case replacing the ram fixed > things. strangly enough that the error encountered on the harddrive.. everything has been fine for almost three years now. I'll run to the next hd shop and try a new disk. I've enabled auto.suspend for hd in bios. Could my HD be dead because it doesn't support to be constantly spinning on and off? -- mathieu -- [EMAIL PROTECTED] mailing list
Re[2]: [gentoo-user] hd problem
hi mathieu, Monday, September 8, 2003, 5:16:23 PM, you wrote: >> First, backup the data on hda. Then, try a different IDE cable. If that >> doesn't work, try putting a spare drive (if you have one) on that >> particular cable in place of the screwy one. If it still acts up then >> its the controller. If you plug the IDE cable directly into the >> motherboard, your motherboard is dying. > I got a disk in hdb, same cable, same controller. Can I conclude the cable and > the controller are ok? > And what does 2xbeep means in BIOS? I searched in the error codes but couldn't > find it. (I've got an asus7v) a little while ago I encountered similar problems on an asus board. those were caused by faulty ram. in my case replacing the ram fixed things. strangly enough that the error encountered on the harddrive.. gruss /Christian mailto:[EMAIL PROTECTED] --- I propose that the following character sequence for joke markers: :-) 19-Sep-82 11:44Scott E Fahlman -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] hd problem
> First, backup the data on hda. Then, try a different IDE cable. If that > doesn't work, try putting a spare drive (if you have one) on that > particular cable in place of the screwy one. If it still acts up then > its the controller. If you plug the IDE cable directly into the > motherboard, your motherboard is dying. I got a disk in hdb, same cable, same controller. Can I conclude the cable and the controller are ok? And what does 2xbeep means in BIOS? I searched in the error codes but couldn't find it. (I've got an asus7v) -- mathieu perrenoud -- [EMAIL PROTECTED] mailing list
Re: [gentoo-user] hd problem
mathieu wrote:
Yesterday afternoon, my box started to emit beeps:
... 30 sec silence ...... etc...
And hda was gone.
After a reboot, all went fine again.
And today, while emerging, the following message appeared on the console:
maison kernel: journal-601, buffer write failed
emerging continued, no problem. but all my other shells got stucked. I
couldn't open new sshells.
I'm away from my computer, so I don't know if it's beeping.
hda being /home, I tried to log in my box as root. worked. and here is what I
found in /var/log/kern.log
- - kern.log snip - -
Sep 8 13:35:37 maison kernel: hda: timeout waiting for DMA
Sep 8 13:35:37 maison kernel: ide_dmaproc: chipset supported ide_dma_timeout
func only: 14
Sep 8 13:35:37 maison kernel: blk: queue c01723c4, I/O limit 4095Mb (mask
0x)
Sep 8 14:48:14 maison kernel: hda: timeout waiting for DMA
Sep 8 14:48:14 maison kernel: ide_dmaproc: chipset supported ide_dma_timeout
func only: 14
Sep 8 14:48:14 maison kernel: hda: status timeout: status=0xd0 { Busy }
Sep 8 14:48:14 maison kernel: hdb: DMA disabled
Sep 8 14:48:14 maison kernel: hda: drive not ready for command
Sep 8 14:48:49 maison kernel: ide0: reset timed-out, status=0x80
Sep 8 14:48:49 maison kernel: hda: status timeout: status=0x80 { Busy }
Sep 8 14:48:49 maison kernel: hda: drive not ready for command
Sep 8 14:49:19 maison kernel: ide0: reset timed-out, status=0x80
Sep 8 14:49:19 maison kernel: end_request: I/O error, cmd 1 dev 03:07 (hda),
sector 43744
Sep 8 14:49:19 maison kernel: end_request: I/O error, cmd 1 dev 03:07 (hda),
sector 43752
Sep 8 14:49:19 maison kernel: end_request: I/O error, cmd 1 dev 03:07 (hda),
sector 43760
Sep 8 14:49:19 maison kernel: journal-601, buffer write failed
Sep 8 14:49:19 maison kernel: kernel BUG at prints.c:334!
Sep 8 14:49:19 maison kernel: invalid operand:
Sep 8 14:49:19 maison kernel: CPU:0
Sep 8 14:49:19 maison kernel: EIP:0010:[xfs_bmap_alloc+5124/5312]
Tainted: P
Sep 8 14:49:19 maison kernel: EIP:0010:[]Tainted: P
Sep 8 14:49:19 maison kernel: EFLAGS: 00010282
Sep 8 14:49:19 maison kernel: eax: 0024 ebx: c1e82c00 ecx: 0001
edx: cd461f7c
Sep 8 14:49:19 maison kernel: esi: edi: 0003 ebp: c1e82c00
esp: dffe3ec0
Sep 8 14:49:19 maison kernel: ds: 0018 es: 0018 ss: 0018
Sep 8 14:49:19 maison kernel: Process kupdated (pid: 8, stackpage=dffe3000)
Sep 8 14:49:19 maison kernel: Stack: c0361f92 c0159280 0003 e0b79234
c024509a c1e82c00 c03709c0 1000
Sep 8 14:49:19 maison kernel:0307 0006 0004
ca799840 003b 0004
Sep 8 14:49:19 maison kernel:0002 c0248ff8 c1e82c00 e0b79234
0001 0006 e0b81388 0004
Sep 8 14:49:19 maison kernel: Call Trace:[xfs_buf_item_unpin+38/116]
[xfs_dir_createname+440/448] [xfs_da_do_buf+1053/1840]
[xfs_bmap_add_extent_delay_real+2428/4060] [do_quotactl+438/704]
Sep 8 14:49:19 maison kernel: Call Trace:[] []
[] [] []
Sep 8 14:49:19 maison kernel: [__constant_c_and_count_memset+84/136]
[getxattr+165/248] [do_vm86_irq_handling+50/720] [sys_fsetxattr+20/64]
Sep 8 14:49:19 maison kernel: [] [] []
[]
Sep 8 14:49:19 maison kernel:
Sep 8 14:49:19 maison kernel: Code: 0f 0b 4e 01 de 63 36 c0 85 db 74 0e 0f b7
43 08 89 04 24 e8
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018424
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018432
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018440
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018448
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018456
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018464
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018472
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018480
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018488
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018496
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018504
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018424
Sep 8 15:04:35 maison kernel: end_request: I/O error, cmd 1 dev 03:05 (hda),
sector 11384
Sep 8 15:04:35 maison kernel: end_request: I/O error, cmd 1 dev 03:05 (hda),
sector 11392
Sep 8 15:04:35 maison kernel: end_request: I/O error, cmd 1 dev 03:05 (hda),
sector 11400
Sep 8 15:04:35 maison kernel: end_request: I/O error, cmd 1 dev 03:05 (hda),
sector 11408
Sep 8 15:04:35 maison kernel: end_request: I/O error, cmd 1 dev 03:05 (hda),
sector 11416
Sep 8 15:04:35 maison kernel: end_request: I/O error, cmd 1
Re: [gentoo-user] hd problem
On Monday 08 September 2003 13:35, mathieu wrote: > > Is my HD screwed? Yes > Could it be gentoo's fault? No >What can I do, beside cry for my lost datas and buy a new hd? After a backup, get some harddisk tool from the vendor. The error messages of this tools shut up all knowing and unsupportive costumer support ;o) Glück Auf Volker -- Conclusions In a straight-up fight, the Empire squashes the Federation like a bug. Even with its numerical advantage removed, the Empire would still squash the Federation like a bug. Accept it. -Michael Wong -- [EMAIL PROTECTED] mailing list
[gentoo-user] hd problem
Yesterday afternoon, my box started to emit beeps:
... 30 sec silence ...... etc...
And hda was gone.
After a reboot, all went fine again.
And today, while emerging, the following message appeared on the console:
maison kernel: journal-601, buffer write failed
emerging continued, no problem. but all my other shells got stucked. I
couldn't open new sshells.
I'm away from my computer, so I don't know if it's beeping.
hda being /home, I tried to log in my box as root. worked. and here is what I
found in /var/log/kern.log
- - kern.log snip - -
Sep 8 13:35:37 maison kernel: hda: timeout waiting for DMA
Sep 8 13:35:37 maison kernel: ide_dmaproc: chipset supported ide_dma_timeout
func only: 14
Sep 8 13:35:37 maison kernel: blk: queue c01723c4, I/O limit 4095Mb (mask
0x)
Sep 8 14:48:14 maison kernel: hda: timeout waiting for DMA
Sep 8 14:48:14 maison kernel: ide_dmaproc: chipset supported ide_dma_timeout
func only: 14
Sep 8 14:48:14 maison kernel: hda: status timeout: status=0xd0 { Busy }
Sep 8 14:48:14 maison kernel: hdb: DMA disabled
Sep 8 14:48:14 maison kernel: hda: drive not ready for command
Sep 8 14:48:49 maison kernel: ide0: reset timed-out, status=0x80
Sep 8 14:48:49 maison kernel: hda: status timeout: status=0x80 { Busy }
Sep 8 14:48:49 maison kernel: hda: drive not ready for command
Sep 8 14:49:19 maison kernel: ide0: reset timed-out, status=0x80
Sep 8 14:49:19 maison kernel: end_request: I/O error, cmd 1 dev 03:07 (hda),
sector 43744
Sep 8 14:49:19 maison kernel: end_request: I/O error, cmd 1 dev 03:07 (hda),
sector 43752
Sep 8 14:49:19 maison kernel: end_request: I/O error, cmd 1 dev 03:07 (hda),
sector 43760
Sep 8 14:49:19 maison kernel: journal-601, buffer write failed
Sep 8 14:49:19 maison kernel: kernel BUG at prints.c:334!
Sep 8 14:49:19 maison kernel: invalid operand:
Sep 8 14:49:19 maison kernel: CPU:0
Sep 8 14:49:19 maison kernel: EIP:0010:[xfs_bmap_alloc+5124/5312]
Tainted: P
Sep 8 14:49:19 maison kernel: EIP:0010:[]Tainted: P
Sep 8 14:49:19 maison kernel: EFLAGS: 00010282
Sep 8 14:49:19 maison kernel: eax: 0024 ebx: c1e82c00 ecx: 0001
edx: cd461f7c
Sep 8 14:49:19 maison kernel: esi: edi: 0003 ebp: c1e82c00
esp: dffe3ec0
Sep 8 14:49:19 maison kernel: ds: 0018 es: 0018 ss: 0018
Sep 8 14:49:19 maison kernel: Process kupdated (pid: 8, stackpage=dffe3000)
Sep 8 14:49:19 maison kernel: Stack: c0361f92 c0159280 0003 e0b79234
c024509a c1e82c00 c03709c0 1000
Sep 8 14:49:19 maison kernel:0307 0006 0004
ca799840 003b 0004
Sep 8 14:49:19 maison kernel:0002 c0248ff8 c1e82c00 e0b79234
0001 0006 e0b81388 0004
Sep 8 14:49:19 maison kernel: Call Trace:[xfs_buf_item_unpin+38/116]
[xfs_dir_createname+440/448] [xfs_da_do_buf+1053/1840]
[xfs_bmap_add_extent_delay_real+2428/4060] [do_quotactl+438/704]
Sep 8 14:49:19 maison kernel: Call Trace:[] []
[] [] []
Sep 8 14:49:19 maison kernel: [__constant_c_and_count_memset+84/136]
[getxattr+165/248] [do_vm86_irq_handling+50/720] [sys_fsetxattr+20/64]
Sep 8 14:49:19 maison kernel: [] [] []
[]
Sep 8 14:49:19 maison kernel:
Sep 8 14:49:19 maison kernel: Code: 0f 0b 4e 01 de 63 36 c0 85 db 74 0e 0f b7
43 08 89 04 24 e8
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018424
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018432
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018440
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018448
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018456
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018464
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018472
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018480
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018488
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018496
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018504
Sep 8 15:00:00 maison kernel: end_request: I/O error, cmd 0 dev 03:06 (hda),
sector 1018424
Sep 8 15:04:35 maison kernel: end_request: I/O error, cmd 1 dev 03:05 (hda),
sector 11384
Sep 8 15:04:35 maison kernel: end_request: I/O error, cmd 1 dev 03:05 (hda),
sector 11392
Sep 8 15:04:35 maison kernel: end_request: I/O error, cmd 1 dev 03:05 (hda),
sector 11400
Sep 8 15:04:35 maison kernel: end_request: I/O error, cmd 1 dev 03:05 (hda),
sector 11408
Sep 8 15:04:35 maison kernel: end_request: I/O error, cmd 1 dev 03:05 (hda),
sector 11416
Sep 8 15:04:35 maison kernel: end_request: I/O error, cmd 1 dev 03:05 (hda)
Re: [gentoo-user] hd problem
Looks like the drive is not responding which means the drive or controller is dying and Gentoo wouldn't do that. If you backup up your data you don't have to cry . On Mon, 8 Sep 2003 15:35:28 +0200 mathieu <[EMAIL PROTECTED]> wrote: Yesterday afternoon, my box started to emit beeps: ... 30 sec silence ...... etc... And hda was gone. After a reboot, all went fine again. And today, while emerging, the following message appeared on the console: maison kernel: journal-601, buffer write failed emerging continued, no problem. but all my other shells got stucked. I couldn't open new sshells. I'm away from my computer, so I don't know if it's beeping. hda being /home, I tried to log in my box as root. worked. and here is what I Is my HD screwed? Could it be gentoo's fault? What can I do, beside cry for my lost datas and buy a new hd? -- mathieu perrenoud -- [EMAIL PROTECTED] mailing list -- [EMAIL PROTECTED] mailing list
