to boot the system reverses dev/sda and /dev/sdb

Everything worked fine, with 2 HD500GB in RAID1 (Adaptec) mounted on dev/sda (LVM) and 1T HD SATA mounted on dev/sdb1 /BACKUP.

This morning on reboot, I found the /BACKUP dir empty, after some research I found that the LVM (2 500GB HD in RAID1) was mounted on dev/sdb and the ext3 1T HD was mounted on dev/sda, the /BACKUP folder was mounted on sdb1, the right mounting point as set in etc/fstab but on the wrong HD.

Untill yesterday the storage shown BACKUP size 1T, today the size is 0,8 GB
---------------------------------------------------------------------------
This is my fstab file
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
UUID=7c111c94-3b79-448a-acf9-f05952626e58 /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
/dev/sdb1 /BACKUP ext3 defaults 0 1
------------------------------------------
Also strange is when I disconnected the 1TB HD I found the old backup in the /BACKUP dir
-----------------------------------------------------------------------
I did the following step also:
- disconnected the 1TB HD
- restart the system (now the dev/sda was on the right HD)
- connected the 1TB HD
- mount the /dev/sdb1 /BACKUP
and I found all my backups files, the storage show the right BACKUP size (but show it as empty under proxmox).
I restart the sytem, and the disk was reverses again.
any tips?

udo said:

Hi,
change in the bios the hdd-order - first the raid and as second your directly connected hdd.

Click to expand...

this is already configured as first the raid (adaptec) and as second the SATA hdd

You can also use the UUID to mount the /backup-Partition, or a Label (man fstab, and blkid to see all uuids). Then you mount allways the right partition.

Click to expand...

Do you means like this :
-------------------------------------------------------------------
# <file system> <mount point> <type> <options> <dump> <pass>
/dev/pve/root / ext3 errors=remount-ro 0 1
/dev/pve/data /var/lib/vz ext3 defaults 0 1
UUID=7c111c94-3b79-448a-acf9-f05952626e58 /boot ext3 defaults 0 1
/dev/pve/swap none swap sw 0 0
proc /proc proc defaults 0 0
# /dev/sdb1 /BACKUP ext3 defaults 0 0
UUID=95cd7e4a-eca0-479a-b7b3-2391474985db /BACKUP ext3 defaults 0 1
--------------------------------------------------------------------------------------

luc

Result:
The storage show:
------------------------------------------------------------------------

Nome Storage | Tipo | Abilitato | Attivo | Condiivso | Utilizzato (GB) |Capacità (GB)
local | Directory |Sì |Sì |No |4.42 | 354.84
BACKUP |Directory | Sì |Sì |Sì |0.20 | 870.32


------------------
Storage 'BACKUP'
Backups VZDump

Volume IDDimensione (GB) nessun dato

-------------------------------
Also it's not clear to me why:
1) the BACKUP device has only 850 GB, where are the other 130GB?
2) the local storage has only 350 GB, where are the other 146 GB?
-----------------------------------------------------------------
s1:~# fdisk -l
Disk /dev/sda: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xf119e3f4
Device Boot Start End Blocks Id System
/dev/sda1 1 121602 976759808 7 HPFS/NTFS
Disk /dev/sdb: 499.2 GB, 499279462400 bytes
255 heads, 63 sectors/track, 60700 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 66 524288 83 Linux
Partition 1 does not end on cylinder boundary.
/dev/sdb2 66 60700 487048430 8e Linux LVM
Disk /dev/dm-0: 4294 MB, 4294967296 bytes
255 heads, 63 sectors/track, 522 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-0 doesn't contain a valid partition table
Disk /dev/dm-1: 103.0 GB, 103079215104 bytes
255 heads, 63 sectors/track, 12532 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-1 doesn't contain a valid partition table
Disk /dev/dm-2: 387.0 GB, 387075538944 bytes
255 heads, 63 sectors/track, 47059 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000
Disk /dev/dm-2 doesn't contain a valid partition table
------------------------------------------------------
here the mount
/dev/pve/root on / type ext3 (rw,errors=remount-ro)
tmpfs on /lib/init/rw type tmpfs (rw,nosuid,mode=0755)
proc on /proc type proc (rw,noexec,nosuid,nodev)
sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
procbususb on /proc/bus/usb type usbfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,nosuid,nodev)
devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=620)
/dev/mapper/pve-data on /var/lib/vz type ext3 (rw)
/dev/sdb1 on /boot type ext3 (rw)
/dev/sda1 on /BACKUP type ext3 (rw)
------------------------------------------------------

However, I wonder how much important is for proxmox that the system is on dev/sdb and the backup is on dev/sda.
The system looks like is working.
What does the guru think about this question?

Ok for the disk space.

Now, about the main question, the device reverse, do you think is not a problem having the backup device on dev/sda1 and the system on dev/sdb, despite the booting priority is different?
About yoy, can I leave the thing as they are?