You are Here:
Linux Lite 7.0 RC1 Released - See Release Announcement Section



Yesterdays updates

Author (Read 8565 times)

0 Members and 1 Guest are viewing this topic.

Re: Yesterdays updates
« Reply #22 on: February 05, 2022, 01:39:53 PM »
 

LarryB1607

  • Occasional Poster
  • **
  • 99
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: Intel I5

  • MEMORY: 6Gb

  • VIDEO CARD: intel onboard
I ran fsck on both partitions and was told that they were clean.  Earlier this week came a new kernel update.  It was listed as 5.4.0-96.101 or something like that.  Running a kernel identifier command said it is 5.4.0-97.  No problems with this one and have had several inconsequential boots.  Made a backup of it.  Would like to get rid of the problem kernels and have successfully done this before except last time when for some unknown reason2 of the 3 parts of 5.4.0-91were also removed which caused boot issues.  Thanks for all of the help to now.
 

Re: Yesterdays updates
« Reply #21 on: January 21, 2022, 02:10:44 PM »
 

LarryB1607

  • Occasional Poster
  • **
  • 99
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: Intel I5

  • MEMORY: 6Gb

  • VIDEO CARD: intel onboard
Same thing happened with both of the 1st suggestions.  I do not feel comfortable trying the forced fsck.  I will try again to make a live usb.  I tried LLOS 4.8  and 5.6 and had issues getting to a desktop. I was using etcher and had issues with that before.  I will try again with unetbootin which has worked for me in the past.  Not sure I will get to it today anymore.

Thanks for the replies
 

Re: Yesterdays updates
« Reply #20 on: January 21, 2022, 08:44:39 AM »
 

firenice03

  • Rockin' the FREE World
  • Global Moderator
  • Platinum Level Poster
  • *****
  • 1848
    Posts
  • Reputation: 284
  • Linux Lite Member
    • View Profile

  • CPU: AMD E2//Atom X5//AMD Phenom II X2

  • MEMORY: 4Gb

  • VIDEO CARD: AMD Mullin Radeon R2//Intel//AMD/ATI RS880

  • Kernel: 5.x
@LarryB1607
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: [Select]
sudo fsck.ext4 -y /dev/sdc1
or
Code: [Select]
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: [Select]
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 ..??...
LL4.8 UEFI 64 bit ASUS E402W - AMD E2 (Quad) 1.5Ghz  - 4GB - AMD Mullins Radeon R2
LL5.8 UEFI 64 bit Test UEFI Kangaroo (Mobile Desktop) - Atom X5-Z8500 1.44Ghz - 2GB - Intel HD Graphics
LL4.8 64 bit HP 6005- AMD Phenom II X2 - 8GB - AMD/ATI RS880 (HD4200)
LL3.8 32 bit Dell Inspiron Mini - Atom N270 1.6Ghz - 1GB - Intel Mobile 945GSE Express  -- Shelved
BACK LL5.8 64 bit Dell Optiplex 160 (Thin) - Atom 230 1.6Ghz - 4GB-SiS 771/671 PCIE VGA - Print Server
Running Linux Lite since LL2.2
 

Re: Yesterdays updates
« Reply #19 on: January 21, 2022, 07:26:59 AM »
 

LarryB1607

  • Occasional Poster
  • **
  • 99
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: Intel I5

  • MEMORY: 6Gb

  • VIDEO CARD: intel onboard
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.
 

Re: Yesterdays updates
« Reply #18 on: January 20, 2022, 08:33:48 PM »
 

firenice03

  • Rockin' the FREE World
  • Global Moderator
  • Platinum Level Poster
  • *****
  • 1848
    Posts
  • Reputation: 284
  • Linux Lite Member
    • View Profile

  • CPU: AMD E2//Atom X5//AMD Phenom II X2

  • MEMORY: 4Gb

  • VIDEO CARD: AMD Mullin Radeon R2//Intel//AMD/ATI RS880

  • Kernel: 5.x
@LarryB1607

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

Code: [Select]
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 ??
LL4.8 UEFI 64 bit ASUS E402W - AMD E2 (Quad) 1.5Ghz  - 4GB - AMD Mullins Radeon R2
LL5.8 UEFI 64 bit Test UEFI Kangaroo (Mobile Desktop) - Atom X5-Z8500 1.44Ghz - 2GB - Intel HD Graphics
LL4.8 64 bit HP 6005- AMD Phenom II X2 - 8GB - AMD/ATI RS880 (HD4200)
LL3.8 32 bit Dell Inspiron Mini - Atom N270 1.6Ghz - 1GB - Intel Mobile 945GSE Express  -- Shelved
BACK LL5.8 64 bit Dell Optiplex 160 (Thin) - Atom 230 1.6Ghz - 4GB-SiS 771/671 PCIE VGA - Print Server
Running Linux Lite since LL2.2
 

Re: Yesterdays updates
« Reply #17 on: January 20, 2022, 04:16:34 PM »
 

LarryB1607

  • Occasional Poster
  • **
  • 99
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: Intel I5

  • MEMORY: 6Gb

  • VIDEO CARD: intel onboard
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


 

Re: Yesterdays updates
« Reply #16 on: January 20, 2022, 03:24:47 PM »
 

firenice03

  • Rockin' the FREE World
  • Global Moderator
  • Platinum Level Poster
  • *****
  • 1848
    Posts
  • Reputation: 284
  • Linux Lite Member
    • View Profile

  • CPU: AMD E2//Atom X5//AMD Phenom II X2

  • MEMORY: 4Gb

  • VIDEO CARD: AMD Mullin Radeon R2//Intel//AMD/ATI RS880

  • Kernel: 5.x
@LarryB1607

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

Code: [Select]
fsck -y /dev/sdc1

