The fact that it's fully rebooting kind of makes me suspect some sort of hardware problem though? I would think that even a kernel crash would leave me staring at a screenful of crash output rather than fully rebooting the box. The problem is that it bombs out and restarts, so unless I hold a phone and video the screen, I may not be able to note what it says when it's dying.
Help?Ĭlick to expand.I did actually try it in debug mode, but I didn't realize it was printing more info to another tty so I didn't think to swap over there and try to catch it. If anybody has any thoughts on why 6.3 is crashing in the middle of the install, or what I can do to help track down the root cause, I would be very grateful (and would be happy to provide debug information if it will help improve the product / fix the problem). I saw that PVE 6.4 was just released, so I'm going to build a USB stick for that and see if everything Just Works there. Something is going wrong related to either ZFS, or the secondary (cabled) SATA disk (which was known-functional and working fine in an external USB enclosure previously). I then went back and installed from the same stick, to the mSATA SSD in EXT4, and that installation completes without any problem (although I did not actually attempt to boot the result). I've repeated this multiple times and it always dies in the middle with a system reset. The installation does not complete, it seems to die around 50-60% through. and then the screen goes black and I'm staring at the UEFI/POST screen again. I'm able to proceed through the installation, and it appears to create the zpool correctly, and even begins copying & extracting packages onto the zpool. I am configuring the zpool to only be 200GB, so even though the drives are slightly mismatched in size, I'm not trying to fill them.Įverything else in the ZFS config is at default (other than setting the max size to 200GB). When installing, I have the CSM entirely disabled in the BIOS, so it is booting from the install USB in UEFI mode. The system has 2x 8GB DDR4 modules installed, and they are testing OK using the built-in memory test utility.
The mSATA is a Kingston SSD, nominal "240GB," and the cabled drive is a Samsung 840 Pro "256GB". I have a Protectli "FW6D" unit (core i5 8250U, passively cooled with a massive heatsink case) that has two internal SSDs - one mSATA (it's not M.2, it's an actual mSATA module), and the other standard cabled SATA device. Proxmox gurus - subject says most of the problem.
0 kommentar(er)
