I literally just installed Proxmox 9 on a brand new server (Asus RS300-E12-RS4). The specs are: Intel Xeon E-2478, 32 GB DDR5 at 4400, a single Micron 7450 NVME 800gb, 2 redundant power supplies. On Proxmox i'm trying to upload my Windows Server 2019 ISO to use (old I know, it's for work.) I've never used Proxmox so I'm not familiar with what to do.
Weird Error on Fresh Install
- Thread starter internetnick
- Start date
Welcome, and nice system for testing!
To gauge how to provide further support, have you used Linux before?
This error (
To prevent data corruption, the EXT4 filesystem automatically switched itself to Read-only mode because it couldn't write to its journal (the log file).
Even though you're using a single Micron 7450 NVMe, the error points to
Here are a few things you can check to narrow it down:
EXT4-fs error ... detected aborted journal) usually isn't a Proxmox bug. It basically means your underlying I/O hit a wall. To prevent data corruption, the EXT4 filesystem automatically switched itself to Read-only mode because it couldn't write to its journal (the log file).
Even though you're using a single Micron 7450 NVMe, the error points to
dm-1. This means there’s a Device Mapper layer (likely the default LVM volume like pve-root) between the drive and the filesystem. The error is bubbling up from the physical NVMe, through LVM, and finally crashing the EXT4 layer.Here are a few things you can check to narrow it down:
- Check the logs first: Run
dmesg | grep -i nvmeorjournalctl -xe. Look for keywords like "Timeout," "Reset," or "I/O error." If you see these, the hardware or driver is definitely acting up. - Check SSD health and firmware: Run
smartctl -a /dev/nvmeXto see if the drive is failing. Also, the Micron 7450 has had some known stability issues with certain firmware versions on Linux—it's highly recommended to check for updates. - Physical connection: If this is a physical server, double-check if the NVMe is seated correctly or if there's any dust in the slot.