If a permissions error - you may need elevated/sudo access..
Code: [Select]
sudo fsck -y /dev/sdc1
LL4.8 UEFI 64 bit ASUS E402W - AMD E2 (Quad) 1.5Ghz  - 4GB - AMD Mullins Radeon R2
LL5.8 UEFI 64 bit Test UEFI Kangaroo (Mobile Desktop) - Atom X5-Z8500 1.44Ghz - 2GB - Intel HD Graphics
LL4.8 64 bit HP 6005- AMD Phenom II X2 - 8GB - AMD/ATI RS880 (HD4200)
LL3.8 32 bit Dell Inspiron Mini - Atom N270 1.6Ghz - 1GB - Intel Mobile 945GSE Express  -- Shelved
BACK LL5.8 64 bit Dell Optiplex 160 (Thin) - Atom 230 1.6Ghz - 4GB-SiS 771/671 PCIE VGA - Print Server
Running Linux Lite since LL2.2
 

Re: Yesterdays updates
« Reply #15 on: January 20, 2022, 02:48:10 PM »
 

LarryB1607

  • Occasional Poster
  • **
  • 99
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: Intel I5

  • MEMORY: 6Gb

  • VIDEO CARD: intel onboard
Thanks for the reply, got same error

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

Re: Yesterdays updates
« Reply #14 on: January 20, 2022, 12:56:07 AM »
 

Jerry

  • Linux Lite Creator
  • Administrator
  • Platinum Level Poster
  • *****
  • 8810
    Posts
  • Reputation: 804
  • Linux Lite Member
    • View Profile
    • Linux Lite OS

  • CPU: Intel Core i9-10850K CPU @ 3.60GHz

  • MEMORY: 32Gb

  • VIDEO CARD: nVidia GeForce GTX 1650

  • Kernel: 5.x
Try putting the -y after fsck
 

Re: Yesterdays updates
« Reply #13 on: January 19, 2022, 05:52:45 PM »
 

LarryB1607

  • Occasional Poster
  • **
  • 99
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: Intel I5

  • MEMORY: 6Gb

  • VIDEO CARD: intel onboard
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'
 

Re: Yesterdays updates
« Reply #12 on: January 18, 2022, 08:51:52 AM »
 

LarryB1607

  • Occasional Poster
  • **
  • 99
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: Intel I5

  • MEMORY: 6Gb

  • VIDEO CARD: intel onboard
Thanks stevef, that is exactly what I was thinking now that I have a working kernel back.
 

Re: Yesterdays updates
« Reply #11 on: January 17, 2022, 04:20:39 PM »
 

stevef

  • Global Moderator
  • Gold Level Poster
  • *****
  • 842
    Posts
  • Reputation: 148
  • Linux Lite Member
    • View Profile

  • CPU: Intel Core i5-4460

  • MEMORY: 16Gb

  • Kernel: 5.x
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.


clueless
 

Re: Yesterdays updates
« Reply #10 on: January 17, 2022, 03:30:53 PM »
 

LarryB1607

  • Occasional Poster
  • **
  • 99
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: Intel I5

  • MEMORY: 6Gb

  • VIDEO CARD: intel onboard
It appears that I successfully restored 5.4.0-91.  I see that there are a bunch of updates.  Included in the list is the kernel 5.4.0-94.  Is there some way I can selectively choose the updates  or do I have to take them all?  thanks
 

Re: Yesterdays updates
« Reply #9 on: January 17, 2022, 02:52:16 PM »
 

LarryB1607

  • Occasional Poster
  • **
  • 99
    Posts
  • Reputation: 1
  • Linux Lite Member
    • View Profile

  • CPU: Intel I5

  • MEMORY: 6Gb

  • VIDEO CARD: intel onboard
Well, I guess I sometimes get confused by the updates.  I believe I mentioned that when I installed 5.4.0-94 and it seemed to be working, I used kernel remover and removed 5.4.0-92.  I did not remove 5.4.0-91 and it is still listed in the kernels to remove.  However all that is listed is 5.4.0-91 generic and the other 2 items associated with kernels is not there.  I only removed the items matching 5.4.0-92.  Tried several times to make a new live USB without success.  Fortunately my 5th time trying to boot 5.4.0-94 was successful so I can hopefully run Timeshist.
 

Re: Yesterdays updates
« Reply #8 on: January 17, 2022, 02:01:24 PM »
 

stevef

  • Global Moderator
  • Gold Level Poster
  • *****
  • 842
    Posts
  • Reputation: 148
  • Linux Lite Member
    • View Profile

  • CPU: Intel Core i5-4460

  • MEMORY: 16Gb

  • Kernel: 5.x
The dates of recent kernel changes on my system have been
5.4.0-91 Nov 30th 2021
5.4.0-92 Jan 5th 2022
5.4.0-94 Jan 11th 2022

I do not understand how the option to boot 5.4.0-91 which you had available on Jan 5th has disappeared.
Did you run any apt remove commands or the Lite Tweaks Kernel Remover at all in the meantime ?

Provided your timeshift image was made on a good working system your plan sounds ok.  That would be while you were reverted to 5.4.0-91 using GRUB, though your first post of Jan 16 talks about making a back up of 5.4.0-92 (which is partly why I am confused).  Obviously you will need to keep the timeshift archive safe through any changes you make while reverting to the older source.

If it works reliably, GRUB can be set to always boots the working kernel.  But that is not a great idea so you will need to know what the error actually is so that you can search for the issue and check for bug reports/fixes in subsequent kernels.

I am struggling to come up with a kernel issue scenario in which it can work intermittently so make sure the system boots reliably on whatever solution you come to.
clueless
 

 

-->
X Close Ad

Linux Lite 7.0 RC1 Released - See Release Announcement Section