Hello
I have a raid 5 array which looks like this:
mdadm --detail /dev/md5
/dev/md5:
Version : 00.90
Creation Time : Sun Feb 3 22:28:44 2008
Raid Level : raid5
Used Dev Size : 732571648 (698.63 GiB 750.15 GB)
Raid Devices : 11
Total Devices : 11
Preferred Minor : 5
Persistence : Superblock is persistent
Update Time : Wed Dec 17 17:44:23 2008
State : active, degraded, Not Started
Active Devices : 8
Working Devices : 11
Failed Devices : 0
Spare Devices : 3
Layout : left-symmetric
Chunk Size : 1024K
UUID : 7f33280c:2e5773a2:51dae465:
f5e9a19b (local to host syrk)
Events : 0.2411530
Number Major Minor RaidDevice State
0 8 81 0 active sync /dev/sdf1
1 8 193 1 active sync /dev/sdm1
2 8 113 2 active sync /dev/sdh1
3 8 1 3 active sync /dev/sda1
4 8 177 4 active sync /dev/sdl1
5 8 65 5 active sync /dev/sde1
6 65 33 6 active sync /dev/sds1
7 0 0 7 removed
8 0 0 8 removed
9 8 129 9 active sync /dev/sdi1
10 0 0 10 removed
11 8 17 - spare /dev/sdb1
12 65 17 - spare /dev/sdr1
13 65 1 - spare /dev/sdq1
The problem is that the array wont assemble after i rebooted the
computer. It showed that my disks has been removed and they showed up
as spares instead. I tried to force assemble it but with no luck and I
then tried to do a --update=resync with no luck. I then tried to
remove the spares from the array with this command: "mdadm /dev/md5
--remove /dev/sdb1" but then I only get the following response:
"mdadm: hot remove failed for /dev/sdb1: No such device". Is the data
lost? I don't know what happened.
Best regards Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
