SOLVED: Upgrading from 2.2 RC
-
You see the same error booting the 2.6 USB image from a local USB drive?
What devices are shown when you enter
?
at the mountroot> prompt? -
@stephenw10 I didn't take any images of that since I could see the devices when using the question mark. A couple of them show pfsense images which makes sense since I had both a usb stick and cdrom mounted.
Using ufs/dev/xxx only lead to error 19 even if I was trying to use the correct device.
I think this thread is done. I'll try to share more if I get anything but at this point, there are people at the server working on it since I cannot do it from remote. I don't yet know if they will accomplish it but if they do, I'll ask for as much info as I can get. If they can't, the plan is to move to a newer server.
-
Ok. It will certainly be easier to accomplish locally.
Let us know what happens.
-
I mentioned that the ISO install loading was virtual media and not physical. The usb stick was physical but it didn't work either.
I asked if someone could cut a cdrom but no one could.However, this morning, someone was able to get to the physical server.
2.6.0 finally got installed using a physical cdrom.The person told me the following things.
Using the "virtual"ISO is what was causing issues with how BSD handled its bootup. It apparently was not able to detect the virtual iso it so it failed to load itself causing the error 19.
For the USB drives, he did not look into it much but guesses its more BSD quirks about how the image was burned to the usb drive.
For this install, he loaded the ISO into the IPMI console.
For the exact reason in how it differed on the backside and why the other method worked, he is not able to say other than it appears to act more as a "real" cdrom instead of virtual ISO so installer was able to find and load it's needed files. BSD does not seem to work well with this particular servers 'virtual' methods.
So that's that. Another lesson from another unusual (to me) problem. Hope this thread can help someone and also hope no drama will be added to a now completed thread so that it might help someone that finds it.
-
@lewis said in Upgrading from 2.2 RC:
Hope this thread can help someone and also hope no drama will be added........
Balena Etcher & Memstick serial iso download and pushing to the USB stick ca. 10 minutes
Fresh install then on an APU6B4 ca. 10 minutes more with
config backup playback all in all is done in ca. 30 minutes!So I really don´t know what drama you are talking about.
-
@dobby_ said in Upgrading from 2.2 RC:
@lewis said in Upgrading from 2.2 RC:
Hope this thread can help someone and also hope no drama will be added........
Balena Etcher & Memstick serial iso download and pushing to the USB stick ca. 10 minutes
Fresh install then on an APU6B4 ca. 10 minutes more with
config backup playback all in all is done in ca. 30 minutes!So I really don´t know what drama you are talking about.
Really no idea what so ever why you bothered to post that. As I said, in most cases I've never had problems but in this case, I was remote and virtual media didn't work. That's the end result of the experience.
Done, finished, not much else to go on about :)
-
Ah, so to be clear the initial attempt there were not using the Supermicro IPMI?
-
@stephenw10 said in Upgrading from 2.2 RC:
Ah, so to be clear the initial attempt there were not using the Supermicro IPMI?
Correct. Sorry I didn't clarify that.
I wanted to (a couple times) but was pretty caught up in the effort and forgot to. -
No worries, thanks for clarifying. We have seen issues using the virtual optical drive in IPMI.
Steve
-
For anyone that comes across this, to sum up, using a Spider KVM and attaching virtual media to that is what was not working, at least not with BSD.
Using the servers IPMI virtual functions worked.