What type of hardware are you using: Old laptop or computer What YunoHost version are you running: 11.3.0.2 (stable). How are you able to access your server: SSH Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: no
Describe your issue
What order do I try to fix things in? I will recreate this support request when I know that.
When trying to upgrade to bookworm I got - System update There are some pending migrations waiting to be run. Please go to Tools > Migrations to run them.
Failed to read info for audiobookshelf : Invalid version: â2.17.5~ynh1â
Failed to read info for netdata : Invalid version: â1.47.5~ynh1â
Failed to read info for nextcloud : Invalid version: â29.0.7~ynh2â
Failed to read info for photoprism : Invalid version: â2022.09.01~ynh4â
Failed to read info for syncthing : Invalid version: â1.28.1~ynh1â
Running migration 0027_migrate_to_bookwormâŚ
Starting migration to BookwormâŚ
Patching the sources.lists fileâŚ
Applying patch to workaround conflict issueâŚ
Starting main upgradeâŚ
Hi and thanks for the reply. Yes, I tried to upgrade in december and posted here but without success.
Iâve only just got back to it as I need to allocate a day at least to working through issues and trying fixes
Latest Logs
Migration to bookworm
Diagnosis log
ended_at: 2025-01-18 11:49:03.012559
error: 'Migration 0027_migrate_to_bookworm did not complete, aborting. Error: Failed
to run command ''aptitude full-upgrade cron rspamd- luajit- libluajit-5.1-2- --show-why
-o APT::Force-LoopBreak=1 -o Dpkg::Options::=''--force-confold'''''
interface: api
operation: tools_migrations_migrate_forward
parent: null
started_at: 2025-01-18 11:48:37.752941
success: false
yunohost_version: 11.3.0.2
============
2025-01-18 22:48:37,758: INFO - Running migration 0027_migrate_to_bookwormâŚ
2025-01-18 22:48:37,764: INFO - Starting migration to BookwormâŚ
2025-01-18 22:48:40,384: INFO - Patching the sources.lists fileâŚ
2025-01-18 22:48:40,995: DEBUG - Running: LC_ALL=C DEBIAN_FRONTEND=noninteractive APT_LISTCHANGES_FRONTEND=none aptitude update --quiet=2 -o=Dpkg::Use-Pty=0 -o "APT::Status-Fd=$YNH_STDINFO"
2025-01-18 22:48:45,535: INFO - Applying patch to workaround conflict issueâŚ
2025-01-18 22:48:45,554: DEBUG - Running: sed -i /var/lib/dpkg/status -e 's@Conflicts: apache2, bind9@Conflicts: apache2, bind9@g'
2025-01-18 22:48:45,573: INFO - Starting main upgradeâŚ
2025-01-18 22:48:45,593: DEBUG - Running: LC_ALL=C DEBIAN_FRONTEND=noninteractive APT_LISTCHANGES_FRONTEND=none aptitude markauto mariadb-server metronome rspamd php-common php-mbstring php-pear php-php-gettext php-xml php7.4-cli php7.4-common php7.4-curl php7.4-fpm php7.4-gd php7.4-intl php7.4-json php7.4-ldap php7.4-mbstring php7.4-mysql php7.4-opcache php7.4-readline php7.4-xml php8.2-cli php8.2-common php8.2-gd php8.2-mbstring php8.2-opcache php8.2-readline php8.2-xml php8.3 php8.3-apcu php8.3-bcmath php8.3-bz2 php8.3-cli php8.3-common php8.3-curl php8.3-fpm php8.3-gd php8.3-gmp php8.3-igbinary php8.3-imagick php8.3-imap php8.3-intl php8.3-ldap php8.3-mbstring php8.3-mysql php8.3-opcache php8.3-readline php8.3-redis php8.3-xml php8.3-zip --quiet=2 -o=Dpkg::Use-Pty=0 -o "APT::Status-Fd=$YNH_STDINFO"
2025-01-18 22:48:47,057: DEBUG - Package rspamd is not installed, cannot be marked/unmarked as automatically installed
2025-01-18 22:48:48,085: DEBUG - Running: YUNOHOST_API_RESTART_WILL_BE_HANDLED_BY_YUNOHOST=yes LC_ALL=C DEBIAN_FRONTEND=noninteractive APT_LISTCHANGES_FRONTEND=none aptitude hold yunohost moulinette ssowat yunohost-admin audiobookshelf-ynh-deps netdata-ynh-deps nextcloud-ynh-deps photoprism-ynh-deps --quiet=2 -o=Dpkg::Use-Pty=0 -o "APT::Status-Fd=$YNH_STDINFO"
2025-01-18 22:48:50,088: DEBUG - Running: sed -i /var/lib/dpkg/status -e 's@rspamd, @@g'
2025-01-18 22:48:50,108: DEBUG - Running: LC_ALL=C DEBIAN_FRONTEND=noninteractive APT_LISTCHANGES_FRONTEND=none aptitude full-upgrade cron rspamd- luajit- libluajit-5.1-2- --show-why -o APT::Force-LoopBreak=1 -o Dpkg::Options::='--force-confold' --quiet=2 -o=Dpkg::Use-Pty=0 -o "APT::Status-Fd=$YNH_STDINFO"
2025-01-18 22:48:52,136: DEBUG - cron is already installed at the latest version (3.0pl1-162), so it will not be upgraded
2025-01-18 22:48:52,136: DEBUG - Package rspamd is not installed, so it will not be removed
2025-01-18 22:48:52,137: DEBUG - Package luajit is not installed, so it will not be removed
2025-01-18 22:48:52,137: DEBUG - Package libluajit-5.1-2 is not installed, so it will not be removed
2025-01-18 22:48:52,137: DEBUG - cron is already installed at the latest version (3.0pl1-162), so it will not be upgraded
2025-01-18 22:48:52,137: DEBUG - Package rspamd is not installed, so it will not be removed
2025-01-18 22:48:52,137: DEBUG - Package luajit is not installed, so it will not be removed
2025-01-18 22:48:52,137: DEBUG - Package libluajit-5.1-2 is not installed, so it will not be removed
2025-01-18 22:48:52,137: DEBUG - The following partially installed packages will be configured:
2025-01-18 22:48:52,138: DEBUG - grub-pc
2025-01-18 22:48:52,138: DEBUG - No packages will be installed, upgraded, or removed.
2025-01-18 22:48:52,138: DEBUG - 0 packages upgraded, 0 newly installed, 0 to remove and 95 not upgraded.
2025-01-18 22:48:52,138: DEBUG - Need to get 0 B of archives. After unpacking 0 B will be used.
2025-01-18 22:48:52,161: DEBUG - Setting up grub-pc (2.06-13+deb12u1) ...
2025-01-18 22:48:52,161: INFO - [....................] > 0.0% Installing grub-pc
2025-01-18 22:48:52,963: DEBUG - grub-pc: Running grub-install ...
2025-01-18 22:48:52,984: DEBUG - Installing for i386-pc platform.
2025-01-18 22:48:56,440: DEBUG - grub-install: error: unable to identify a filesystem in hostdisk//dev/sda; safety check can't be performed.
2025-01-18 22:48:56,470: DEBUG - grub-install failure for /dev/sda
2025-01-18 22:48:56,473: DEBUG - You must correct your GRUB install devices before proceeding:
2025-01-18 22:48:56,473: DEBUG -
2025-01-18 22:48:56,474: DEBUG - DEBIAN_FRONTEND=dialog dpkg --configure grub-pc
2025-01-18 22:48:56,474: DEBUG - dpkg --configure -a
2025-01-18 22:48:56,575: DEBUG - dpkg: error processing package grub-pc (--configure):
2025-01-18 22:48:56,576: DEBUG - installed grub-pc package post-installation script subprocess returned error exit status 1
2025-01-18 22:48:56,626: DEBUG - Errors were encountered while processing:
2025-01-18 22:48:56,627: DEBUG - grub-pc
2025-01-18 22:48:56,816: WARNING - E: Sub-process /usr/bin/dpkg returned an error code (1)
2025-01-18 22:48:56,835: DEBUG - Setting up grub-pc (2.06-13+deb12u1) ...
2025-01-18 22:48:57,579: WARNING - grub-pc: Running grub-install ...
2025-01-18 22:48:57,592: WARNING - Installing for i386-pc platform.
2025-01-18 22:49:00,832: WARNING - grub-install: error: unable to identify a filesystem in hostdisk//dev/sda; safety check can't be performed.
2025-01-18 22:49:00,856: WARNING - grub-install failure for /dev/sda
2025-01-18 22:49:00,859: WARNING - You must correct your GRUB install devices before proceeding:
2025-01-18 22:49:00,860: WARNING -
2025-01-18 22:49:00,860: WARNING - DEBIAN_FRONTEND=dialog dpkg --configure grub-pc
2025-01-18 22:49:00,860: WARNING - dpkg --configure -a
2025-01-18 22:49:00,958: WARNING - dpkg: error processing package grub-pc (--configure):
2025-01-18 22:49:00,959: WARNING - installed grub-pc package post-installation script subprocess returned error exit status 1
2025-01-18 22:49:01,006: WARNING - Errors were encountered while processing:
2025-01-18 22:49:01,007: WARNING - grub-pc
2025-01-18 22:49:03,008: ERROR - Migration 0027_migrate_to_bookworm did not complete, aborting. Error: Failed to run command 'aptitude full-upgrade cron rspamd- luajit- libluajit-5.1-2- --show-why -o APT::Force-LoopBreak=1 -o Dpkg::Options::='--force-confold''
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/yunohost/tools.py", line 786, in tools_migrations_run
migration.run()
File "/usr/lib/python3/dist-packages/yunohost/migrations/0027_migrate_to_bookworm.py", line 204, in run
aptitude_with_progress_bar(
File "/usr/lib/python3/dist-packages/yunohost/utils/system.py", line 315, in aptitude_with_progress_bar
raise YunohostError(
yunohost.utils.error.YunohostError: Failed to run command 'aptitude full-upgrade cron rspamd- luajit- libluajit-5.1-2- --show-why -o APT::Force-LoopBreak=1 -o Dpkg::Options::='--force-confold''
2. Diagnosis
=================================
Base system (basesystem)
=================================
[INFO] Server hardware architecture is bare-metal amd64
- Server model is Gigabyte Technology Co., Ltd. X58A-UD3R
[INFO] Server is running Linux kernel 6.1.0-28-amd64
[INFO] Server is running Debian 12.8
[INFO] Server is running YunoHost 11.3.0.2 (stable)
- yunohost version: 11.3.0.2 (stable)
- yunohost-admin version: 11.3.0 (stable)
- moulinette version: 11.3.0 (stable)
- ssowat version: 11.3.0 (stable)
=================================
Internet connectivity (ip)
=================================
[SUCCESS] Domain name resolution is working!
[SUCCESS] The server is connected to the Internet through IPv4!
- Global IP: xx.xx.xx.xx
- Local IP: 192.168.50.5
[WARNING] The server does not have working IPv6.
- IPv6 should usually be automatically configured by the system or your provider if it's available. Otherwise, you might need to configure a few things manually as explained in the documentation here: https://yunohost.org/ipv6.
=================================
DNS records (dnsrecords)
=================================
[SUCCESS] DNS records are correctly configured for domain maindomain.tld (category basic)
[SUCCESS] DNS records are correctly configured for domain maindomain.tld (category mail)
[SUCCESS] DNS records are correctly configured for domain maindomain.tld (category xmpp)
[SUCCESS] DNS records are correctly configured for domain maindomain.tld (category extra)
[INFO] Domain domain2.tld is based on a special-use top-level domain (TLD) such as .local or .test and is therefore not expected to have actual DNS records.
=================================
Ports exposure (ports)
=================================
[SUCCESS] Port 22 is reachable from the outside.
- Exposing this port is needed for admin features (service ssh)
[SUCCESS] Port 25 is reachable from the outside.
- Exposing this port is needed for email features (service postfix)
[SUCCESS] Port 80 is reachable from the outside.
- Exposing this port is needed for web features (service nginx)
[SUCCESS] Port 443 is reachable from the outside.
- Exposing this port is needed for web features (service nginx)
[SUCCESS] Port 587 is reachable from the outside.
- Exposing this port is needed for email features (service postfix)
[SUCCESS] Port 993 is reachable from the outside.
- Exposing this port is needed for email features (service dovecot)
[SUCCESS] Port 5222 is reachable from the outside.
- Exposing this port is needed for xmpp features (service metronome)
[SUCCESS] Port 5269 is reachable from the outside.
- Exposing this port is needed for xmpp features (service metronome)
[SUCCESS] Port 22000 is reachable from the outside.
- Exposing this port is needed for [?] features (service syncthing)
=================================
Web (web)
=================================
[INFO] Domain domain2.tld is based on a special-use top-level domain (TLD) such as .local or .test and is therefore not expected to be exposed outside the local network.
[SUCCESS] Domain maindomain.tld is reachable through HTTP from outside the local network.
[SUCCESS] Domain audiobookshelf.maindomain.tld is reachable through HTTP from outside the local network.
=================================
Email (mail)
=================================
[SUCCESS] The SMTP mail server is able to send emails (outgoing port 25 is not blocked).
[SUCCESS] The SMTP mail server is reachable from the outside and therefore is able to receive emails!
[SUCCESS] Your reverse DNS is correctly configured!
[SUCCESS] The IPs and domains used by this server do not appear to be blacklisted
[SUCCESS] 0 pending emails in the mail queues
=================================
Services status check (services)
=================================
[SUCCESS] Service audiobookshelf is running!
[SUCCESS] Service dnsmasq is running!
[SUCCESS] Service dovecot is running!
[SUCCESS] Service fail2ban is running!
[SUCCESS] Service metronome is running!
[SUCCESS] Service mysql is running!
[SUCCESS] Service netdata is running!
[SUCCESS] Service nginx is running!
[SUCCESS] Service photoprism is running!
[SUCCESS] Service php7.4-fpm is running!
[SUCCESS] Service php8.3-fpm is running!
[SUCCESS] Service postfix is running!
[SUCCESS] Service postgresql is running!
[SUCCESS] Service redis-server is running!
[ERROR] Service rspamd is dead :(
- You can try to restart the service, and if it doesn't work, have a look at the service logs in the webadmin (from the command line, you can do this with 'yunohost service restart rspamd' and 'yunohost service log rspamd').
[SUCCESS] Service slapd is running!
[SUCCESS] Service ssh is running!
[SUCCESS] Service syncthing is running!
[SUCCESS] Service yunohost-api is running!
[SUCCESS] Service yunohost-firewall is running!
[SUCCESS] Service yunomdns is running!
=================================
System resources (systemresources)
=================================
[SUCCESS] The system still has 6.0 GiB (77%) RAM available out of 7.8 GiB.
[SUCCESS] The system has 976 MiB of swap!
- Please be careful and aware that if the server is hosting swap on an SD card or SSD storage, it may drastically reduce the life expectancy of the device.
[SUCCESS] Storage / (on device /dev/mapper/system-root) still has 405 GiB (91.4%) space left (out of 443 GiB)!
[SUCCESS] Storage /boot (on device /dev/sdb1) still has 109 MiB (51%) space left (out of 213 MiB)!
[SUCCESS] Storage /home/accessy/apps/audiobookshelf (on device /dev/mapper/system-root) still has 405 GiB (91.4%) space left (out of 443 GiB)!
[SUCCESS] Storage /home/yunohost.app/audiobookshelf/data (on device /dev/mapper/system-audiobookshelf) still has 124 GiB (44%) space left (out of 279 GiB)!
[SUCCESS] Storage /home/yunohost.app/nextcloud/data (on device /dev/mapper/system-nextcloud) still has 331 GiB (35%) space left (out of 933 GiB)!
[SUCCESS] Storage /home/yunohost.multimedia/accessy/audiobookshelf (on device /dev/mapper/system-audiobookshelf) still has 124 GiB (44%) space left (out of 279 GiB)!
=================================
System configurations (regenconf)
=================================
=================================
Applications (apps)
=================================
[SUCCESS] All installed apps respect basic packaging practices
Type dpkg --help for help about installing and deinstalling packages [*];
Use âaptâ or âaptitudeâ for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;
Options marked [*] produce a lot of output - pipe it through âlessâ or âmoreâ !
ok. I think I worked that out. I ran pkg --configure -a
root@@@@@:~# root@@@@@:~# dpkg --configure -a
Setting up grub-pc (2.06-13+deb12u1) âŚ
grub-pc: Running grub-install âŚ
Installing for i386-pc platform.
grub-install: error: unable to identify a filesystem in hostdisk//dev/sda; safet y check canât be performed.
grub-install failure for /dev/sda
You must correct your GRUB install devices before proceeding:
DEBIAN_FRONTEND=dialog dpkg --configure grub-pc
dpkg --configure -a
dpkg: error processing package grub-pc (âconfigure):
installed grub-pc package post-installation script subprocess returned error ex it status 1
Errors were encountered while processing:
grub-pc
If that does not solve the problem, please post the results of
$ sudo lsblk
and of
$ sudo fdisk -l
Please take the trouble to format your reply, so that it is easy to read for visitors of the forum; for example, use the </> button to format the output on your screen:
Apologies, it was noted in another post but I do this so infrequently I forgot. I have run the commands in order and hopefully formatted correctly for you.
sudo dpkg --configure -a
root@****:~# sudo dpkg --configure -a
Setting up grub-pc (2.06-13+deb12u1) ...
grub-pc: Running grub-install ...
Installing for i386-pc platform.
grub-install: error: unable to identify a filesystem in hostdisk//dev/sda; safety check can't be performed.
grub-install failure for /dev/sda
You must correct your GRUB install devices before proceeding:
DEBIAN_FRONTEND=dialog dpkg --configure grub-pc
dpkg --configure -a
dpkg: error processing package grub-pc (--configure):
installed grub-pc package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
grub-pc
sudo apt-get install -f
root@****:~# sudo apt-get install -f
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 95 not upgraded.
1 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Setting up grub-pc (2.06-13+deb12u1) ...
grub-pc: Running grub-install ...
Installing for i386-pc platform.
grub-install: error: unable to identify a filesystem in hostdisk//dev/sda; safety check can't be performed.
grub-install failure for /dev/sda
You must correct your GRUB install devices before proceeding:
DEBIAN_FRONTEND=dialog dpkg --configure grub-pc
dpkg --configure -a
dpkg: error processing package grub-pc (--configure):
installed grub-pc package post-installation script subprocess returned error exit status 1
Errors were encountered while processing:
grub-pc
E: Sub-process /usr/bin/dpkg returned an error code (1)
âThanksâ for not reading the post I linked to, and executing the same commands that you already know wonât work
Please take the trouble to actually read the post (I had to do it as well). If you have trouble, the post that starts with "I think I have found the solution. " may have the solution.
Please try those steps first, but do not reboot yet.
The output of lsblk and fdisk -l point out the cause of the trouble. It shouldnât be a problem, but it seems some part of the system has trouble that your root filesystem is on /dev/sdb, and not coping with a full disk LVM on /dev/sda.
Iâm quite sure that your server has been rebooted once in a while, so GRUB is installed.
Would you post the output of:
$ sudo cat /boot/grub/grub.cfg|grep /dev
I expect a line starting with linux and having something like root=/dev/sdb.... ; if it has /dev/sda there then your previous commands should have worked.
With that confirmed, install GRUB on /dev/sdb:
$ sudo grub-install /dev/sdb
With no errors, continue to tell dpkg/apt to use /dev/sdb:
$ sudo dpkg-reconfigure grub-pc
You have to check the output of the commands, or maybe change a bit here or there: it has been a long time since I had a system that booted off the second disk, or that had an MBR / grub-pc.
Solving this bit will bring your system back in a normal state and allow you to (finally) upgrade anything. That is good Having something go wrong here, will make your system not boot. In that case, you canât boot, but the system itself is not broken: youâll need a system rescue USB stick to repair GRUB in that case. Not bad per se, but annoying for sure
apologies and I will do better. I appreciate your time and will try to note waste any more of it.
I found the section" I think I have found the solution" and ran the commands. Here is the output and I did not reboot.
root@***:~# sudo -i
root@***:~# cd /boot/grub
root@***:/boot/grub# rm grubenv
root@***:/boot/grub# grub-editenv grubenv create
root@***:/boot/grub# grub-editenv grubenv set default=0
root@***:/boot/grub# grub-editenv grubenv list
default=0
root@***:/boot/grub# update-grub
Generating grub configuration file ...
/usr/sbin/grub-probe: warning: Couldn't find physical volume `pv1'. Some modules may be missing from core image..
Found linux image: /boot/vmlinuz-6.1.0-28-amd64
Found initrd image: /boot/initrd.img-6.1.0-28-amd64
Found linux image: /boot/vmlinuz-5.10.0-33-amd64
Found initrd image: /boot/initrd.img-5.10.0-33-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
I ran your first command and did not get the expected output so I didnt go further
root@***:/boot/grub# sudo cat /boot/grub/grub.cfg|grep /dev
linux /vmlinuz-6.1.0-28-amd64 root=/dev/mapper/system-root ro quiet
linux /vmlinuz-6.1.0-28-amd64 root=/dev/mapper/system-root ro quiet
linux /vmlinuz-6.1.0-28-amd64 root=/dev/mapper/system-root ro single
linux /vmlinuz-5.10.0-33-amd64 root=/dev/mapper/system-root ro quiet
linux /vmlinuz-5.10.0-33-amd64 root=/dev/mapper/system-root ro single
I did some research and tried these output commands
root@****:~# df -h /
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/system-root 468G 39G 406G 9% /
I tried to check the output commands as you suggested and look for information on how to find root. Hope this helped. but I wish I hadnât tried to add that second larger drive which put the filesystem on sbd
root@***:/boot/grub# sudo cat /boot/grub/grub.cfg|grep /dev
linux /vmlinuz-6.1.0-28-amd64 root=/dev/mapper/system-root ro quiet
My bad, it slipped my mind that your / is on LVM. This matches the output of your lsblk.
I thought of pasting sections of my /boot/grub/grub.cfg, but as my system boots of LVM it has some options in it you wonât need.
I found a (very) old thread about a similar situation as yours:
boot from other than /dev/sda*
/ on LVM
/boot on regular partition
The difference being that it is on Arch.
He also got
/usr/sbin/grub-probe: warning: Couldn't find physical volume `pv1'. Some modules may be missing from core image..
and writes
Your server is at home, is it not? You ⌠could give it a try (What, there exists no YOLO-emoticon?)
Donât fret⌠You needed the space, I guess, and I think weâre half way through to a working situation
Do check your /etc/fstab though, to see that your partitions are referenced by UUID or that the correct device is refered to.
Looking at the sizes of the disks, is one of them an SSD and the other spinning rust? LVM has some tricks that allow an HDD drive to be cached by an SSD, but that is an exercise for another day
Yes my server is at home
I did need the space. I worked through a guide posted here to accomplish it but it took a while.
root@***:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/system-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=2b52732d-cf12-45db-9b01-13b2fdfe1011 /boot ext4 defaults 0 2
/dev/mapper/system-swap none swap sw 0 0
# Automount nextcloud located sba
/dev/system/nextcloud /home/yunohost.app/nextcloud/data ext4 defaults 0 2
# Automount audiobookshelf located at sba
/dev/system/audiobookshelf /home/yunohost.app/audiobookshelf/data ext4 defaults 0 2
/var/www/audiobookshelf /home/accessy/apps/audiobookshelf none defaults,bind 0 0
/home/yunohost.app/audiobookshelf/data /home/yunohost.multimedia/accessy/audiobookshelf none defaults,bind 0 0
root@***:~#
The interwebs indicated that I should use the âblkidâ command to show all drives andf their UUID. From this I got the below info. I recall I had a lot of difficulty sorting out the boot drive which was the ssd and it was originally on sda1. when I put in the second drive it became sdb and the new drive became sda. Is the fstab indicating it still thinks its at sda1?
I followed rgis guide on the Yunohost help section to configure LVM
Follow up. I looked up the command and it seems to indicate that I should have run it after setting up LVM so Ill give it a try.
root@****:~# grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
/usr/sbin/grub-probe: warning: Couldn't find physical volume `pv1'. Some modules may be missing from core image..
Found linux image: /boot/vmlinuz-6.1.0-28-amd64
Found initrd image: /boot/initrd.img-6.1.0-28-amd64
Found linux image: /boot/vmlinuz-5.10.0-33-amd64
Found initrd image: /boot/initrd.img-5.10.0-33-amd64
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
done
root@druss:~#
I checked the fstab again after reboot
root@****:~# cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# systemd generates mount units based on this file, see systemd.mount(5).
# Please run 'systemctl daemon-reload' after making changes here.
#
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/mapper/system-root / ext4 errors=remount-ro 0 1
# /boot was on /dev/sda1 during installation
UUID=2b52732d-cf12-45db-9b01-13b2fdfe1011 /boot ext4 defaults 0 2
/dev/mapper/system-swap none swap sw 0 0
# Automount nextcloud located sba
/dev/system/nextcloud /home/yunohost.app/nextcloud/data ext4 defaults 0 2
# Automount audiobookshelf located at sba
/dev/system/audiobookshelf /home/yunohost.app/audiobookshelf/data ext4 defaults 0 2
/var/www/audiobookshelf /home/accessy/apps/audiobookshelf none defaults,bind 0 0
/home/yunohost.app/audiobookshelf/data /home/yunohost.multimedia/accessy/audiobookshelf none defaults,bind 0 0
Also, thinking to the future . Will this happen everytime I do a major upgrade? If so should I look at restoring the system to a more standard config. That Is boot and file system on sda (ssd) and program data using LVM on sdb?
yes, but itâs life in computers is it not? I have nearly put a computer through a wall a few times in my career. Most notably trying to configure BNC network cards under dos in the old days. Followed the same steps across multiple computers and one wouldnât work no matter what I did. Came in the next day and followed the same steps ⌠worked
Luckily we were in short supply so it lived to torture me another day
no luck
root@***:~# sudo grub-install /dev/sdb
Installing for i386-pc platform.
grub-install: error: unable to identify a filesystem in hostdisk//dev/sdb; safety check can't be performed.
Hahah, computers in those times would have broken your back when throwing them out of the window. Laptops and singre board computers are way more suitable for that (and somewhat friendlier to innocent passers by outside of the windowâŚ)
With grub nor dpkg participating in a solution, we could try re-installing grub:
root@***:~# sudo apt purge grub-pc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
grub-pc-bin grub2-common
Use 'sudo apt autoremove' to remove them.
The following packages will be REMOVED:
grub-pc*
0 upgraded, 0 newly installed, 1 to remove and 95 not upgraded.
1 not fully installed or removed.
After this operation, 564 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 73352 files and directories currently installed.)
Removing grub-pc (2.06-13+deb12u1) ...
Processing triggers for man-db (2.11.2-2) ...
(Reading database ... 73341 files and directories currently installed.)
Purging configuration files for grub-pc (2.06-13+deb12u1) ...
root@***:~#
root@***:~# sudo apt update
Hit:2 http://ftp.debian.org/debian bookworm InRelease
Hit:3 http://security.debian.org/debian-security bookworm-security InRelease
Get:4 http://ftp.debian.org/debian bookworm-updates InRelease [55.4 kB]
Get:5 https://packages.sury.org/php bookworm InRelease [7,551 B]
Get:6 https://packages.sury.org/php bookworm/main amd64 Packages [255 kB]
Hit:1 https://forge.yunohost.org/debian bookworm InRelease
Fetched 318 kB in 4s (87.6 kB/s)
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
95 packages can be upgraded. Run 'apt list --upgradable' to see them.
Root@****:~#
Had trouble here but after some internet research went with the last command. Hope it is the one you intended
root@***:~# sudo install - f
install: cannot stat '-': No such file or directory
root@***:~# sudo install -f
install: invalid option -- 'f'
Try 'install --help' for more information.
root@***:~# sudo install -f
install: invalid option -- 'f'
Try 'install --help' for more information.
root@***:~# sudo install - f # fix loose ends
install: cannot stat '-': No such file or directory
root@***:~# sudo apt install -f
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
grub-pc-bin grub2-common
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 95 not upgraded.
root@*****:~#
root@***:~# sudo dpkg --configure -a
root@***:~#
It failed here with an error code so I stopped at this step.
root@***:~# sudo apt install grub-pc
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following NEW packages will be installed:
grub-pc
0 upgraded, 1 newly installed, 0 to remove and 95 not upgraded.
Need to get 137 kB of archives.
After this operation, 564 kB of additional disk space will be used.
Get:1 http://ftp.debian.org/debian bookworm/main amd64 grub-pc amd64 2.06-13+deb12u1 [137 kB]
Fetched 137 kB in 2s (89.8 kB/s)
Preconfiguring packages ...
Selecting previously unselected package grub-pc.
(Reading database ... 73342 files and directories currently installed.)
Preparing to unpack .../grub-pc_2.06-13+deb12u1_amd64.deb ...
Unpacking grub-pc (2.06-13+deb12u1) ...
Setting up grub-pc (2.06-13+deb12u1) ...
Creating config file /etc/default/grub with new version
grub-pc: Running grub-install ...
You must correct your GRUB install devices before proceeding:
DEBIAN_FRONTEND=dialog dpkg --configure grub-pc
dpkg --configure -a
dpkg: error processing package grub-pc (--configure):
installed grub-pc package post-installation script subprocess returned error exit status 1
Processing triggers for man-db (2.11.2-2) ...
Errors were encountered while processing:
grub-pc
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@***:~#