[ale] Software raid 0 getting strnage errors.
Jim Lynch
ale_nospam at fayettedigital.com
Thu Sep 27 13:38:53 EDT 2007
Keith Hopkins (ALE) wrote:
> Jim Lynch wrote:
>
>> I first noticed that I had a problem when I received the following email:
>>
>> A DegradedArray event had been detected on md device /dev/md0.
>>
>>
>> I did a google on this error and found that it's probably because of an
>> unclean mount. I suspect that happened during a storm when power went out.
>> a cat of /proc/mdstat
>> Personalities : [linear] [raid0] [raid1] [raid10] [raid6] [raid5]
>> [raid4] [multipath]
>> md0 : active raid1 hda5[1]
>> 93771264 blocks [2/1] [_U]
>>
>> unused devices: <none>
>>
>> Sure enough /dev/hdb5 is missing. However when I attempt to add it back
>> in, I get:
>>
>> root at chinaberry:~# umount /dev/md0
>> root at chinaberry:~# mdadm /dev/md0 --add /dev/hdb5
>> mdadm: Cannot open /dev/hdb5: Device or resource busy
>>
>>
>
> Hi Jim,
>
> mdadm -E on a failed drive is usually not helpful, as it shows 'outdated' info. What does mdadm -D /dev/md0 show you?
>
> You odd bit is that you have the wrong partition type set on hdb5. It should be "fd" Linux raid autodetect.
>
> For what it's worth, let's see the output from `cat /proc/mounts`.
>
> --Keith
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale
>
>
cat /proc/mounts
none /sys sysfs rw,nosuid,nodev,noexec 0 0
none /proc proc rw,nosuid,nodev,noexec 0 0
udev /dev tmpfs rw 0 0
/dev/disk/by-uuid/4f67dae8-cdcb-460e-86cd-a5f0e4009422 / ext3
rw,data=ordered 0 0
/dev/disk/by-uuid/4f67dae8-cdcb-460e-86cd-a5f0e4009422 /dev/.static/dev
ext3 rw,data=ordered 0 0
tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /dev/shm tmpfs rw 0 0
devpts /dev/pts devpts rw 0 0
usbfs /dev/bus/usb/.usbfs usbfs rw 0 0
udev /proc/bus/usb tmpfs rw 0 0
usbfs /proc/bus/usb/.usbfs usbfs rw 0 0
tmpfs /var/run tmpfs rw,nosuid,nodev,noexec 0 0
tmpfs /var/lock tmpfs rw,nosuid,nodev,noexec 0 0
/dev/sda5 /home ext3 rw,data=ordered 0 0
/dev/md0 /backupmirror ext3 rw,data=ordered 0 0
mdadm -D /dev/md0
/dev/md0:
Version : 00.90.03
Creation Time : Fri Feb 23 15:03:40 2007
Raid Level : raid1
Array Size : 93771264 (89.43 GiB 96.02 GB)
Device Size : 93771264 (89.43 GiB 96.02 GB)
Raid Devices : 2
Total Devices : 1
Preferred Minor : 0
Persistence : Superblock is persistent
Update Time : Thu Sep 27 13:28:43 2007
State : clean, degraded
Active Devices : 1
Working Devices : 1
Failed Devices : 0
Spare Devices : 0
UUID : d01d66b4:16efa6c2:d7493088:59f3fe68
Events : 0.1690
Number Major Minor RaidDevice State
0 0 0 0 removed
1 3 5 1 active sync /dev/hda5
And just 'cause I hadn't tried it recently:
mdadm /dev/md0 -a /dev/hdb5
mdadm: Cannot open /dev/hdb5: Device or resource busy
And this is kind of interesting:
jim at chinaberry:~$ sudo vol_id /dev/hda5
ID_FS_USAGE=raid
ID_FS_TYPE=linux_raid_member
ID_FS_VERSION=0.90.1
ID_FS_UUID=b4661dd0-c2a6-ef16-8830-49d768fef359
ID_FS_LABEL=
ID_FS_LABEL_SAFE=
jim at chinaberry:~$ sudo vol_id /dev/hdb5
ID_FS_USAGE=raid
ID_FS_TYPE=linux_raid_member
ID_FS_VERSION=0.90.1
ID_FS_UUID=b4661dd0-c2a6-ef16-8830-49d768fef359
ID_FS_LABEL=
ID_FS_LABEL_SAFE=
Thanks,
Jim.
More information about the Ale
mailing list