Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.linux.suse    |    Suse is actually not that bad    |    138,051 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 136,690 of 138,051    |
|    Carlos E.R. to Anton Shepelev    |
|    Re: SLES won't boot after removal of the    |
|    19 Dec 18 11:56:38    |
      XPost: alt.os.linux       From: robin_listas@es.invalid              On 19/12/2018 10.00, Anton Shepelev wrote:       > J.O. Aho:       >       >> The noresume will just be useful those times you have       >> hibernated and don't want to resume from the point where       >> you hibernated but do a fresh boot. I would recommend to       >> remove that or you may get a big head ache if you one day       >> would like to use hibernation.       >       > I had to use it instead of       >       > resume=/dev/system/swap       >       > What shall I specify for the resume device now that swap has       > been removed? I don't think that hibernation will ever be       > required for a server hosted on a virtual machine.              Nothing, or noresume, IMO.              >       >>> I have deleted the swap partition from LVM and added the       >>> `noresume' option to the kernel boot options. When,       >>> however, I restarted the system it failed with this error:       >>>       >>> 12:12:10 dracut-initqueue[363]: Scanning devices sda1 for LVM logical       volumes system/swap system/root       >>> 12:12:10 dracut-initqueue[363]: inactive '/dev/system/root' [110.00 GiB]       inherit       >>> 12:12:10 dracut-initqueue[363]: Failed to find logical volume "system/swap"       >>>       >> I think this is handled by systemd and systemd will fail       >> boots when a disk/partition is missing (quite stupid IMHO),       >> you will need to regenerate the initramfs       >>       >> dracut --regenerate-all --force       >       > Thanks, it has helped! What does initramfs have to do with       > persistent storage? Is it not for RAM-drives only?              dracut, or in SUSE systems, "mkinitrd", creates an archive that is       loaded with the kernel during boot (as a ramdisk), containing modules       the kernel needs before it reads the root filesystem and finds modules,       but also a minimal tree with configuration files, such as a copy of the       needed fstab.              You system was booting with the old archive that had the previous copy       of those files.              --       Cheers, Carlos.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca