Yesterdays updates

[stevef]

That's good news.

There is a facility for apt to hold back updates which can be applied to kernel - any package in the hold list does not get updates so is effectively frozen.

But as you can keep multiple kernels on your system and use GRUB to selectively boot them I'd go with letting any new kernel downloads but using GRUB to keep booting 5.4.0-91 for the time being as you seem to have had problems with both 5.4.0-92 and 5.4.0-94

When a new kernel comes you can try it once and if it doesn't work switch back to the working kernel using GRUB.

[LarryB1607]

Thanks stevef, that is exactly what I was thinking now that I have a working kernel back.

[LarryB1607]

Trying to run following command and get accompanying error.  What do I need to do to fix.  Thanks

(initramfs) fsck /dev/sdc1 -y
bash: syntax error near unexpected token `fsck'

[Valtam]

Try putting the -y after fsck

[LarryB1607]

Thanks for the reply, got same error

(initramfs) fsck -Y /dev/sdc1
bash: syntax error near unexpected token `fsck'

[firenice03]

[member=11699]LarryB1607[/member]

Context and flags are case sensitive... lower case Y

Code:

fsck -y /dev/sdc1

If a permissions error - you may need elevated/sudo access..

Code:

sudo fsck -y /dev/sdc1

[LarryB1607]

sudo fsck -y /dev/sdc1
[sudo] password for larrypc:
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)
fsck.ext2: Attempt to read block from filesystem resulted in short read while trying to open /dev/sdc1
Could this be a zero-length partition?

sudo fsck -y /dev/sdc1
[sudo] password for larrypc:
fsck from util-linux 2.34
e2fsck 1.45.5 (07-Jan-2020)

scd1 is an extended partition bootable.  It contains sdc5 LLOS and sdc6/home

[firenice03]

[member=11699]LarryB1607[/member]

You may want to paste the output of the following command... Might help those and ensure you run on the correct partitions

Code:

lsblk

I assume /dev/sdc is the USB drive?
sdc5 is root for LL
sd6 is LL /home
sdc1 is ?? (extended partition?) is this just data or unallocated, swap or something else..
is there sdc3 and sdc4 ?? /boot or swap


More so curious as to what's what...


those errors, I've seen - but usually when I've been working with LVM managed partitions. ?? but maybe something else... It should prompt to unmount if mounted.....


How were the partitions formatted - xfs, ext4, btrfs ??

[LarryB1607]

sdc1 is an extended partition created on a USB external HDD,  The rest of the HDD is formatted ntfs.  sdc1 is formatted ext4 and contains sdc5 & sdc6.  I have had the busybox error with every kernel update since 5.4.0-91.  I found the supposed solution to the error and then ran into the syntax error and then got the short read error.  Not sure why no kernel updates until these are causing this.

Thanks for all help so far.

[firenice03]

[member=11699]LarryB1607[/member]
Are you running on the your installed LL?
If so - its possible, if sdc5 & 6 are sub to sdc1 (?? - as its extended, havent messed with extended partitions for some time)
That it cannot check because those are mounted...

also... in your output fsck... it says "fsck.ext2"

You could try ... see if any better... although I assume the same...

Code:

sudo fsck.ext4 -y /dev/sdc1

or

Code:

sudo e2fsck -y /dev/sdc1

BUT what are the hopes in checking sdc1? its not the root/data partition... which root is /dev/sdc5 ...

If you wanting to check root - use sdc5 ..


BUT - if its mounted it wont run on a mounted system....
You can try a force at next boot.. you need to create a file in the root directory...

Code:

touch /forcefsck

That's assuming the system boots properly (not to a default shell)..
ELSE you could boot to a LiveUSB, attach the drive with LL and run fsck on the root partition on the usb drive from inside the Live Environment... *note the disk letters may change... sdc may become sdb or sde for example...


Hope that helps ..??...