System was running alright. Beautiful thing. Then I shut it down to install a new system disk, turned it back on and…got this “kernel panic - fails to boot “error: out of memory” and unable to mount root fs” message.
Searched and found this thread here…
Since I have an i5 processor with video on it that I´m using, tried install another video card because of what I read in that thread but didn´t solve the problem. Don’t know how to do the proposed file system modifications since I can´t access the system files if the system does not load…can I?
Anyways, as I thought it was some corruption in the boot files I reinstalled the system in the same drive it was…nothing good happened. Then installed the system in the new drive, boot from it and…problem solved! I could boot and import my pools. Used the old system drive to make a new apps-VM pool. Imported the configuration file I had saved, uploaded it…and it spent the next 30 minutes with a screen message saying that it was communicating with the NAS to upload the system file…I finally gave up on it, shutdown the machine and when rebooted…back to the original kernel panic problem…
No idea of what to do here…guess I could erase the new system disk and reinstall again but that´s not really a solution…it will probably happen again when I shutdown the system again…
Don´t think so…that happened with the former system disk (an 512 nvme), then I replaced it with an 256 Sata ssd, it worked and when I shutdown the system and then turned it on again, the same happened. And the old one I used to make a new pool, so I know it´s working…
BTW: Should I disable fast boot in BIOS?
Ok…so what I did was to pull the stem drive out of the machine again, format it in a Linux machine , put it back to the server, reinstall the system and it boots alright again. Imported my pools, it´s working. Still have to reconfigure the thunderbolt local connection but only after I figure out what´s going on. I’m sure that if I shut the system down again I’ll be in the mud once more…
I´m posting below the scree I get stuck on the boot when it happens in the hope it makes sense to someone…my linux skills are quite small …
Well, so anybody who goes into the same sh** know how to solve it…
I followed this ideas:
Many of the file modifications couldn´t be made for permission and read-only mount points and things like that…chat gpt taught me how to solve this things (that´s becoming freaking good…)
Also increased the amount o memory available to my CPU graphics from 64mb and 128mb in BIOS, as someone suggested that could be the issue.
One of this things apparently solved the problem. Booting normally now
WAs also getting this message in POST, but that vanished after all that…
dev/root: can’t open blockdev
VFS: cannot open root device “ZFS=boot-pool/ROOT/24.04.02”
Please append a correct “root=“ boot option
