[SOLVED] Trying to install on RAID

JimDeadlock · 2019-04-22 19:51:59

I'm trying to install Arch on a RAID 0 array created on an identical pair of NVMe drives. I originally created the array in BIOS, it was very easy to set up but unfortunately when I switched to RAID mode the array was not detected when booting into a live session. I reported this on the Newbie forum and was advised to "avoid Fake RAID like the plague" so then I wiped it all and recreated the RAID with mdadm from a live session, as per the wiki instructions. It all seems to be fine as far as I can tell. I went ahead and installed Arch on it, ran GRUB (on a separate drive) and it detected the new Arch install. However, when attempting to boot into it I get this:

[some other stuff...]
ERROR: device '/dev/md127p1' not found. Skipping fsck.
:: mounting '/dev/md127p1' on real root
mount: /new_root: no filesystem type specified.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off
[rootfs ]#

fstab on the new install (note that I've attempted to install/boot in both legacy and EFI modes, both with the same results as above):

# /dev/md127p1 LABEL=ArchSys
UUID=8aa5ca90-0e5b-420f-a53c-1789c70e4f32	/         	ext4      	rw,relatime,stripe=256	0 1

# /dev/nvme1n1p1 LABEL=EFI
#UUID=03A3-0196      	/boot     	vfat      	rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro	0 2

# /dev/md127p2 LABEL=ArchHome
UUID=b3808afb-5eba-435f-90aa-f6c0aabcfd0e	/home     	ext4      	rw,relatime,stripe=256	0 2

lsblk

NAME          MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
loop0           7:0    0 489.5M  1 loop  /run/archiso/sfs/airootfs
sda             8:0    0 447.1G  0 disk  
├─sda1          8:1    0 107.4G  0 part  
├─sda2          8:2    0   481M  0 part  
├─sda3          8:3    0     1K  0 part  
├─sda4          8:4    0     8G  0 part  
├─sda5          8:5    0  19.5G  0 part  
└─sda6          8:6    0 311.8G  0 part  /root/ubu
sdb             8:16   0   1.8T  0 disk  
├─sdb1          8:17   0    20G  0 part  
└─sdb2          8:18   0   1.8T  0 part  
sdc             8:32   0   1.8T  0 disk  
├─sdc1          8:33   0 105.1G  0 part  
├─sdc2          8:34   0   1.1T  0 part  
└─sdc3          8:35   0 683.6G  0 part  
sdd             8:48   1   3.7G  0 disk  
├─sdd1          8:49   1   602M  0 part  /run/archiso/bootmnt
└─sdd2          8:50   1    64M  0 part  
nvme1n1       259:0    0 931.5G  0 disk  
├─nvme1n1p1   259:2    0   550M  0 part  
└─nvme1n1p2   259:3    0   931G  0 part  
  └─md127       9:127  0   1.8T  0 raid0 
    ├─md127p1 259:6    0    20G  0 part  
    └─md127p2 259:7    0   1.8T  0 part  
nvme0n1       259:1    0 931.5G  0 disk  
├─nvme0n1p1   259:4    0   550M  0 part  
└─nvme0n1p2   259:5    0   931G  0 part  
  └─md127       9:127  0   1.8T  0 raid0 
    ├─md127p1 259:6    0    20G  0 part  
    └─md127p2 259:7    0   1.8T  0 part

fdisk -l

Disk /dev/nvme1n1: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 970 EVO Plus 1TB            
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: 751B84FB-407A-9945-A10F-88B0F9393829

Device           Start        End    Sectors  Size Type
/dev/nvme1n1p1    2048    1128447    1126400  550M Microsoft basic data
/dev/nvme1n1p2 1128448 1953523711 1952395264  931G Linux filesystem


Disk /dev/nvme0n1: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 970 EVO Plus 1TB            
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: B7F405F0-D3FB-6C4F-BC62-8DCFF2E5524D

Device           Start        End    Sectors  Size Type
/dev/nvme0n1p1    2048    1128447    1126400  550M EFI System
/dev/nvme0n1p2 1128448 1953523711 1952395264  931G Linux filesystem


Disk /dev/sda: 447.1 GiB, 480103981056 bytes, 937703088 sectors
Disk model: SSD PLUS 480GB  
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: 0xf79d45bf

Device     Boot     Start       End   Sectors   Size Id Type
/dev/sda1            2048 225216682 225214635 107.4G  7 HPFS/NTFS/exFAT
/dev/sda2       225218560 226203647    985088   481M 27 Hidden NTFS WinRE
/dev/sda3       226207742 920924159 694716418 331.3G  5 Extended
/dev/sda4       920926208 937701375  16775168     8G 82 Linux swap / Solaris
/dev/sda5  *    226207744 267168681  40960938  19.5G 83 Linux
/dev/sda6       267169792 920924159 653754368 311.8G 83 Linux

Partition table entries are not in disk order.


Disk /dev/sdc: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000DL003-9VT1
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: 499DE894-F145-4591-BCDF-E4E852B31DFB

Device          Start        End    Sectors   Size Type
/dev/sdc1  3686723584 3907028991  220305408 105.1G Microsoft basic data
/dev/sdc2        2048 2253125631 2253123584   1.1T Linux filesystem
/dev/sdc3  2253125632 3686723583 1433597952 683.6G Microsoft basic data

Partition table entries are not in disk order.


Disk /dev/sdb: 1.8 TiB, 2000398934016 bytes, 3907029168 sectors
Disk model: ST2000DM005-2CW1
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 5C2EF25E-CBCB-4611-9F2F-6ADF4A132707

Device        Start        End    Sectors  Size Type
/dev/sdb1      2048   41945087   41943040   20G Linux filesystem
/dev/sdb2  41945088 3907028991 3865083904  1.8T Linux filesystem


Disk /dev/sdd: 3.7 GiB, 4005527552 bytes, 7823296 sectors
Disk model: USB Flash Memory
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: 0x2e7f95ca

Device     Boot Start     End Sectors  Size Id Type
/dev/sdd1  *        0 1232895 1232896  602M  0 Empty
/dev/sdd2         164  131235  131072   64M ef EFI (FAT-12/16/32)


Disk /dev/loop0: 489.5 MiB, 513298432 bytes, 1002536 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


Disk /dev/md127: 1.8 TiB, 1998984314880 bytes, 3904266240 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 524288 bytes / 1048576 bytes
Disklabel type: dos
Disk identifier: 0x432a272d

Device       Boot    Start        End    Sectors  Size Id Type
/dev/md127p1          2048   41945087   41943040   20G 83 Linux
/dev/md127p2      41945088 3904266239 3862321152  1.8T 83 Linux

Last edited by JimDeadlock (2019-04-23 02:53:44)

bugsmanagement · 2019-04-23 01:06:05

ERROR: device '/dev/md127p1' not found. Skipping fsck.
:: mounting '/dev/md127p1' on real root
mount: /new_root: no filesystem type specified.
You are now being dropped into an emergency shell.
sh: can't access tty; job control turned off

Hello there, Seems like initrd/fs is broken, have you recreated it after the changes?

JimDeadlock · 2019-04-23 02:53:11

While searching information on how to do what you just said, I came across something that mentioned adding mdadm_udev to the HOOKS in /etc/mkinitcpio.conf so I did that, ran mkinitcpio and... bingo! Gordon's alive!! Thank you ever so much! I'm new to both RAID and Arch so the past few days have been quite a headache but at last I'm on the home straight!

bugsmanagement · 2019-04-23 03:07:33

Please add [solve] by editing the first topic

Arch Linux

#1 2019-04-22 19:51:59

[SOLVED] Trying to install on RAID

#2 2019-04-23 01:06:05

Re: [SOLVED] Trying to install on RAID

#3 2019-04-23 02:53:11

Re: [SOLVED] Trying to install on RAID

#4 2019-04-23 03:07:33

Re: [SOLVED] Trying to install on RAID

Board footer