Oops when creating software RAID device (2.6.16.14).
I'm trying to set up a Linux software RAID over 12 disks. As mdadm is creating the array it appears that a drive is flaking out (if anybody can provide a layman's explanation for what is being complained about, I'd very much appreciate it). Now, since this is a RAID device I would expect the md driver to simply discard this device, add the remainder and leave me with a degraded array. No such luck, though.
Full log: http://www.wirschell.nl/boot.log
Relevant section with oops:
ATA: abnormal status 0x58 on port 0xF88A211C
ata7: PIO error
ATA: abnormal status 0x58 on port 0xF88A211C
ata7: translated ATA stat/err 0x58/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata7: status=0x58 { DriveReady SeekComplete DataRequest }
ATA: abnormal status 0x58 on port 0xF88A211C
ATA: abnormal status 0x58 on port 0xF88A211C
ATA: abnormal status 0x58 on port 0xF88A211C
ATA: abnormal status 0x58 on port 0xF88A211C
ata7: Entering mv_eng_timeoutmmio_base f8880000 ap dfe942a4 qc dfe94770 scsi_cmnd f7741080 &cmnd f77410c4 ata7: status=0x50 { DriveReady SeekComplete }
ata7: error=0x01 { AddrMarkNotFound }
sdc: Current: sense key=0x0
ASC=0x0 ASCQ=0x0 Assertion failed! qc != NULL,drivers/scsi/libata-core.c,ata_pio_poll,line=3017 Assertion failed! qc != NULL,drivers/scsi/libata-core.c,ata_pio_block,line=3474 Unable to handle kernel NULL pointer dereference at virtual address 00000014 printing eip: c02e47b7 *pde = 00000000 Oops: 0000 [#1] SMP Modules linked in: raid5 md_mod xor e1000 intel_agp agpgart CPU: 0 EIP: 0060:[<c02e47b7>] Not tainted VLI EFLAGS: 00010246 (2.6.16.14 #1)
EIP is at ata_pio_task+0xf2/0x6a1
eax: 00000053 ebx: 00000050 ecx: 00000010 edx: 00000050
esi: 00000002 edi: 00000000 ebp: 00000212 esp: c1a8df34
ds: 007b es: 007b ss: 0068
Process ata/0 (pid: 389, threadinfo=c1a8c000 task=dff1c580)
Stack: <0>00000000 dff1c6a8 dff1c580 c0424100 c1807560 c7562b80 0098966b 00000000 dfe94850 dfe94850 dfe94854 dfd84c40 00000212 c0125ff4 dfe942a4 c02e46c5 dfe942a4 dfd84c4c dfd84c40 dfd84c54 c01260bb c012619b 00000001 00000000 Call Trace: [<c0125ff4>] run_workqueue+0x78/0xb6 [<c02e46c5>] ata_pio_task+0x0/0x6a1 [<c01260bb>] worker_thread+0x0/0x111 [<c012619b>] worker_thread+0xe0/0x111 [<c01152a3>] default_wake_function+0x0/0x15 [<c0128bcb>] kthread+0xa5/0xd2 [<c0128b26>] kthread+0x0/0xd2 [<c0100bf5>] kernel_thread_helper+0x5/0xb Code: 56 e3 ff 83 c4 14 0f b6 d3 f6 c2 21 74 1a 83 8f 8c 00 00 00 02 8b
54 24 38 c7 82 dc 05 00 00 07 00 00 00 e9 18 ff ff ff 8d 4f 10 <8a> 41 04 83 e8 05 3c 02 0f 87 c0 01 00 00 80 e2 08 75 13 8b 4c <3>md: invalid raid superblock magic on sdc2 md: sdc2 has invalid sb, not importing!
md: md_import_device returned -22
Interestingly enough, this problem is entirely reproducable, however so far each time a different disk was being complained about. Is there something I should know about the WD200JB drives?
Hardware this is happening on:
Intel P4 3.0GHz CPU
ASUS PSCH-L Mobo (E7210 + 6300ESB)
Promise FastTrak S150 TX4 onboard, unused.
SuperMicro AOC-SAT2-MV8 SATA controller card (Marvell 88SX6081 chip) 2x Western Digital WD2000JB 200 GB PATA drives
9x Western Digital WD2000JD 200 GB SATA drives
If anybody has any insights at so what I can or should do now to resolve this issue, I'm all ears.
I'm not subscribed to LKML, so please CC me in any replies.
Thank you.
Kind regards,
Tom Wirschell
Quoted 10 lines · Tom Wirschell
I'm trying to set up a Linux software RAID over 12 disks. As mdadm is creating the array it appears that a drive is flaking out (if anybody can provide a layman's explanation for what is being complained about, I'd very much appreciate it). Now, since this is a RAID device I would expect the md driver to simply discard this device, add the remainder and leave me with a degraded array. No such luck, though.
Full log: http://www.wirschell.nl/boot.log
Relevant section with oops:
ata_pio_task() oopsed. Added linux-ide to CC.
ISTR others hitting this recently.
Quoted 77 lines
ATA: abnormal status
0x58on port0xF88A211C
ata7: PIO error
ATA: abnormal status0x58on port0xF88A211C
ata7: translated ATA stat/err 0x58/00 to SCSI SK/ASC/ASCQ 0xb/47/00
ata7: status=0x58 { DriveReady SeekComplete DataRequest }
ATA: abnormal status0x58on port0xF88A211C
ATA: abnormal status0x58on port0xF88A211C
ATA: abnormal status0x58on port0xF88A211C
ATA: abnormal status0x58on port0xF88A211C
ata7: Enteringmv_eng_timeoutmmio_basef8880000apdfe942a4qcdfe94770scsi_cmndf7741080&cmndf77410c4ata7: status=0x50 { DriveReady SeekComplete }
ata7: error=0x01 { AddrMarkNotFound }
sdc: Current: sense key=0x0ASC=0x0 ASCQ=0x0 Assertion failed! qc != NULL,drivers/scsi/libata-core.c,ata_pio_poll,line=3017 Assertion failed! qc != NULL,drivers/scsi/libata-core.c,ata_pio_block,line=3474 Unable to handle kernel NULL pointer dereference at virtual address 00000014 printing eip: c02e47b7 *pde = 00000000 Oops: 0000 [#1] SMP Modules linked in: raid5 md_mod xor e1000 intel_agp agpgart CPU: 0 EIP: 0060:[<c02e47b7>] Not tainted VLI EFLAGS: 00010246 (2.6.16.14 #1)EIP is at
ata_pio_task+0xf2/0x6a1
eax: 00000053 ebx: 00000050 ecx: 00000010 edx: 00000050
esi: 00000002 edi: 00000000 ebp: 00000212 esp:c1a8df34
ds: 007b es: 007b ss: 0068
Process ata/0 (pid: 389, threadinfo=c1a8c000 task=dff1c580)Stack: <0>00000000 dff1c6a8 dff1c580 c0424100 c1807560 c7562b80 0098966b 00000000 dfe94850 dfe94850 dfe94854 dfd84c40 00000212 c0125ff4 dfe942a4 c02e46c5 dfe942a4 dfd84c4c dfd84c40 dfd84c54 c01260bb c012619b 00000001 00000000 Call Trace: [<c0125ff4>] run_workqueue+0x78/0xb6 [<c02e46c5>] ata_pio_task+0x0/0x6a1 [<c01260bb>] worker_thread+0x0/0x111 [<c012619b>] worker_thread+0xe0/0x111 [<c01152a3>] default_wake_function+0x0/0x15 [<c0128bcb>] kthread+0xa5/0xd2 [<c0128b26>] kthread+0x0/0xd2 [<c0100bf5>] kernel_thread_helper+0x5/0xb Code: 56 e3 ff 83 c4 14 0f b6 d3 f6 c2 21 74 1a 83 8f 8c 00 00 00 02 8b54 24 38 c7 82 dc 05 00 00 07 00 00 00 e9 18 ff ff ff 8d 4f 10 <8a> 41 04 83 e8 05 3c 02 0f 87 c0 01 00 00 80 e2 08 75 13 8b 4c <3>md: invalid raid superblock magic on sdc2 md: sdc2 has invalid sb, not importing!
md:md_import_devicereturned -22Interestingly enough, this problem is entirely reproducable, however so far each time a different disk was being complained about. Is there something I should know about the WD200JB drives?
Hardware this is happening on:
Intel P4 3.0GHz CPU
ASUS PSCH-L Mobo (E7210 + 6300ESB)
Promise FastTrak S150 TX4 onboard, unused.
SuperMicro AOC-SAT2-MV8 SATA controller card (Marvell 88SX6081 chip) 2x Western Digital WD2000JB 200 GB PATA drives
9x Western Digital WD2000JD 200 GB SATA drivesIf anybody has any insights at so what I can or should do now to resolve this issue, I'm all ears.
I'm not subscribed to LKML, so please CC me in any replies.
Thank you.
Kind regards,
Tom Wirschell
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Quoted 4 lines · Andrew Morton
ata_pio_task()oopsed. Added linux-ide to CC.ISTR others hitting this recently.
I upgraded to 2.6.17-rc5-mm2 and dispite a small BUG being reported at boot by the Marvell SATA driver I was able to create the array and use it. I'm still testing this setup, but so far it seems to work nicely.
I'll send the maintainer of the Marvell SATA driver the BUG message.
Thanks again.
Kind regards,
Tom Wirschell
I'm not subscribed to LKML or linux-ide, so please CC me in any replies.
Signature · 4 lines
A small child once asked me why people cant be nicer and just love one another. I pondered this for but a moment and I then, of course, ate the small child. He was very tangy and did NOT taste like chicken. - Lenore 2 -