On Sun, 08 Dec 2013 20:50:13 -0600 David C. Rankin wrote:
On 12/08/2013 08:15 PM, David C. Rankin wrote:
I'm not sure how to proceed safely from here. Is there anything else I should try before attempting to --create the array again? If I do create the array with 1 drive and "missing", should I then use --add or --re-add to add the other drive? Also, since /dev/sda5 shows Events: 148 and /dev/sdb5 shows Events: 149, should I choose /dev/sdb5 as the one to preserve and let "missing" take the place of /dev/sda5? If so, then does the following create statement look correct:
mdadm --create --verbose --level=1 --metadata=1.0 --raid-devices=2 \ /dev/md1 /dev/sdb5 missing
Should I also use --force?
Well before taking drastic steps, checking inf the partitions are mountable -- they are! Whoop!
nemtemp:/mnt # mdadm --verbose --assemble /dev/md1 /dev/sdb5 mdadm: looking for devices for /dev/md1 mdadm: /dev/sdb5 is identified as a member of /dev/md1, slot 1. mdadm: no uptodate device for slot 0 of /dev/md1 mdadm: added /dev/sdb5 to /dev/md1 as 1 mdadm: /dev/md1 assembled from 1 drive - need all 2 to start it (use --run to insist). nemtemp:/mnt # cat /proc/mdstat Personalities : [raid1] md2 : active raid1 sda7[0] sdb7[1] 221929772 blocks super 1.0 [2/2] [UU] bitmap: 0/424 pages [0KB], 256KB chunk
md1 : inactive sdb5[1](S) 20972752 blocks super 1.0
md0 : active raid1 sda1[0] sdb1[1] 104376 blocks super 1.0 [2/2] [UU] bitmap: 0/7 pages [0KB], 8KB chunk
unused devices: <none> nemtemp:/mnt # mdadm --run /dev/md1 mdadm: failed to run array /dev/md1: Input/output error
Hmm., this is just raid1, mirrored ext3, so mounting should work:
nemtemp:/mnt # mkdir sda nemtemp:/mnt # mkdir sdb
nemtemp:/mnt # mdadm --stop /dev/md1 mdadm: stopped /dev/md1 nemtemp:/mnt # mount -o ro /dev/sdb5 /mnt/sdb/ mount: unknown filesystem type 'linux_raid_member'
nemtemp:/mnt # mount -t ext3 -o ro /dev/sdb5 /mnt/sdb/ nemtemp:/mnt # l sdb total 116 drwxr-xr-x 21 root root 4096 2013-01-25 17:06 ./ drwxr-xr-x 7 root root 140 2013-12-08 06:38 ../ drwxr-xr-x 2 root root 4096 2010-12-05 06:43 bin/ drwxr-xr-x 2 root root 4096 2008-08-21 06:48 boot/ drwxr-xr-x 2 root root 4096 2008-08-22 01:54 data/ drwxr-xr-x 5 root root 4096 2008-08-21 06:48 dev/ <snip>
nemtemp:/mnt # mount -t ext3 -o ro /dev/sda5 /mnt/sda nemtemp:/mnt # l sda total 116 drwxr-xr-x 21 root root 4096 2013-01-25 17:06 ./ drwxr-xr-x 7 root root 140 2013-12-08 06:38 ../ drwxr-xr-x 2 root root 4096 2010-12-05 06:43 bin/ drwxr-xr-x 2 root root 4096 2008-08-21 06:48 boot/ drwxr-xr-x 2 root root 4096 2008-08-22 01:54 data/ drwxr-xr-x 5 root root 4096 2008-08-21 06:48 dev/ <snip>
nemtemp:/mnt # mount <snip> /dev/md0 on /mnt/boot type ext3 (rw) /dev/md2 on /mnt/home type ext3 (rw) /dev/sdb5 on /mnt/sdb type ext3 (ro) /dev/sda5 on /mnt/sda type ext3 (ro)
Both drives are fine!! Why is mdadm having problems? Would a newer mdadm be worth a shot? I'd rather figure out why my version (2.6.4) isn't working, but I think I've pretty much tried everything up to the point of having to use the --create mode and risk data loss. JA, all, anybody have any other suggestions?
Hi David, Wouldn't the safest course of action be to clone these partitions and make backups of the others before proceeding? If the additional event on sdb5 was a read/write error causing the read only bit to be set, that could explain mdadm being 'cranky' about mounting and using the partition. That would also explain you being able to mount the partition manually in read only mode. Along the same lines, are these drives SMART capable? Have you tried using smartctl to check on the status of sdb? Of particular interest would be the number of reallocated sectors and whether or not that number is perceptibly climbing -- in which case drive failure could be imminent. I wish you the best of luck & regards, Carl -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org