Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic: New Install will not upgrade  (Read 261 times)

Offline bad_aptitude

  • User
  • Posts: 70
New Install will not upgrade
« on: 2021/06/14, 05:51:11 »

Not sure if this an Installation issue or a Dist-upgrade issue.
I installed siduction-21.1.0-cblues-kde-amd64-202102141913.iso  on a Lenovo Ideapd 3 Core i7 512 mb SSD.
The first time I used the non-EFI method but it didn't work.  I then successfully installed it with EFI.

When I did a dist-upgrade I got the following : (typed in from a mobile phone photo of my ideapad screen)

Code: [Select]
[           1.999132] ahci 0000:00:17.0: failed to start port 0 (errno= 12)
[           2:091412] xhci_hcd 0000:00:14.0: can't setup: -12
[           2.092122] xhci_hcd 0000:00:14.0 init 0000:00:14.0 fail, -12
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
...
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
mdadm error opening /dev/md?*: No such file or directory
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
...
mdadm: No arrays found in config file or automatically
mdadm: No arrays found in config file or automatically
Gave up waiting for suspend/resume device
mdadm: No arrays found in config file or automatically
Gave up waiting for root file system device. Common problems:
- Boot args (cat /proc/cmdline)
  - check rootdelay= (did this system unit wait long enough?
- Missing modules (cat /proc/modules; ls /dev)
ALERT! UUID=7dffddfb-d0f-42e6-852f-f56a205bcf81 does not exist. Dropping to shell
Busybox v1.30.1 (Debian 1:1.30.1-6*b2) built-in shell (ash)
Enter 'help' for a list of built-in commands.
(initramfs)




I could still log in with the old kernel
I tried reinstalling from the live USB and immediately did a dist upgrade and got the same result though the UUID referred to in the code  above was different.
I am using a separate home partition which was copied from an install on a a previous Ideapad.


To get the touchpad to work I added "pci=nocrs" to the /etc/default/grub file.


i'm thinking I may have corrupted the boot record from my attempt at a non-EFI installation which may have confused to EFI bootloader?
I tried again as a non-EFI install but the installation just hung after unpacking the live USB files. so I went back to the EFI based installation.
Is there some way to fix the installation so I can perform dist-upgrades?
Thanks


bad_aptitude


Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.597
Re: New Install will not upgrade
« Reply #1 on: 2021/06/14, 07:31:05 »
The essential line here is probably:
Code: [Select]
ALERT! UUID=7dffddfb-d0f-42e6-852f-f56a205bcf81 does not exist. This most probably means there is a UUID in /etc/fstab that does not match any device. In that situation systemd is very strict and drops you to Busybox until you fix your fstab. For that you need to chroot in. get the right UUID (sudo blkid) and exchange it for the erroneous one.

Offline towo

  • Global Moderator
  • User
  • *****
  • Posts: 2.533
Re: New Install will not upgrade
« Reply #2 on: 2021/06/14, 07:53:57 »
If the old kernel boots, but the new one not, provide the output of

Code: [Select]
df -h
ls -al /boot/
Ich gehe nicht zum Karneval, ich verleihe nur manchmal mein Gesicht.

Offline bad_aptitude

  • User
  • Posts: 70
Re: New Install will not upgrade
« Reply #3 on: 2021/06/14, 08:21:54 »
Hi Devil.

Indeed,  UUID=7dffddfb-d0cf-42e6-852f-f56a205bcf81 is in fstab

however  blkid gives:
Code: [Select]
root@kent-linux:/home/kent# blkid
/dev/nvme0n1p1: LABEL="SYSTEM_DRV" UUID="DA8D-3486" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="EFI system
partition" PARTUUID="11973189-3eec-4f27-b23b-96dbe2f86b56"
/dev/nvme0n1p3: LABEL="Windows-SSD" BLOCK_SIZE="512" UUID="64048DC1048D9728" TYPE="ntfs" PARTLABEL="Bas
ic data partition" PARTUUID="9f188224-daa3-4c5e-9a8d-d02720c4368a"
/dev/nvme0n1p4: LABEL="WINRE_DRV" BLOCK_SIZE="512" UUID="76728E53728E184F" TYPE="ntfs" PARTLABEL="Basic
 data partition" PARTUUID="139fa93a-85a4-4b73-9ecd-d0d90796e1f3"
/dev/nvme0n1p5: UUID="5340-3EE1" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="85960698-773b-1e46-8ce7-9ae9570
bd346"
/dev/nvme0n1p6: UUID="6d426a90-7906-431a-b68b-5119059f7859" TYPE="swap" PARTUUID="c72a1d6f-4fa9-924c-a5
d7-5c0b970afb9f"
/dev/nvme0n1p7: UUID="7dffddfb-d0cf-42e6-852f-f56a205bcf81" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="ed3
f59bc-b64a-bd47-8fbf-22baabf6f45e"
/dev/nvme0n1p8: UUID="95a5804f-eacd-4d21-b676-5db4db6ca663" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c26
74492-de19-cf4f-abd0-baef435cf53d"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="ea1f5287-4f09-40c6-a5c1-a77dfb23c3bb
"

As you can see this UUID corresponds to dev/nvme0n1p7 which is what I have set up as my root partition.(I piped blkid through grep using the culprit UUID and it matches exactly)
So it appears busybox can't find the partition even though it is clearly there.

I"ll follow up on Towo's suggestion separately to help avoid confusion.

Thanks
Kent

Offline bad_aptitude

  • User
  • Posts: 70
Re: New Install will not upgrade
« Reply #4 on: 2021/06/14, 08:28:59 »
Hi towo
Here is the output of df -h:
Code: [Select]
root@kent-linux:/home/kent# df -h
Filesystem      Size  Used Avail Use% Mounted on
udev            5.7G     0  5.7G   0% /dev
tmpfs           1.2G  1.6M  1.2G   1% /run
/dev/nvme0n1p7   20G  8.8G  9.8G  48% /
tmpfs           5.7G  198M  5.5G   4% /dev/shm
tmpfs           5.0M  4.0K  5.0M   1% /run/lock
tmpfs           5.7G   11M  5.7G   1% /tmp
/dev/nvme0n1p5  8.1G  288K  8.1G   1% /boot/efi
/dev/nvme0n1p8  328G  175G  137G  57% /home
tmpfs           1.2G  108K  1.2G   1% /run/user/1000
/dev/nvme0n1p3   90G   79G   11G  89% /media/kent/Windows-SSD

and  ls -al /boot/:
Code: [Select]
root@kent-linux:/home/kent# ls -al /boot/
total 97320
drwxr-xr-x  4 root root     4096 Jun 10 11:44 .
drwxr-xr-x 20 root root     4096 Jun 10 11:43 ..
-rw-r--r--  1 root root   219753 Feb 17 23:23 config-5.10.17-towo.1-siduction-amd64
-rw-r--r--  1 root root   222229 Jun  9 02:50 config-5.12.9-2-siduction-amd64
drwx------  3 root root     8192 Dec 31  1969 efi
drwxr-xr-x  5 root root     4096 Jun 10 11:43 grub
-rw-r--r--  1 root root 34957348 Jun 10 11:29 initrd.img-5.10.17-towo.1-siduction-amd64
-rw-r--r--  1 root root 36242950 Jun 10 11:44 initrd.img-5.12.9-2-siduction-amd64
-rw-r--r--  1 root root   182704 Aug 15  2019 memtest86+.bin
-rw-r--r--  1 root root   184884 Aug 15  2019 memtest86+_multiboot.bin
-rw-r--r--  1 root root  5187412 Feb 17 23:23 System.map-5.10.17-towo.1-siduction-amd64
-rw-r--r--  1 root root  5246495 Jun  9 02:50 System.map-5.12.9-2-siduction-amd64
-rw-r--r--  1 root root  8506112 Feb 17 23:23 vmlinuz-5.10.17-towo.1-siduction-amd64
-rw-r--r--  1 root root  8665568 Jun  9 02:50 vmlinuz-5.12.9-2-siduction-amd64



Thanks
bad_aptitude