Update Errors, also on fix commands!

Hey folks how about not hijacking my topic. Now I can start again cause your things made me lose track thanks … Sigh

So lets forget all others their issues, since somethings are server specific.

Where was i oh the empty response so yeah.

now I TRY grep -nr ‘HARDDISK’ /boot/

Also empty.

Okey lets try grub-install; fine no issues reported

Fix commands still give issues;
root@easycomp:~# sudo apt install --fix-broken
Pakketlijsten worden ingelezen… Klaar
Boom van vereisten wordt opgebouwd
De statusinformatie wordt gelezen… Klaar
Het volgende pakket is automatisch geïnstalleerd en is niet langer nodig:
linux-image-4.19.0-12-amd64
Gebruik ‘sudo apt autoremove’ om het te verwijderen.
0 opgewaardeerd, 0 nieuw geïnstalleerd, 0 te verwijderen en 37 niet opgewaardeerd.
1 niet volledig geïnstalleerd of verwijderd.
Na deze bewerking zal er 0 B extra schijfruimte gebruikt worden.
Instellen van grub-pc (2.02+dfsg1-20+deb10u3) …
/dev/disk/by-id/ata-VBOX_HARDDISK_VB8274e419-47df3d29 does not exist, so cannot grub-install to it!
You must correct your GRUB install devices before proceeding:

dpkg-reconfigure grub-pc
dpkg: fout bij verwerken van pakket grub-pc (–configure):
subproces van pakket grub-pc werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
Fouten gevonden tijdens verwerken van:
grub-pc
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@easycomp:~# sudo dpkg --configure -a
Instellen van grub-pc (2.02+dfsg1-20+deb10u3) …
/dev/disk/by-id/ata-VBOX_HARDDISK_VB8274e419-47df3d29 does not exist, so cannot grub-install to it!
You must correct your GRUB install devices before proceeding:

EasyCompZLD, to me the problem looks the same as to the rest of us.
If not, we should start another thread?

Hi,
it looks like I solved my problem by following the instructions from here - grub related error on 5.5.23 update - Updates/Upgrades - openmediavault

The only thing that didnt work was to see HDD from debconf-set-selections so I hade to list /dev/disk/by-id$ ls

Yes, the issue is pretty much the same for all 3 people here …

Can you elaborate on what you did exactly ?

What about running :

sudo DEBIAN_FRONTEND=text dpkg --configure -a

(N.B. @someonesusername you should try this too)

Sure,

  1. First I tried to see my old and new HDD
sudo debconf-show grub-pc | grep -wi install_devices | awk -F: '{print $2}

but I only got the old one

 /dev/disk/by-id/ata-OCZ_VERTEX_PLUS_19JE1KI41W61AY8PEP3Y
  1. Then I checked the new HDD by listing
$ cd  /dev/disk/by-id/
/dev/disk/by-id$ ls
ata-ST9250315AS_6VC0JAYW
  1. Then I changed it to the new one
echo grub-pc grub-pc/install_devices multiselect /dev/disk/by-id/ata-ST9250315AS_6VC0JAYW | sudo debconf-set-selections
$ sudo DEBIAN_FRONTEND=text dpkg --configure -a

gave just a new line (did this after the above…)

Looks like this worked ! I indeed had to choose where to install grub :

Le chargeur d'amorçage GRUB était précédemment installé sur un disque qui n'est plus présent ou dont l'identifiant unique a changé pour une raison ou une autre

(installed it on /dev/sda for my configuration), and then grub was reconfigured. I could then update the system with yunohost tools upgrade :slight_smile:
Thanks a lot @tomas for the link you found !

It worked for me without doing that :wink:

Cache issue double post…

Because it’s my candy and you are taking it from me :lollipop: :cry:.
Like stealing candy from a baby. No actually im easily distracted sometimes, ADHD YuKnow.
So getting answers or messages which are similar but not the same since your drives are not my drives and vice versa. So then some commands differ. I.e. grep -nr “OCZ_VERTEX_PLUS”
Yeah thank you for almost messing my server rack…
I actually ran that command then I taught waaaaaait and had to call out the swat team to breach it and force stop it.

@Aleks So please give me a point in the right direction to the fix which is for me.

Yes …

Yeah hey, so I that and the terminal pompt became stuk then it what disconnected and idk now hat is happening but the system(VM) and the hosted websites had become really unstable and sometimes even unusable, which then gives me to much delay and thats exactly why I choose for yuno because I was convinced that AIO solution was going to make my life just les stressful. So it seems that the machine is running but:

