first install flawless, second and third boot into grub bash shell (EDIT: SOLVED, WTF, HOLY SHAMOLEY!)

Hey,

My mini pc came with the BIOS time set to a date in 2047, setting this to 2025 and reinstalling Proxmox appears to have worked for me and others
 
Hey,

My mini pc came with the BIOS time set to a date in 2047, setting this to 2025 and reinstalling Proxmox appears to have worked for me and others
Oh man
I will have to go check but I could swear I saw that date in the bios but didn't cross my mind it could cause a problem...
Thanks so much for the lifeline!!!!
If it turns out to be that, then geez, that needs to go into a sticky installation troubleshooting guide ..

Thanks buddy!
 
  • Like
Reactions: SteveITS
Oh my flipping good grief.
Took all of 2 seconds to change the date, reinstall the 17th time and 3rd type of install, after mucking with grub-repair, etc, etc, etc, etc, etc.

That was all it was the whole time...

So not really prox mox related to begin with, and apparently unrelated to the drive itself. I guess the 2nd and 3rd systems I got for some reason had the same 2047 year, and although I noticed it, I frankly assumed the installation would override it.

It would have never crossed my mind that a fresh install would fail because of the BIOS date.

Thank you so much amcwhae!!!

(and the others who tried to help as well).

Here's the sad irony. I've had these 2 boxes for so long, and tried to boot them so many times, in two different homes, that now I have them both ready but can't find one of their power supplies...

ARGH! Must be at the other location and I forgot it there...


But hey, I'm finally out of the crapper.

THANKS!!!
 
  • Like
Reactions: SteveITS
Actually I found a link that says linux may balk at booting if it sees a large difference between filesystem dates and the system date.
I just can't believe that it would do that silently (as far as I can tell), and fail so completely, and not realize that it's a brand new install so the system didn't have an NTP link or anything like that yet.
I went through the journal logs looking for any sort of error but never saw anything except complaints about no bootable filesystem.
If it said 'because the dates look funny compared to the BIOS date', I didn't see it...

I can't believe I spent all this time on this but gosh bless the guy with the answer...
Here's the link I found that explains it a little (I only found it after the previous poster gave me the solution..)


https://access.redhat.com/solutions/57977#:~:text=Issue,timestamp is in the future".

1750644320810.png