Home / ubuntu / Questions / 1189835
In Process
ygoe
Asked: 2019-11-19 10:49:25 +0800 CST

The initramfs will attempt to resume from /dev/dm-1

  • 772

I'm setting up a new Ubuntu 18.04 server and have already played through one backup/restore loop. So the entire system has been restored from backup with a fresh RAID and LVM volumes.

Now recently, unattended-upgrades has reported this:

Processing triggers for initramfs-tools (0.130ubuntu3.8) ...
update-initramfs: Generating /boot/initrd.img-4.15.0-66-generic
I: The initramfs will attempt to resume from /dev/dm-1
I: (/dev/mapper/vg0-swap)
I: Set the RESUME variable to override this.

I tried to find out what that actually means but wasn't successful. What is it resuming there? Some process of generating boot files? I know it can take a while do do that. Does it have to do with the RAID? That is long finished with its resync. I don't get it. And what's actually wrong? What does that message want me to do? I'm clueless. If I don't need it, how can I make it go away?

The server did reboot successfully twice after that message so it can't be important. (If that "I" was supposed to mean something like that.)

Here's some commands if that helps:

> lvs
  LV   VG  Attr       LSize   Pool Origin Data%  Meta%  Move Log Cpy%Sync Convert
  root vg0 -wi-ao---- 400.00g
  swap vg0 -wi-ao----   8.00g

> cat /proc/mdstat
Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] [raid4] [raid10]
md1 : active raid1 nvme1n1p2[0] nvme0n1p2[1]
      499449152 blocks super 1.2 [2/2] [UU]
      bitmap: 1/4 pages [4KB], 65536KB chunk

md0 : active raid1 nvme0n1p1[1] nvme1n1p1[0]
      523264 blocks super 1.2 [2/2] [UU]

unused devices: <none>

I can't find a good command to show something about these "dm-0" and "dm-1" devices that are also related to the RAID I guess.

boot lvm raid

3 Answers

  1. It may happen when you install another OS alongside the first one. Means that swap partition has changed UUID and you need to adjust that in fstab.

    To check that run sudo blkid, that gives you actual UUIDs of your swaps, swapon -s will show which one is active, then compare its UUID to the one in /etc/fstab.

    If different, edit/create the file /etc/initramfs-tools/conf.d/resume with RESUME=UUID=<swap UUID from blkid>. THen run update-initramfs -u -k all and if it doesn't complain, you win.

    • 31

  2. This might actually be a (not even new) bug as mentioned here. They and others suggest to add RESUME=none to /etc/initramfs-tools/conf.d/resume.

    I needed to sudo-create the file /etc/initramfs-tools/conf.d/resume first on my U 19.04 machine. With sudo update-initramfs -u -k all you test and deploy the initramfs image. See details here.

    • 9

  3. Thank You! I love to learn, especially in Linux, because I love Linux! My problem was everytime I got a firmware update I would get the resume variable message, for initd.img from 5.4.0-29 all the way to 5.4.0-100, which took over a half hour, probably longer to update my OS, which is 20.04 that I have been running with no other problems for 3 years now, so after reading I tried a series of commands:

    First I ran 'sudo blkid'

    Second I ran '/etc/fstab'

    Found the same swap uuid

    Then ran '/etc/initramfs-tools/conf.d/resume with RESUME=UUID=<swap' and set the ID...

    Then ran 'update-initramfs -u -k all'

    And it started updating all the old firmwares for me . This has been driving me nuts for over a year now. At first I thought my system was borked. Now I am going to reboot and see if all went well. What kicks me in the ass is that a new OS with LTS is set to be released in a few days. But thats not the point...The point is that I "Learned" something new about linux on what to look for in the future thanks for all the contributions for ideas to try! Maybe someone can get use out of this problem that worked for me.

    • 1