Oke sys back up and now ?

[quote=“EasyCompZLD, post:51, topic:14496”]

Ruunning the fix command stil gives issues, and the server overal is very very unstable? Mind to go via tv or something in to detail? :im afraid of losing my stuff again1!

i stil cannot update
:frowning:

So neither this

nor that

allowed you to chose the disk where you wanted to reinstall grub properly, so that it didn’t prevent the upgrade anymore?

Equals error.

 @easycomp:~# sudo DEBIAN_FRONTEND=newt dpkg --configure -a
Instellen van grub-pc (2.02+dfsg1-20+deb10u3) ...
debconf: kan het frontend niet initialiseren: Newt
debconf: (Can't locate Debconf/FrontEnd/Newt.pm in @INC (you may need to install the Debconf::FrontEnd::Newt module) (@INC contains: /etc/perl /usr/local/lib/x86_64-linux-gnu/perl/5.28.1 /usr/local/share/perl/5.28.1 /usr/lib/x86_64-linux-gnu/perl5/5.28 /usr/share/perl5 /usr/lib/x86_64-linux-gnu/perl/5.28 /usr/share/perl/5.28 /usr/local/lib/site_perl /usr/lib/x86_64-linux-gnu/perl-base) at (eval 18) line 2.)
debconf: er wordt teruggevallen op frontend: Noninteractive
/dev/disk/by-id/ata-VBOX_HARDDISK_VB8274e419-47df3d29 does not exist, so cannot grub-install to it!
You must correct your GRUB install devices before proceeding:

  dpkg-reconfigure grub-pc
dpkg: fout bij verwerken van pakket grub-pc (--configure):
 subproces van pakket grub-pc werd script post-installation geïnstalleerd gaf de foutwaarde 1 terug
Fouten gevonden tijdens verwerken van:
 grub-pc
root@easycomp:~# 

Equals wired stuffs;

root@easycomp:~# sudo DEBIAN_FRONTEND=text dpkg --configure -a
Instellen van grub-pc (2.02+dfsg1-20+deb10u3) ...
Bezig met configureren van grub-pc
----------------------------------

Het GRUB opstartprogramma was voorheen geïnstalleerd op een schijf die niet langer aanwezig is, of waarvan de unieke identificatie om een of andere reden is veranderd. Het is belangrijk om ervoor te zorgen dat het geïnstalleerde image van de GRUB-kern gesynchroniseerd 
blijft met GRUB modules en grub.cfg. Controleer of GRUB wel naar de juiste opstartapparaten wordt geschreven.

Indien u niet zeker weet welk station door het BIOS wordt gebruikt als opstartstation, is het vaak een goed idee om GRUB op alle stations te installeren.

Merk op dat het ook mogelijk is om GRUB naar opstartstructuren op partities te installeren. Enkele geschikte partities worden hier aangeboden. Dit wordt echter niet aangeraden omdat het GRUB dwingt om een bloklijstmechanisme te gebruiken waar het minder betrouwbaar van 
wordt.

  1. /dev/sda (966367 MB; VBOX_HARDDISK)  3. /dev/sda3 (773095 MB; LVM PV gHJy37-Jjo5-zGfJ-pF6r-edws-nzg4-9679gq on /dev/sda3)  5. /dev/dm-0 (965084 MB; system-root)
  2. - /dev/sda1 (254 MB; /boot)          4. /dev/sda5 (193015 MB; LVM PV 1nrBRc-jaqU-VRdC-VsAM-nLWV-g7cW-B3uvNV on /dev/sda5)  6. geen van bovenstaande

(Geef de waarden die u wilt selecteren, gescheiden door spaties.)

Apparaten waarop GRUB moet komen: 2


Installeren voor i386-pc-platform.
grub-install: waarschuwing: Bestandssysteem 'ext2' kent geen inbedding.
grub-install: waarschuwing: Inbedden is niet mogelijk.  GRUB kan in deze configuratie alleen worden geïnstalleerd met bloklijsten.  Bloklijsten zijn echter ONBETROUWBAAR en het gebruik ervan wordt ontraden..
Installatie is afgerond. Er werden geen fouten gerapporteerd.
Aanmaken van GRUB-configuratiebestand...
Linux-image gevonden: /boot/vmlinuz-4.19.0-14-amd64
Initiële RAM-schijf-image gevonden: /boot/initrd.img-4.19.0-14-amd64
Linux-image gevonden: /boot/vmlinuz-4.19.0-13-amd64
Initiële RAM-schijf-image gevonden: /boot/initrd.img-4.19.0-13-amd64
Linux-image gevonden: /boot/vmlinuz-4.19.0-12-amd64
Initiële RAM-schijf-image gevonden: /boot/initrd.img-4.19.0-12-amd64
voltooid
root@easycomp:~#

My fellow cat friend and Louis,

Not to be an jerk or something so please do not get me wrong. But couldn’t i do some kind of a complete reinstall of YunoHost BUT KEEPING all of the apps and their respective content. but not the config files for php and sql etc EXEPT WEBCONTENTS CONFIGS?

Also anytime if I try to do something i.e. uploading a file to my store easycomp(dot)shop; it crashes completely :cry:

root@easycomp:~# systemctl status

● easycomp.cloud
State: degraded
Jobs: 0 queued
Failed: 1 units
Since: Fri 2021-02-19 20:27:49 CET; 17h ago
CGroup: /
├─user.slice
│ └─user-0.slice
│ ├─session-59.scope
│ │ ├─ 8769 sshd: root@pts/0
│ │ ├─ 8776 -bash
│ │ ├─10716 systemctl status
│ │ └─10717 pager
│ └─user@0.service
│ └─init.scope
│ ├─8751 /lib/systemd/systemd --user
│ └─8752 (sd-pam)
├─init.scope
│ └─1 /sbin/init
└─system.slice
├─fail2ban.service
│ └─524 /usr/bin/python3 /usr/bin/fail2ban-server -xf start
├─haveged.service
│ └─414 /usr/sbin/haveged --Foreground --verbose=1 -w 1024
├─systemd-udevd.service
│ └─280 /lib/systemd/systemd-udevd
├─cron.service
│ └─1079 /usr/sbin/cron -f
├─nginx.service
│ ├─1139 nginx: master process /usr/sbin/nginx -g daemon on; master_process on;
│ ├─1140 nginx: worker process
│ ├─1141 nginx: worker process
│ ├─1143 nginx: worker process
│ └─1144 nginx: worker process
├─mariadb.service
│ └─637 /usr/sbin/mysqld
├─systemd-journald.service
│ └─234 /lib/systemd/systemd-journald
├─php7.3-fpm.service
│ ├─ 490 php-fpm: master process (/etc/php/7.3/fpm/php-fpm.conf)
│ ├─1160 php-fpm: pool phpmyadmin
│ ├─1162 php-fpm: pool phpmyadmin
│ ├─1163 php-fpm: pool roundcube
│ ├─1165 php-fpm: pool roundcube
│ ├─1166 php-fpm: pool wordpress__2
│ ├─1168 php-fpm: pool wordpress__2
│ ├─1169 php-fpm: pool wordpress__2
│ ├─1170 php-fpm: pool wordpress__2
│ ├─1171 php-fpm: pool wordpress__3
│ ├─1172 php-fpm: pool wordpress__3
│ ├─1173 php-fpm: pool wordpress__3
│ ├─1174 php-fpm: pool wordpress__3
│ ├─1175 php-fpm: pool www
│ └─1176 php-fpm: pool www
├─unattended-upgrades.service
│ └─522 /usr/bin/python3 /usr/share/unattended-upgrades/unattended-upgrade-shutdown --wait-for-signal
├─ssh.service
│ └─585 /usr/sbin/sshd -D
├─streama.service
│ └─516 /usr/bin/java -Djava.awt.headless=true -Dserver.port=8095 -jar streama.jar
├─nslcd.service
│ └─1072 /usr/sbin/nslcd
├─rsyslog.service
│ └─430 /usr/sbin/rsyslogd -n -iNONE
├─dnsmasq.service
│ └─641 /usr/sbin/dnsmasq -x /run/dnsmasq/dnsmasq.pid -u dnsmasq -7 /etc/dnsmasq.d,.dpkg-dist,.dpkg-old,.dpkg-new --local-service --trust-anchor=.,20326,8,2,e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
├─metronome.service
│ └─744 lua5.1 /usr/bin/metronome
├─slapd.service
│ └─1035 /usr/sbin/slapd -h ldap://127.0.0.1:389/ ldaps:/// ldapi:/// -g openldap -u openldap -F /etc/ldap/slapd.d
├─unscd.service
│ └─434 /usr/sbin/nscd -d
├─redis-server.service
│ └─586 /usr/bin/redis-server 127.0.0.1:6379
+++++++++++++++++