Software Raid Issue Raid 1 not recognized by the new system?
by bluefish1 from LinuxQuestions.org on (#6CF7W)
I upgraded to a new server after 12 years on a AMD Phenom II box with 16gb ram. I purchased a HP Z840 with Intel Xeon 2x 8core cpus and 64gb of ram. Based on VERY recent announcements about RHEL source support, I moved reluctantly from Alma Linux 8 to Redhat 9.
The process I used was to use a fresh install of Redhat configuring it on a single boot drive. The system is obviously more robust and fast on boot, way quieter than the old box and i am not getting any errors on boot.
My Raid 5 array was recognized immediately and I was able to mount it using the UUID to fstab with ultra simplicity. Works perfectly! It is 4 by 1tb Western Digital Black server drives.
However, my Raid 1 array did not get recognized. It is 2 Western Digital 4tb Black drives.
fdisk -l
Code:Disk /dev/sda: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD4000FYYZ-0
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: 82B5683E-C572-0E48-BD5F-B1337BA6004F
Device Start End Sectors Size Type
/dev/sda1 2048 7814037134 7814035087 3.6T Linux RAID
Disk /dev/sdc: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD4000FYYZ-0
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: 84C804FB-2F14-0748-B8B2-F7C8E299211B
Device Start End Sectors Size Type
/dev/sdc1 2048 7814037134 7814035087 3.6T Linux RAIDmdadm:
Code:[root@localhost james]# mdadm --detail /dev/sda1
mdadm: /dev/sda1 does not appear to be an md device
[root@localhost james]# mdadm --detail /dev/sdc1
mdadm: /dev/sdc1 does not appear to be an md device
[root@localhost james]# mdadm --examine /dev/sda1
mdadm: No md superblock detected on /dev/sda1.
[root@localhost james]# mdadm --examine /dev/sda
/dev/sda:
MBR Magic : aa55
Partition[0] : 4294967295 sectors at 1 (type ee)
[root@localhost james]# mdadm --examine /dev/sdc1
mdadm: No md superblock detected on /dev/sdc1.
[root@localhost james]# mdadm --examine /dev/sdc
/dev/sdc:
MBR Magic : aa55
Partition[0] : 4294967295 sectors at 1 (type ee)gdisk:
Code:[root@localhost james]# gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.7
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/sda: 7814037168 sectors, 3.6 TiB
Model: WDC WD4000FYYZ-0
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 82B5683E-C572-0E48-BD5F-B1337BA6004F
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 2048, last usable sector is 7814037134
Partitions will be aligned on 2048-sector boundaries
Total free space is 0 sectors (0 bytes)
Number Start (sector) End (sector) Size Code Name
1 2048 7814037134 3.6 TiB FD00
[root@localhost james]# gdisk /dev/sdc
GPT fdisk (gdisk) version 1.0.7
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/sdc: 7814037168 sectors, 3.6 TiB
Model: WDC WD4000FYYZ-0
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 84C804FB-2F14-0748-B8B2-F7C8E299211B
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 2048, last usable sector is 7814037134
Partitions will be aligned on 2048-sector boundaries
Total free space is 0 sectors (0 bytes)
Number Start (sector) End (sector) Size Code Name
1 2048 7814037134 3.6 TiB FD00[root@localhost james]# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md126 : active raid5 sdf1[1] sdd1[2] sdg1[0] sde1[4]
628749312 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
bitmap: 0/2 pages [0KB], 65536KB chunk
md127 : active raid5 sdd2[2] sdg2[0] sdf2[1] sde2[4]
2300739072 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
bitmap: 0/6 pages [0KB], 65536KB chunk
unused devices: <none>
Can anyone tell me what is going on and why they are not connecting?
The process I used was to use a fresh install of Redhat configuring it on a single boot drive. The system is obviously more robust and fast on boot, way quieter than the old box and i am not getting any errors on boot.
My Raid 5 array was recognized immediately and I was able to mount it using the UUID to fstab with ultra simplicity. Works perfectly! It is 4 by 1tb Western Digital Black server drives.
However, my Raid 1 array did not get recognized. It is 2 Western Digital 4tb Black drives.
fdisk -l
Code:Disk /dev/sda: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD4000FYYZ-0
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: 82B5683E-C572-0E48-BD5F-B1337BA6004F
Device Start End Sectors Size Type
/dev/sda1 2048 7814037134 7814035087 3.6T Linux RAID
Disk /dev/sdc: 3.64 TiB, 4000787030016 bytes, 7814037168 sectors
Disk model: WDC WD4000FYYZ-0
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: 84C804FB-2F14-0748-B8B2-F7C8E299211B
Device Start End Sectors Size Type
/dev/sdc1 2048 7814037134 7814035087 3.6T Linux RAIDmdadm:
Code:[root@localhost james]# mdadm --detail /dev/sda1
mdadm: /dev/sda1 does not appear to be an md device
[root@localhost james]# mdadm --detail /dev/sdc1
mdadm: /dev/sdc1 does not appear to be an md device
[root@localhost james]# mdadm --examine /dev/sda1
mdadm: No md superblock detected on /dev/sda1.
[root@localhost james]# mdadm --examine /dev/sda
/dev/sda:
MBR Magic : aa55
Partition[0] : 4294967295 sectors at 1 (type ee)
[root@localhost james]# mdadm --examine /dev/sdc1
mdadm: No md superblock detected on /dev/sdc1.
[root@localhost james]# mdadm --examine /dev/sdc
/dev/sdc:
MBR Magic : aa55
Partition[0] : 4294967295 sectors at 1 (type ee)gdisk:
Code:[root@localhost james]# gdisk /dev/sda
GPT fdisk (gdisk) version 1.0.7
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/sda: 7814037168 sectors, 3.6 TiB
Model: WDC WD4000FYYZ-0
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 82B5683E-C572-0E48-BD5F-B1337BA6004F
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 2048, last usable sector is 7814037134
Partitions will be aligned on 2048-sector boundaries
Total free space is 0 sectors (0 bytes)
Number Start (sector) End (sector) Size Code Name
1 2048 7814037134 3.6 TiB FD00
[root@localhost james]# gdisk /dev/sdc
GPT fdisk (gdisk) version 1.0.7
Partition table scan:
MBR: protective
BSD: not present
APM: not present
GPT: present
Found valid GPT with protective MBR; using GPT.
Command (? for help): p
Disk /dev/sdc: 7814037168 sectors, 3.6 TiB
Model: WDC WD4000FYYZ-0
Sector size (logical/physical): 512/512 bytes
Disk identifier (GUID): 84C804FB-2F14-0748-B8B2-F7C8E299211B
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 2048, last usable sector is 7814037134
Partitions will be aligned on 2048-sector boundaries
Total free space is 0 sectors (0 bytes)
Number Start (sector) End (sector) Size Code Name
1 2048 7814037134 3.6 TiB FD00[root@localhost james]# cat /proc/mdstat
Personalities : [raid6] [raid5] [raid4]
md126 : active raid5 sdf1[1] sdd1[2] sdg1[0] sde1[4]
628749312 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
bitmap: 0/2 pages [0KB], 65536KB chunk
md127 : active raid5 sdd2[2] sdg2[0] sdf2[1] sde2[4]
2300739072 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [UUUU]
bitmap: 0/6 pages [0KB], 65536KB chunk
unused devices: <none>
Can anyone tell me what is going on and why they are not connecting?