Blacklist the wwwid in multipath.conf and/or blacklist the disk type in multipath. And/or whitelist the disks you want multipath to manage. If all of your disks have 2 paths and are expected to have 2 paths then you can set file_multipaths to only manage devices with 2 paths, but to make multipath work right in the one path case the disks need to be listed in the bindings file. The short term is add ,nofail to the options on the mount then it will always boot up but may not mount /boot. But make sure /boot is mounted when doing the things mentioned below. The bios finds the data on /boot and puts what is needed to boot into memory, once that is done you really only need /boot on the machine if you are updating kernels/changing grub options/rebuilding initrds. On Wed, Mar 3, 2021 at 4:19 AM GianPiero Puccioni <gianpiero.puccioni@xxxxxxxxxx> wrote: > > On 3/2/21 10:24 PM, Jorge Fábregas wrote: > > On 3/2/21 5:04 PM, GianPiero Puccioni wrote: > >> 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? > > > > Hi GianPiero, > > > > This is strange. I don't know why there's no device file for the first > > partition (/dev/sda1). Can you try "partprobe /dev/sda" to see if it creates > > the file? > > Thanks all for the help > > I didn't know this command (never neded it..) but yes, it did create the file > now I have > # ls /dev/sd* > /dev/sda /dev/sda1 /dev/sda2 > > and "blkid" has > /dev/sda1: UUID="f365a320-f3d7-4c07-8bfb-f0164b9ce8c0" BLOCK_SIZE="4096" > TYPE="xfs" PARTUUID="6ccdd7fd-01" > that wasn't there before. > > > Are you sure /dev/sda1 was used for /boot ? > I think so(it was the partion marked as bootable), and now that I can mount it I > can see that all the usal /boot stuff is there. > Can you > > show the output of "cat /proc/cmdline"? > > > # cat /proc/cmdline > BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.10.19-200.fc33.x86_64 > root=/dev/mapper/fedora_node06-root ro resume=/dev/mapper/fedora_node06-swap > rd.lvm.lv=fedora_node06/root rd.lvm.lv=fedora_node06/swap rhgb quiet > > As Roger said the problem seems to be multipath but > if there is no fix to the fact that sda1 disappeared (any idea?) > I suppose the solution now could be to copy all the stuff from sda1 in /boot and > recreate grub in sda ignoring sda1. Unless it needs a separate /boot, I think > UEFI is disabled but I am not sure, or for the weird RAID stuff. > > As I said I am doing all this remotely so I have to be careful not to break the > boot. > > Thanks again. > > GiP > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
