Re: kernel errors - SOLVED

[Richmond <dnomhcir@gmx.com>]

Richmond <richmond@criptext.com> writes:

> It may be a coincidence but yesterday I installed some
> libguestfs-tools. Now I see errors when booting, which also appear in
> /var/log/messages:
>
> kernel: [    9.506798] sr 3:0:0:0: [sr0] tag#12 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE cmd_age=2s
> kernel: [    9.507009] sr 3:0:0:0: [sr0] tag#12 Sense Key : Not Ready [current] 
> kernel: [    9.507146] sr 3:0:0:0: [sr0] tag#12 Add. Sense: Medium not present - tray closed
> kernel: [    9.507304] sr 3:0:0:0: [sr0] tag#12 CDB: Read(10) 28 00 00 07 ff fc 00 00 02 00
> kernel: [    9.507731] sr 3:0:0:0: [sr0] tag#31 unaligned transfer
> kernel: [    9.513520] sr 3:0:0:0: [sr0] tag#13 unaligned transfer
> kernel: [    9.529995] sr 3:0:0:0: [sr0] tag#14 unaligned transfer

These errors started occurring again. This time I knew what I had done, I
commented out a line in fstab referencing a swap space, because the
system had two swap spaces defined and I wanted to use one for something
else. What I overlooked was that this swap space was also the resume
space.

During the boot there were other messages which did not appear in the
journal so I filmed them with a smart phone:

Running /scripts/local-block..

These occurred over and over, but allowed me to find this site:

https://tipstricks.itmatrix.eu/solving-the-running-scripts-local-block-loop-while-booting-in-linux/

Which explained the problem and how to fix it. I had already edited:

/etc/initramfs-tools/conf.d/resume

To use the other swap space. But this did not help because I missed this
crucial step:

sudo update-initramfs -u

After I did this, the errors went away.

I don't know why the errors reference sr0, it's a mystery.