Hi.
When I decided to move an existing RAID 1 array consisting of two disks to a new system, I checked online and saw that this would not be a problem- it would be autodetected. Well, this old array is not showing up in webgui Raid Management. It was installed under OMV 3.x on another hardware, software raid using OMV. It worked as a charm, until the motherboard got killed due to a powersurge so I had to move them to another OMV installation.
The two new disks shows up under Physical disks as /dev/sdc and /dev/sdd (which is kind of strange, because the already existing raid array (two disks, raid1) in the new system was /dev/sdc & /dev/sdd.. I had to install a PCI Express SATA card to this new system for this expansion. However, I do not know if this is relevant- just wanted to inform you guys). The existing raid (md0) is working and everything is in order.
Anyways, I have been googling some forums, and my guess is that under this new hardware the uuid is wrong.
Could someone guide me for creating a md1 with these two new disks? I want to keep the data that is on that old array.
cat /proc/mdstat:
root@takaguwa:/# cat /proc/mdstat
Personalities : [raid1]
md0 : active raid1 sdf[0] sdg[1]
5860391488 blocks super 1.2 [2/2] [UU]
bitmap: 0/44 pages [0KB], 65536KB chunk
unused devices: <none>
mdadm --detail --scan --verbose: (this new system is called takaguwa)
root@takaguwa:/# mdadm --detail --scan --verbose
ARRAY /dev/md0 level=raid1 num-devices=2 metadata=1.2 name=takaguwa:0 UUID=ee467228:89fa28ca:d461e0cb:ff61ef8c
devices=/dev/sdf,/dev/sdg
mdadm --assemble --scan --verbose:
root@takaguwa:/# mdadm --assemble --scan --verbose
mdadm: looking for devices for /dev/md0
mdadm: no RAID superblock on /dev/md0
mdadm: /dev/sdg is busy - skipping
mdadm: /dev/sdf is busy - skipping
mdadm: no RAID superblock on /dev/sde5
mdadm: no RAID superblock on /dev/sde3
mdadm: no RAID superblock on /dev/sde2
mdadm: no RAID superblock on /dev/sde1
mdadm: no RAID superblock on /dev/sde
mdadm: /dev/sdd has wrong uuid.
mdadm: /dev/sdc has wrong uuid.
mdadm: no RAID superblock on /dev/sdb1
mdadm: no RAID superblock on /dev/sdb
mdadm: no RAID superblock on /dev/sda1
mdadm: no RAID superblock on /dev/sda
Alles anzeigen
mdadm --examine /dev/sdc: (the old system was calld hattori)
root@takaguwa:/# mdadm --examine /dev/sdc
/dev/sdc:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ad30ac55:b2c3c863:4d6cd752:5c0b7a2f
Name : hattori:Raid
Creation Time : Sun Mar 2 16:06:35 2014
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 7814035120 (3726.02 GiB 4000.79 GB)
Array Size : 3907017424 (3726.02 GiB 4000.79 GB)
Used Dev Size : 7814034848 (3726.02 GiB 4000.79 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
Unused Space : before=1968 sectors, after=272 sectors
State : clean
Device UUID : 26d90a4e:a7ba63ba:80d2156c:6e959dd0
Update Time : Sat Aug 5 16:26:14 2017
Checksum : 8cb782bf - correct
Events : 815
Device Role : Active device 1
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
Alles anzeigen
mdadm --examine /dev/sdd: (the old system was called hattori)
root@takaguwa:/# mdadm --examine /dev/sdd
/dev/sdd:
Magic : a92b4efc
Version : 1.2
Feature Map : 0x0
Array UUID : ad30ac55:b2c3c863:4d6cd752:5c0b7a2f
Name : hattori:Raid
Creation Time : Sun Mar 2 16:06:35 2014
Raid Level : raid1
Raid Devices : 2
Avail Dev Size : 7814035120 (3726.02 GiB 4000.79 GB)
Array Size : 3907017424 (3726.02 GiB 4000.79 GB)
Used Dev Size : 7814034848 (3726.02 GiB 4000.79 GB)
Data Offset : 2048 sectors
Super Offset : 8 sectors
Unused Space : before=1968 sectors, after=272 sectors
State : clean
Device UUID : 848885fb:e663dbdf:91dd43c9:d0bb9a7b
Update Time : Sat Aug 5 16:26:14 2017
Checksum : 67d50ccf - correct
Events : 815
Device Role : Active device 0
Array State : AA ('A' == active, '.' == missing, 'R' == replacing)
Alles anzeigen
blkid:
root@takaguwa:/# blkid
/dev/sda1: UUID="0b76492f-f148-4a7e-87c0-374c16cc36e8" TYPE="ext4" PARTUUID="1b5e84ac-7b97-409b-bd6b-03aca2e01933"
/dev/sdb1: UUID="9d3f2528-edc3-4017-8af4-19d6ef0533ad" TYPE="ext4" PARTUUID="baf44685-0d3a-4c27-9963-24e3b09c1e6e"
/dev/sdc: UUID="ad30ac55-b2c3-c863-4d6c-d7525c0b7a2f" UUID_SUB="26d90a4e-a7ba-63ba-80d2-156c6e959dd0" LABEL="hattori:Raid" TYPE="linux_raid_member"
/dev/sdd: UUID="ad30ac55-b2c3-c863-4d6c-d7525c0b7a2f" UUID_SUB="848885fb-e663-dbdf-91dd-43c9d0bb9a7b" LABEL="hattori:Raid" TYPE="linux_raid_member"
/dev/sde1: UUID="6ef59f68-c122-4bf3-a715-a70220972749" TYPE="ext4" PARTUUID="5ded702d-01"
/dev/sde3: UUID="e8750dd2-e34e-4e3a-a169-822f064cb67b" TYPE="ext4" PARTUUID="5ded702d-03"
/dev/sde5: UUID="3e4278ac-3ecd-4b8c-b3ad-3c3dc9536d12" TYPE="swap" PARTUUID="5ded702d-05"
/dev/sdf: UUID="ee467228-89fa-28ca-d461-e0cbff61ef8c" UUID_SUB="7474bd84-88eb-4e49-960b-9cd9e76a0a4f" LABEL="takaguwa:0" TYPE="linux_raid_member"
/dev/md0: UUID="da00ddb0-1fd0-4ba5-86ec-b9b036baf2dd" TYPE="ext4"
/dev/sdg: UUID="ee467228-89fa-28ca-d461-e0cbff61ef8c" UUID_SUB="e73bd905-2792-1738-dad8-2759a3528c86" LABEL="takaguwa:0" TYPE="linux_raid_member"
root@takaguwa:/#
Alles anzeigen
fdisk -l: (it comes with a warning saying "Partition table entries are not in order")
root@takaguwa:/# fdisk -l
Disk /dev/sda: 931.5 GiB, 1000204883968 bytes, 1953525164 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 70435575-5EB9-468F-8198-AA1696A30C45
Device Start End Sectors Size Type
/dev/sda1 2048 1953525130 1953523083 931.5G Linux filesystem
Disk /dev/sdb: 1.8 TiB, 2000398931968 bytes, 3907029164 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 75E91EFF-7B04-45DE-9E8A-B5A68321C3BA
Device Start End Sectors Size Type
/dev/sdb1 2048 3907029130 3907027083 1.8T Linux filesystem
Disk /dev/sdc: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdd: 3.7 TiB, 4000787030016 bytes, 7814037168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sde: 232.9 GiB, 250059350016 bytes, 488397168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5ded702d
Device Boot Start End Sectors Size Id Type
/dev/sde1 * 2048 44046335 44044288 21G 83 Linux
/dev/sde2 468555774 488396799 19841026 9.5G 5 Extended
/dev/sde3 44046336 468553727 424507392 202.4G 83 Linux
/dev/sde5 468555776 488396799 19841024 9.5G 82 Linux swap / Solaris
Partition table entries are not in disk order.
Disk /dev/sdf: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/sdg: 5.5 TiB, 6001175126016 bytes, 11721045168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk /dev/md0: 5.5 TiB, 6001040883712 bytes, 11720782976 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Alles anzeigen
So,, anyone?
Is the problem due to the new PCI Express SATA card, and that the devices has swapped places (dev/sdf and /dev/sdg is the existing md0 array- which previosloy was /dev/sdc and /dev/sdd)? Maybe I will just swap cables to the new installation and it will somehow work?
On the old installation I think that the raid 1 array was created from /dev/sdc and /dev/sdd.
I do not know the order of the old raid.