A message from our CEO about the future of Stack Overflow and Stack Exchange. Read now.

New answers tagged

1

So this seems to be a case of a random bogus partition table mis-detection. Here's an example of an Atari / AHDI partition table (created with parted): # hexdump -C -n 512 /dev/loop0 000001c0 00 00 00 03 20 00 01 4c 4e 58 00 00 08 00 00 00 |.... ..LNX......| 000001d0 08 00 01 4c 4e 58 00 00 18 00 00 00 60 00 00 50 |...LNX......`..P| 000001e0 41 52 ...


-1

This could be a "bad sign", I'm not sure... But in our case the device "/dev/sdc1" was having problems as we could see with the command... fsck -c /dev/sdc1 TIP: If you are not worried about the contents of the disk use the fsck -y /dev/sdc1 command so that all corrections will be made automatically if necessary. You can use the command below to check ...


0

The problem was occurring for the reasons below... The dracut documentation implies that any md raid arrays should be automatically assembled, and that the "rd.md.uuid" parameter should only be used if you only want certain arrays assembled as part of the boot process. It seems that in reality, the arrays are not assembled automatically, and ...


Top 50 recent answers are included