LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Server
User Name
Password
Linux - Server This forum is for the discussion of Linux Software used in a server related context.

Notices

Reply
 
Search this Thread
Old 01-14-2009, 05:27 AM   #1
personalsoft_fabiano
LQ Newbie
 
Registered: Jan 2009
Posts: 3

Rep: Reputation: 0
raid1 degraded after every boot


Hi all,

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 doesnt happens in other installations.

Both partitions in the raid1 array are marked as type 'fd - Linux raid autodetect'

I have smartd monitoring both hds, and there are no problems reported, so im 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
 
Old 01-14-2009, 05:36 AM   #2
acid_kewpie
Moderator
 
Registered: Jun 2001
Location: UK
Distribution: Gentoo, RHEL, Fedora, Centos
Posts: 43,378

Rep: Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963Reputation: 1963
check dmesg / /var/log/messages for details of what happened when the array was attempted to be started.
 
Old 01-15-2009, 02:36 PM   #3
personalsoft_fabiano
LQ Newbie
 
Registered: Jan 2009
Posts: 3

Original Poster
Rep: Reputation: 0
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
 
Old 01-15-2009, 03:52 PM   #4
bzyk
Member
 
Registered: Jun 2007
Location: Poland
Distribution: Debian, Slackware
Posts: 42

Rep: Reputation: 15
mdadm /dev/md0 -a /dev/sda1
and then check this by;
mdadm -D /dev/md0
 
Old 01-17-2009, 04:19 AM   #5
personalsoft_fabiano
LQ Newbie
 
Registered: Jan 2009
Posts: 3

Original Poster
Rep: Reputation: 0
I have this messages from 'dmesg':

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]



Do someone know what is it saying?
 
  


Reply

Tags
degraded, mirroring, raid


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Degraded raid1 array problem on slack 12.0.0 / mdadm slack-12.0.0 Slackware 5 10-12-2007 06:36 AM
raid1: md resyncing at every boot? gergra Linux - General 1 11-01-2006 04:42 PM
Software RAID-1 unable to boot degraded keithk23 Linux - Server 2 09-27-2006 08:52 AM
/boot on RAID1? Swakoo Linux - General 3 08-22-2006 07:38 PM
Slackware 10.2 boot from SATA RAID1? Rexxars Slackware 2 01-06-2006 11:04 AM


All times are GMT -5. The time now is 06:00 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration