if you are running multipath then here is what happened, multipath started up and attempted to manage sda and so it deleted sda1, then once it gets to sda2 it figures out the vg is live and online and it figures out it cannot manage it, so stops. No code exists apparently to go back and put back sda1 in some versions.
partprobe will work, but without partprobe sda1 won't exist, and the uuid links will be pointing to something that does not exist.
On Tue, Mar 2, 2021 at 4:02 PM Ed Greshko ed.greshko@greshko.com wrote:
On 03/03/2021 05:04, GianPiero Puccioni wrote:
Hi,
I have a problem with an old rack unit I use in a cluster. We had a problem with the HD and had to change it and reinstall. It was done by someone new to the job (I am locked and doing everything remotely) and he had a problem with the configuration as it seems that this unit HD HAS to be configured as RAID and F33 didn't see it at first.
I am not sure what he did try, only thing he said is that it stopped at boot and he had to comment a line in fstab, but the result is that the unit starts in weird way.
The situation is this (skipping some lines): # lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT sda 8:0 0 931.5G 0 disk └─sda2 8:2 0 930.5G 0 part ├─fedora_node06-root 253:0 0 50G 0 lvm / ├─fedora_node06-swap 253:1 0 4G 0 lvm [SWAP] └─fedora_node06-home 253:2 0 876.5G 0 lvm /home
#fdisk -l /dev/sda Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors Disk identifier: 0x6ccdd7fd Device Boot Start End Sectors Size Id Type /dev/sda1 * 2048 2099199 2097152 1G 83 Linux /dev/sda2 2099200 1953523711 1951424512 930.5G 8e Linux LVM
#ls -l /dev/sd* brw-rw----. 1 root disk 8, 0 Feb 2 01:00 /dev/sda brw-rw----. 1 root disk 8, 2 Feb 2 01:00 /dev/sda2
# cat /etc/fstab
/dev/mapper/fedora_node06-root / xfs defaults 0 0 #UUID=f365a320-f3d7-4c07-8bfb-f0164b9ce8c0 /boot xfs defaults 0 0 /dev/mapper/fedora_node06-home /home xfs defaults 0 0 /dev/mapper/fedora_node06-swap none swap defaults 0 0
# ls -l /boot total 0
So as I understand it sda1 is bootable and contains the kernel, linux start from there and then finds (how?) and mounts / and /home but not /boot which is empty. I would have changed the line in fstab with /dev/sda1 but it doesn't exist (!).
dmesg has this:
[ 4.369576] sd 3:0:0:0: Attached scsi generic sg1 type 0 [ 4.384096] sda: sda1 sda2
so it is there and seen but why the block device is not created? Copying the content of (sda1)boot into /boot and reinstalling grub could probably work but how?
Any advice?
man fstab
Notice there are multiple ways to identify a disk partition. Including the device name as well as LABEL=, PARTUUID= and PARTLABEL= and UUID=
Run.... "blkid" and you'd probably see....
/dev/sda1: UUID="f365a320-f3d7-4c07-8bfb-f0164b9ce8c0" BLOCK_SIZE= etc.
So, uncomment the line
#UUID=f365a320-f3d7-4c07-8bfb-f0164b9ce8c0 /boot xfs defaults 0 0
in your fstab and then
mount /boot
-- People who believe they don't make mistakes have already made one.
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure