As some are aware, my NAS hates me. Anyway, I ran an update just now and it spat out the following:

Setting up linux-firmware (1.187.27) ...
update-initramfs: Generating /boot/initrd.img-5.13.0-30-generic
I: The initramfs will attempt to resume from /dev/sdb2
I: (UUID=e6480da4-95f0-4cf3-a047-a43ef09f978f)
I: Set the RESUME variable to override this.
update-initramfs: Generating /boot/initrd.img-5.11.0-27-generic
I: The initramfs will attempt to resume from /dev/sdb2
I: (UUID=e6480da4-95f0-4cf3-a047-a43ef09f978f)

UUID=e6480da4-95f0-4cf3-a047-a43ef09f978f is /swap.

/dev/sdb2: UUID="e6480da4-95f0-4cf3-a047-a43ef09f978f" TYPE="swap" PARTUUID="329487d0-88c7-4d47-ab82-dc4b80bd3bfe"

The full log is below. If I reboot this thing, will it tell me that it cannot find GRUB like the previous installation that shit the bed?

My assumption is that its simply telling me that it's enabled some sort of hibernation and will use the /swap for that.. but I'm totally on edge with this thing. I don't have a lot to set up with the system-side of things, so I put off trying to fix the old installation from the previous post until later.

Anyway, does anything here seem fishy?

edit:

UUID=842ddd01-963f-4cea-b04f-a52b6b719a16 /          ext4  errors=remount-ro 0   1
# /boot was on /dev/sdb1 during installation
UUID=5cfbef39-3eb7-41e6-8223-e6881b4f3286 /boot      ext4  defaults          0   2
# /home was on /dev/sdb3 during installation
UUID=4f30a4a2-9f28-4831-a22c-dc5b969c4f17 /home      ext4  defaults          0   2
# swap was on /dev/sdb2 during installation
UUID=e6480da4-95f0-4cf3-a047-a43ef09f978f none       swap  tf                0   0

A few months ago I got a new to me HP Proliant ML310e Gen8. For the most part it works well, but I went to add some drives to it yesterday and grub / whateverthefuck doesn't like the one and only kernel that is installed.

I'm running Ubuntu 20.04. I looked around saw guides like this. this, and this -- but I'm not sure if this will fix the issue.

After grub I get the ol'

---[end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]---

I think I need to run something with initramfs or something, but I just want to be sure before I go messing around.

The bad kernel listed is 5.11.0-27-generic. I'm a little out of my element with this part of things.

So I am reading the cgroups manpage because I want to learn about... cgroups. It tells me that for CGroups V1, if I want to use specific features, my kernel needs to be configured. Either I missed a section or it isn't there, because I don't see much mention of kernel requirements for CGroups V2.

So, my question is, is my kernel ready for CGroups, or should I recompile? Should I be able to support both V1 and V2? The manpage says V1 was a heap, so I was thinking I might continue without it... ... ...

CONFIG_CGROUPS=y

# CONFIG_BLK_CGROUP is not set

CONFIG_CGROUP_SCHED=y

# CONFIG_CGROUP_PIDS is not set

# CONFIG_CGROUP_RDMA is not set

CONFIG_CGROUP_FREEZER=y

# CONFIG_CGROUP_HUGETLB is not set

# CONFIG_CGROUP_DEVICE is not set

CONFIG_CGROUP_CPUACCT=y

# CONFIG_CGROUP_PERF is not set

# CONFIG_CGROUP_DEBUG is not set

# CONFIG_NET_CLS_CGROUP is not set

# CONFIG_CGROUP_NET_PRIO is not set

# CONFIG_CGROUP_NET_CLASSID is not set

edit: wowie markdown fix