So i build myself a brand new VM with SMG 10.9.1-3 and running it next to my old not updateable SMG.
I created a backup on my old SMG and try to restore it on my new SMG. This is not working. And im getting errors.
Apr 10 2025 15:55:10 [https-jsse-nio-443-exec-1] [RestoreAction] ERROR - Cannot restore the database from the file. bad decrypt
408C1CD6ED7F0000:error:1C800064:Provider routines:ossl_cipher_unpadblock:bad decrypt:providers/implementations/ciphers/ciphercommon_block.c:124:
Failed to run: '/opt/Symantec/Brightmail/common/sbin/cryptde /data/tmp/backup_tar.signature /data/tmp/backup_tar.plain': ERROR: Backup signature verification failed.
2025-04-10 14:55:11 3 [Warning] Access denied for user 'root'@'localhost'
2025-04-10 14:55:11 4 [Warning] Access denied for user 'root'@'localhost'
2025-04-10 14:55:11 5 [Warning] Access denied for user 'root'@'localhost'
2025-04-10 14:55:12 6 [Warning] Access denied for user 'root'@'localhost'
How do i proceed from here?
Or do i need an older VM? Where can i get the older version?
Original Message:
Sent: Apr 04, 2025 02:17 AM
From: Bernd42
Subject: I can't update to SMG 10.9.1-3 version problem
Hello James,
I can fully understand now that it is not possible to expand the boot filesystem as ther is no root account. And it makes perfect sense, given the fact, that SMG is a security appliance. And it's also good to read, that we will not run into a similiar issue ever again. So far so good. So for me, everything is fine now.
However, let me point out a few things. First, the communication about the issue was not good. Yes, there was a small information in the release notes. But not very clear. And even in the KB article it was only said, one may run into an issue if one had initially installed prior to version 10.7. But no hint about how to check if that is the case. I can not say with which version every single one of my over hundred devices was originally installed. Can you? And also no clear info about how much space is needed on the boot filesystem and how one can check the size of the boot filesystem.
In future, please make those things clear in the release notes. And please provide information how one can if one is affected by a issue. We would have needed a way to check this. And if it wasn't possible to add this to the web gui, there was a way to check on command line. All it would have taken to reduce the pain was a few sentences in the release notes on how to check the sitze of the root filesystem via cli and that everything is good if the size shown there was equal or greater than 500 MB (or whatever).
That said, SMG is a great product. The process with backup, reinstall, restore and then finally upgrade is not as painful as it seems at first. Maybe after so many years it was a good thing to do a clean install.
Regards,
Bernd
Original Message:
Sent: Mar 28, 2025 12:44 PM
From: James Martini
Subject: I can't update to SMG 10.9.1-3 version problem
Hello Bernd,
The reason that the filesystem can't be restructured on the fly as part of the upgrade is relatively complex but essentially comes down to the positioning of the filesystems on disk and the fact that you cannot move the root filesystem when the system is running.
In SMG, the boot filesystem is at the front of the disk volume and abuts the root filesystem. To expand the boot filesystem, the root filesystem would need to be moved while the system was running (and using it). There are clever ways around this but doing them in an automated manner as part of the upgrade would present a greater risk of system failure which would, itself, require a reinstall of the OS.
Unfortunately, it wasn't known when SMG 10.9.0 was built that the 10.9.1 kernel files might exhaust available space on the boot filesystem so no mechanism was build into 10.9.0 to check for this prior to upgrade.
Rest assured, however, that the boot filesystem laid down by the the 10.9.0 install is spaciuos enough for the forseeable future. And by "forseeable future" I mean that we're all likely to be roaming the desert wastelands in home build hot rods searching for water, gasoline, and bullets before SMG runs into this issue again.
Original Message:
Sent: Mar 28, 2025 03:27 AM
From: Bernd Struve
Subject: I can't update to SMG 10.9.1-3 version problem
Hi James,
exactly, and that's what worked for me. So +1 for the way Sanni did it. And by the way thanks to the broadcom support employee who helped me with this.
However, I don't understand one thing: Why can't SMG change the filesystem layout on an existing virtual machine? As far as I know, there is one volume having a size of approx. 450 MB (in my case) and this volume needed to be something around 550 MB in size. My virtual hard disk has 200 GB and seems to be mostly empty.
I assume the underlying operation system is generally capable of growing a volume. So why are we forced to do a clean install and have to take all the trouble with backup, restore and all?
Regards,
Bernd
Original Message:
Sent: Mar 21, 2025 10:28 AM
From: James Martini
Subject: I can't update to SMG 10.9.1-3 version problem
Thank you Sanni,
That is the recommended resolution to the upgrade issues as laid out in the "Kernel Panic - not syncing: VFS: Unable to mount root fs... " after upgrade of Messaging Gateway KB although the KB is slightly more abbreviated. The key step is the install of a clean VM using the 10.9.0 ISO as this creates a new SMG VM with a different filesystem layout that can accomodate the 10.9.1 boot files and kernel.
Quite a few of the SMG virtual machines that experience the upgrade issues were originally installed seven to ten years ago (or longer) and while their memory and cpu resources may have been upgraded, the underlying hard disk layout remains unchanged.
Essentually, the disk partitioning of SMG systems installed in 10.7.0 (released in 2011) is incompatible with 10.9.1 released 14 years later.
Regards,
James Martini
Original Message:
Sent: Mar 21, 2025 03:23 AM
From: Sanni Abrim
Subject: I can't update to SMG 10.9.1-3 version problem
This is how it worked for me:
- Download ISO 10.9.0
- Fresh install VM with ISO (important)
- Setup netowrk IP, hostname and License etc (this will not change after the restore)
- Full Backup your old 10.9.0 machine
- Restore old Backup to your new machine and wait
- Then reboot
- Then setup you network, hostname etc
- Then snapshot your new VM and start the upgrade
- That should hopefully work for you too
Original Message:
Sent: Mar 19, 2025 08:47 AM
From: sekreber1966
Subject: I can't update to SMG 10.9.1-3 version problem
I agree. Please share what steps you took to fix this issue
Original Message:
Sent: Mar 19, 2025 08:29 AM
From: alexander sanita
Subject: I can't update to SMG 10.9.1-3 version problem
Unclassified | Non classifi?
Wow. Nice. Send how u did that.
Original Message:
Sent: 3/19/2025 8:28:00 AM
From: Ozer ILERI
Subject: RE: I can't update to SMG 10.9.1-3 version problem
Hello ,
I fixed the problem with a zero installation and backup restore,
the related case is closed for me.
Original Message:
Sent: Feb 27, 2025 02:28 AM
From: Ozer ILERI
Subject: I can't update to SMG 10.9.1-3 version problem
Hello,
I have been trying to upgrade to the new version for a few days but no matter what I did, except for a clean install, I could not upgrade directly,
1st Attempt: I am trying to upgrade my current version 10.9.0-3 directly to 10.9.1-3, the error I get is as follows, I have all kinds of compatibility with Disk, CPU, OS.
2nd Attempt: I am trying to restore my current version 10.9.0-3 image by installing it from scratch and backing up the current device, the error I get is as follows, what exactly should I do, I cannot send a case because there is a problem with the support portal,
[https-jsse-nio-443-exec-7] [RestoreAction] ERROR - Backup image is incompatible with target system. Host type must match.
I kindly request your support