EXT4-fs error (device dm-1):

[lubbe5]

Hello,


I'm really at a loss. Since yesterday, my Proxmox server has crashed, and after a reboot the server is no longer reachable.
I can no longer log in through the console either. The only way I can access a console is by booting from the USB stick (that contains the Proxmox installation files.)


Please see the error message below.


Can anyone help me? The files stored on the server are very important to me, and I'm worried about losing them.


Thank you in advance for any assistance.

----------------------------
Welcome to the Proxmox Virtual Environment. Please use your web browser to
configure this server - connect to:

https://192.168.1.xxx:8006/

Proxmox-Server login:

[ 18.419043] EXT4-fs error (device dm-1):
ext4_journal_check_start:87: comm systemd-journal:
Detected aborted journal

[ 18.419115] EXT4-fs (dm-1):
Remounting filesystem read-only

 

[Impact]

Check these

journalctl -kr
ls -l /dev/mapper/
lsblk -o+FSTYLE,LABEL,MODEL

If you care about your data back it up.

 

[Domino]

@Impact, is on the money, if you need it, back it up.

When you say files, do you mean your guests?

What you can do is attach an external storage device, mount it, and then do a

cp -r /etc/pve <your mounted storage device>

(for example)

cp -r /etc/pve /mnt/external_storage

Then you need something like clonezilla, bootable usb, and clone the corrupt physical drive.

Once you have that drive cloned and the pve folder all backed up.

From that point on you then need to just try any number of routes that will result in getting back to a running system, first off a new drive is needed, keep the clone safe until you are happy that you got everything up and running.

 

[lubbe5]

Thanks for the help everybody,

I was installing a truenas at the proxmox, but too late with the backup

 

[Domino]

I was installing a truenas at the proxmox, but too late with the backup

It's never too late unless the drive is totally dead. Clone the drive the first chance you get, do NOT disable RO mode, it does that to protect the data, at this point you have no idea what could have caused the ext4 journalling issue, hence cloning it at this stage is paramount, so that you have a point you can keep going back to until you recover.

I've recovered from far worse situations, the main rule is to get a clone before you do anything else!