Recent Upgrade Failed

Take a look at my post here.

My prior boot drive was an Intel 80GB SSD. Earlier today I attempted the 81 package upgrade. See attachments for the error messages -- in particular "OMV-Large-81-pkg-update-error-INTEL-SSD-01.png". ( I also added likely superfluous info, but you never know if it might help. )

1st Question: The replacement boot drive was a 'rescuezilla' copy of the Intel SSD. Why would the old Intel drive still be referenced ? Of course, the new boot drive is a clone of the old one, so DUH! ... But I would not expect such a DEPENDENCY.

2nd Question: How to fix this relatively painless ?

I have not yet rebooted ... almost afraid to ... let me know what other info you would like to see.

TIA for any advice.

Cheers.

Quote from C-3PO

Hello.

I am only a beginner on the forum and I will try to help you my best.

Please wait for other members to confirm before you do anything.

The problem with SSDs is that it can fail almost completely in the worst scenario and no data can be recovered.

But if you achieved a rescuezilla copy, your SSD disc is probably still working.
I hope that you have a backup.

Apparently you had a problem during grub-pc upgrade, which is the package that manages the /boot partition and grub file.

If your boot and grub files are damaged, it is normal that you cannot boot.

What you call "boot drive" is the main system where OMV resides?

I don't understand what you call a dependency, please be more precise.

Step 1: make sure to repair your main partition if is has bad sectors

As OMV is a Debian system, you may boot on a Debian installer and choose "rescue" mode.

Then follow the process but don't mount your partitions (it is very important not to mount your partitions in rescue mode).
If your partitions are mounted and you try to repair them, it can result in data lost, so be very cautious.

When you issue a command stay "in the context of the installer" and don't mount partitions.

At first, list your partitions and identity your /root partition:

Code

lsblk # or fdisk -l

Then check your main root partition without modification:

Code

sudo fsck -n /dev/sdXN

It should tell you wether your main partition is safe.

If your disc has errors, you may repair them automatically:

Code

sudo fsck -y /dev/sdXN

Step 2: finish Debian upgrade and fix grub-pc

Then it should be safe to reboot in rescue mode and mount the partitions (choose to automount them, this is safe).

As your system was dammaged during an apt upgrade, you should finish the upgrade.

Issue those command lines:

Code

apt update
apt upgrade

Debian will try to finish the upgrade and it cannot finish, it will give you a command to fix your system.

Normally it should attempt a new grub upgrade.

If everything was successful, reboot.

I will only be able to help in 24 hours, please wait for other advice.

Kind regards,

Display More

Thanks for your response. And yes, I will wait for confirmation from others.

A bit more info. The Intel Boot Drive -- yes, by Boot Drive I mean where OMV was installed originally -- did not have any errors or issues. The reason I cloned it (using rescuezilla) was to move the boot drive to an IDE drive. So, after cloning the contents of the Intel SSD to the IDE drive, I removed the Intel SSD and started booting off the IDE drive -- which by-the-way is also an SSD !

Everything has worked as expected, booting off the cloned boot drive. I did not notice anything unusual for the week or so I was using the new IDE boot drive, until the BIG UPGRADE.

What I mean by DEPENDENCY is this ... it appears that by cloning the original INTEL boot drive the reference to the Intel drive is still stored with grub. ( I don't really understand 'grub' ... ) To me that is a DEPENDENCY, because if I had been FORCED to replace a failed boot drive by recovering a backup to a new drive -- everything I did voluntarily for different reasons -- the UPGRADE would still fail because grub appears to still "need" the failed drive to complete the upgrade.

Obviously ... either

a) such dependency should not be created in the first place, and/or

b) a fix, whether manual or automatic, must exist to fix the grub reference on the cloned drive.

Hope this helps. Waiting for an answer from a Moderator, while listening to music playing from my "sick" OMV.

Cheers.

Ok. I solved the problem by myself. A few hours of google-research on 'grub' with cloned drives led me to a simple solution.

I had tried to reboot ... but the boot process stalled and I could not boot into the upgraded OMV after the error I had encountered. So I used 'rescuezilla' to recover the latest backup image of the new IDE Boot Drive made before the big 81 pkg upgrade. I then went back to the save screenshot with the error message received during the attempted upgrade. (See attachment "OMV-First-Attempt-Error.png")

Now for the solution. After doing a CLONING of the BOOT DRIVE ... for some reason the system remembers the OLD Boot Drive's IDs. After my research I nailed it down to where they need to be. (See attachment "OMV-Clone-Problem-01.png")

Once 4 links were created I re-processed the 81 pkg update. It proceeded without a hitch. (See attachment "OMV-New-Attempt---Success.png").

I hope this helps someone

Cheers.

Quote from C-3PO

Good to know. Debian installer in recovery mode is also very smart in recovering the boot.

I am not sure if using the Debian Installer in recovery mode would have worked, but I might be wrong since my experience with grub is close to nil.

The original Boot Drive (Intel 80GB SSD) was no longer connected, but OMV still had its ID hidden somewhere. Which is why I called it a "DEPENDENCY", and which is why the UPDATE FAILED because it attempted to use the ID of a non-existent drive. Knowing the original ID from the error message I had screenshotted allowed me to fool OMV to complete the UPDATE without the need to try the Debian recovery mode.

Cheers.

Quote from macom

The error message in the first picture is telling you what to do in order to install grub to the correct drive.

Just below your red box.

Ok, thanks everyone ! Including C-3PO

I am learning

Cheers