Error with un-mounting disk

[wolframio]

Hello, when I installed proxmox, I mounted the disk that I use for backups from the command line and not from the web interface.

Tt works without problems except that when I turn off my server the error seen in the image appears, any advice?

Thank you

 

[gfngfn256]

Have you checked contents of /etc/fstab ?

 

[wolframio]

Have you checked contents of /etc/fstab ?

root@R420:~# cat /etc/fstab
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext4 errors=remount-ro 0 1
UUID=2249-1844 /boot/efi vfat defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0


UUID=1d48a16d-45db-40d9-9ec3-e91bbd67bb30 /mnt/DATA ext4 defaults 0 2

 

[gfngfn256]

if I understand you correctly the above drive used for backups is no longer attached to the server.
Is the last entry in your fstab the said drive:

UUID=1d48a16d-45db-40d9-9ec3-e91bbd67bb30 /mnt/DATA ext4 defaults 0 2

Check the UUID for this drive. If it is this no longer attached drive, then comment out this line. Reboot server.

 

[wolframio]

/dev/sda1 is mounted by that line, and is attached to the server.

root@R420:~# blkid
/dev/mapper/pve-root: UUID="95e7dde4-45ef-429f-bd37-03fd24399be1" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdb1: UUID="fdba3777-f2b0-4f76-866f-bc37ba31bf0e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="6102a45a-125f-44cf-8185-3d8c362000ba"
/dev/mapper/pve-swap: UUID="bc5c61cc-6ef7-4ce1-8855-89f08de77e16" TYPE="swap"
/dev/sdc2: UUID="2249-1844" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="34eb9ff5-1790-4ea0-b975-2b99aa1db865"
/dev/sdc3: UUID="ECvXMN-X77Q-EvA2-5c60-eYp8-3PYe-AqhJiq" TYPE="LVM2_member" PARTUUID="ec25780f-48f0-49db-9142-d8640f175d89"
/dev/sda1: UUID="1d48a16d-45db-40d9-9ec3-e91bbd67bb30" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="472452a2-3db1-40d6-9979-f15ddd63a9c1"

 

[gfngfn256]

What does this show:

cat /etc/pve/storage.cfg

 

[wolframio]

What does this show:

cat /etc/pve/storage.cfg

root@R420:~# cat /etc/pve/storage.cfg

dir: local
path /var/lib/vz
content iso,vztmpl,backup

lvmthin: local-lvm
thinpool data
vgname pve
content rootdir,images

dir: DATA
path /mnt/DATA
content snippets,rootdir,images,backup
prune-backups keep-all=1
shared 0

dir: BACK
path /mnt/pve/BACK
content images,backup,snippets,rootdir
is_mountpoint 1
nodes R420
shared 0

root@R420:~#

 

[gfngfn256]

dir: DATA
path /mnt/DATA
content snippets,rootdir,images,backup
prune-backups keep-all=1
shared 0

dir: BACK
path /mnt/pve/BACK
content images,backup,snippets,rootdir
is_mountpoint 1
nodes R420
shared 0

Are these still available/connected?

 

[wolframio]

Are these still available/connected?

Yes

 

[gfngfn256]

If I understand your situation correctly:

In the past, you attached a USB drive which you mounted from the CLI to an unused mountpoint. But not permanently in fstab.
You then copied over your backups to the correct directories, using the CLI.
You then unmounted the above drive from the CLI & removed the drive.

The above would be the correct procedure & shouldn't cause any errors, I've done it myself in the past many times.

 

[wolframio]

If I understand your situation correctly:

In the past, you attached a USB drive which you mounted from the CLI to an unused mountpoint. But not permanently in fstab.
You then copied over your backups to the correct directories, using the CLI.
You then unmounted the above drive from the CLI & removed the drive.

The above would be the correct procedure & shouldn't cause any errors, I've done it myself in the past many times.

1.- Install Proxmox on a drive (that is, Proxmox is on its own drive).

2.- Mount the "DATA" drive (which is on drive "A") via CLI/SHELL in the empty "/mnt/DATA" directory, then add the line in "fstab" so that it mounts itself upon reboot.

3.- Mount the "BACK" drive (which is on drive "B") via "Proxmox Web Panel", by doing so I think I also wiped it.

4.- I started restoring my "Backups" from a "PBS" server.


That's how it went...


Thanks!

 

[gfngfn256]

If I now understand your situation;

1. All drives are connected, mounted & are configured correctly in PVE storage.

2. Your system works as expected.

3. Your PVE system shuts down when requested.

4. Your PVE system starts up correctly when booted.

I think you can ignore that message in the OP. (It may be caused by a specific controller in your HW, or something specific to your HW/PVE setup. I don't know anything about your HW/PVE setup except your storage.cfg).