LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Server (https://www.linuxquestions.org/questions/linux-server-73/)
-   -   Software Raid Issue Raid 1 not recognized by the new system? (https://www.linuxquestions.org/questions/linux-server-73/software-raid-issue-raid-1-not-recognized-by-the-new-system-4175726318/)

bluefish1 06-25-2023 10:01 AM
Software Raid Issue Raid 1 not recognized by the new system?
 
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 RAID
mdadm:
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?

lvm_ 06-25-2023 01:33 PM
RAID won't work without superblocks. No idea what happened to them but theoretically simply recreating the array on these disks should recover the data, some guys did it https://www.google.co.uk/search?q=md...ing+superblock Or you may use testdisk to be ultra safe.

bluefish1 06-30-2023 08:40 PM
Ran DIsktest
 
Disk test is saying the structure is fine. If I create a drive with the array I get the same error… wrong type.
My sense and instincts are that the data is fine, it is the system that is not understanding the partition type. Has anyone else seen this? It is a raid 1 drive… aka it is just a mirrored file system. In the past I could pull my raid one drives and mount a single drive as a normal linux file system….. there is no overriding raid schema to deal with.

I think it is because the drive is labeled as a Linux raid rather than a ext4 drive.

syg00 07-01-2023 12:46 AM
Quote:
Originally Posted by bluefish1 (Post 6439439)
It is a raid 1 drive… aka it is just a mirrored file system. In the past I could pull my raid one drives and mount a single drive as a normal linux file system….. there is no overriding raid schema to deal with.
That doesn't make a lot of sense - you would expect to have to assemble the array in degraded mode then issue the mount. A properly constructed initrd should recognise and assemble the degraded array for you on boot. What does this show ?
Code:
sudo file -s /dev/sda1

lvm_ 07-01-2023 10:12 AM
Quote:
Originally Posted by syg00 (Post 6439457)
That doesn't make a lot of sense
On the contrary, this is exactly as it should be. If you zero the superblock (already happened), change partition type from fd to 20 and let testdisk have a look, you'll get a non-mirrored partition with data.

syg00 07-01-2023 06:49 PM
Why would the OP zero the metadata then not mention it ?.

lvm_ 07-02-2023 12:14 AM
He did mention it but he didn't do it.


All times are GMT -5. The time now is 07:08 PM.