Results 1 to 1 of 1
I have a RAID1 array that is supposed to have two Hitachi disks /dev/sdf and /dev/sdg. Instead I think have:
) a degraded RAID1 /dev/md125p1, composed of a single /dev/md/RAID_Hitachi_0_0p1, ...
Enjoy an ad free experience by logging in. Not a member yet? Register.
- 07-17-2011 #1Just Joined!
- Join Date
- Oct 2006
- Posts
- 25
I fear my RAID1 is “tangled” between three abstractions.
I have a RAID1 array that is supposed to have two Hitachi disks /dev/sdf and /dev/sdg. Instead I think have:
) a degraded RAID1 /dev/md125p1, composed of a single /dev/md/RAID_Hitachi_0_0p1, that has a working filesystem
) a single “Raid Component”/dev/md126 aka /dev/md/RAID_Hitachi_0_0, composed of disks /dev/sdf and /dev/sdg, with apparently no filesystem, and is a component of /dev/md127
) a partially assembled imsm container /dev/md127, with one member, /dev/md/RAID_Hitachi_0_0, wich cannot even be read with parted.
I fear that I have TWO fake-raids, but the only one I wanted, RAID_Hitachi_0_0, has been re-purposed into a raid component of hitachi_mirror_0. Can this be untangled? Or am I stuck reformatting?
Thanks!
Code:mdadm --detail /dev/md125p1 /dev/md125p1: Version : 1.0 Creation Time : Tue Jan 26 12:06:25 2010 Raid Level : raid1 Array Size : 976751968 (931.50 GiB 1000.19 GB) Used Dev Size : unknown Raid Devices : 2 Total Devices : 1 Persistence : Superblock is persistent Update Time : Sun Jul 17 14:31:47 2011 State : clean, degraded Active Devices : 1 Working Devices : 1 Failed Devices : 0 Spare Devices : 0 Name : hitachi_mirror UUID : 781fa619:a0d8b7c6:8b1736ab:0e05354f Events : 7232892 Number Major Minor RaidDevice State 0 259 0 0 active sync /dev/md/RAID_Hitachi_0_0p1 1 0 0 1 removedCode:ls –la /dev/md lrwxrwxrwx. 1 root root 8 Jul 17 12:58 hitachi_mirror_0 -> ../md125 lrwxrwxrwx. 1 root root 10 Jul 17 12:59 hitachi_mirror_0p1 -> ../md125p1 -rw-------. 1 root root 5 Jul 17 12:59 md127.pid srwxr-xr-x. 1 root root 0 Jul 17 12:59 md127.sock= -rw-------. 1 root root 205 Jul 17 12:58 md-device-map lrwxrwxrwx. 1 root root 8 Jul 17 14:41 RAID_Hitachi_0_0 -> ../md126 lrwxrwxrwx. 1 root root 10 Jul 17 12:58 RAID_Hitachi_0_0p1 -> ../md126p1
Code:mdadm -E -s ARRAY metadata=imsm UUID=59aa3704:4716e93c:da98c89d:424f6409 ARRAY /dev/md/RAID_Hitachi_0 container=59aa3704:4716e93c:da98c89d:424f6409 member=0 UUID=5ddd9fc2:43d5d2ba:8258f6b9:64a11a3d ARRAY /dev/md/hitachi_mirror metadata=1.0 UUID=781fa619:a0d8b7c6:8b1736ab:0e05354f name=hitachi_mirror
Code:mdadm --detail /dev/md126 /dev/md126: Container : /dev/md127, member 0 Raid Level : raid1 Array Size : 976762368 (931.51 GiB 1000.20 GB) Used Dev Size : 976762368 (931.51 GiB 1000.20 GB) Raid Devices : 2 Total Devices : 2 State : clean Active Devices : 2 Working Devices : 2 Failed Devices : 0 Spare Devices : 0 UUID : 5ddd9fc2:43d5d2ba:8258f6b9:64a11a3d Number Major Minor RaidDevice State 1 8 80 0 active sync /dev/sdf 0 8 96 1 active sync /dev/sdgCode:mdadm --detail /dev/md127 /dev/md127: Version : imsm Raid Level : container Total Devices : 2 Working Devices : 2 UUID : 59aa3704:4716e93c:da98c89d:424f6409 Member Arrays : /dev/md/RAID_Hitachi_0_0 Number Major Minor RaidDevice 0 8 80 - /dev/sdf 1 8 96 - /dev/sdg


Reply With Quote
