Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have a raid1 array in a customer server which is degraded every time the system is booted. I use raid1 on others servers, with the same distribution (Fedora 8), and this problem doesn´t happens in other installations.
Both partitions in the raid1 array are marked as type 'fd - Linux raid autodetect'
I have smartd monitoring both hd´s, and there are no problems reported, so i´m pretty sure they are ok.
Do someone have a clue about what could be happening or where should i look?
Regards,
Fabiano
[root@server1-sp /]# fdisk -l
Disk /dev/sda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xd678d678
Device Boot Start End Blocks Id System
/dev/sda1 * 1 18947 152191746 fd Linux raid autodetect
/dev/sda2 18948 19457 4096575 82 Linux swap / Solaris
Disk /dev/sdb: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0001e277
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 18947 152191746 fd Linux raid autodetect
/dev/sdb2 18948 19457 4096575 82 Linux swap / Solaris
Disk /dev/md0: 155.8 GB, 155844280320 bytes
2 heads, 4 sectors/track, 38047920 cylinders
Units = cylinders of 8 * 512 = 4096 bytes
Disk identifier: 0x00000000
Disk /dev/md0 doesn't contain a valid partition table
md: md0 stopped.
md: bind<sda1>
md: bind<sdb1>
md: kicking non-fresh sda1 from array!
md: unbind<sda1>
md: export_rdev(sda1)
raid1: raid set md0 active with 1 out of 2 mirrors
ata3.00: error: { UNC }
ata3.00: configured for UDMA/133
sd 2:0:0:0: [sda] Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE,SUGGEST_OK
sd 2:0:0:0: [sda] Sense Key : Medium Error [current] [descriptor]
Descriptor sense data with sense descriptors (in hex):
72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
11 dd 14 0f
sd 2:0:0:0: [sda] Add. Sense: Unrecovered read error - auto reallocate failed
end_request: I/O error, dev sda, sector 304383551
printk: 4 messages suppressed.
Buffer I/O error on device sda1, logical block 76095872
ata3: EH complete
sd 2:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
sd 2:0:0:0: [sda] 312581808 512-byte hardware sectors (160042 MB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] Mode Sense: 00 3a 00 00
sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
ata3.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
And i have this message from 'smartctl':
Error 71 occurred at disk power-on lifetime: 0 hours (0 days + 0 hours)
When the command that caused the error occurred, the device was in an unknown state.
After command completion occurred, registers were:
ER ST SC SN CL CH DH
-- -- -- -- -- -- --
00 00 00 00 00 00 00
Commands leading to the command that caused the error were:
CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
-- -- -- -- -- -- -- -- ---------------- --------------------
00 00 00 00 00 fd 00 00 00:00:00.000 NOP [Abort queued commands]
00 00 7f ff 00 00 00 00 00:00:00.000 NOP [Abort queued commands]
00 00 00 00 00 00 00 00 00:00:20.736 NOP [Abort queued commands]
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.