Drive "disappears" from my set-up

[dasc]

Hi there;

I'm discovering Proxmox and I'm stacked with one problem that I would like to have your support .I'm running version 7.3.6 with 2 SSD an1 4TB HD sata connection ,1- 128G USB pen drive and 1 external 4TB HD connected with a USB>SATA adaptor.
This setup was running for some months but suddenly the USB HD disappears from the list of disks but the mount point it was still available on datacenterand I try a restore from one backup and it worked .I tried the drive on a another machine and effectively the mount point and the files were there. By other side I was obliged to remove the missing drive from fstab because if not the server starts only in emergency mode .
Does anybody has an idea about what it's happening?

Regards


root@pve:~# df -h
Filesystem Size Used Avail Use% Mounted on
udev 12G 0 12G 0% /dev
tmpfs 2.4G 1.2M 2.4G 1% /run
/dev/mapper/pve-root 461G 359G 82G 82% /
tmpfs 12G 46M 12G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/sda 880G 123G 712G 15% /mnt/data/backup
/dev/sde 113G 65G 42G 61% /mnt/sandusb
/dev/sdc2 511M 336K 511M 1% /boot/efi
/dev/sdb1 3.6T 1.8T 1.7T 53% /mnt/BackupHD
/dev/fuse 128M 20K 128M 1% /etc/pve
tmpfs 2.4G 0 2.4G 0% /run/user/0


root@pve:~# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
loop0 7:0 0 8G 0 loop
sda 8:0 0 894.3G 0 disk /mnt/data/backup
sdb 8:16 0 3.6T 0 disk
└─sdb1 8:17 0 3.6T 0 part /mnt/BackupHD
sdc 8:32 0 476.9G 0 disk
├─sdc1 8:33 0 1007K 0 part
├─sdc2 8:34 0 512M 0 part /boot/efi
└─sdc3 8:35 0 476.4G 0 part
├─pve-swap 253:0 0 8G 0 lvm [SWAP]
└─pve-root 253:1 0 468.4G 0 lvm /
sde 8:64 1 114.6G 0 disk /mnt/sandusb


root@pve:~# blkid
/dev/sda: LABEL="storageprox" UUID="cce8b453-556d-4480-a8bb-e72616354157" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdb1: UUID="30f826be-392c-4a7e-9ad0-eebf71a06e0e" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="72e5345c-d5bc-489a-8faa-c22d9bd3a06b"
/dev/sdc2: UUID="2766-C6CC" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="ad3e2635-cfb8-4f94-abbb-9ad611225ede"
/dev/sdc3: UUID="anfGMA-WuBZ-Mqw5-Ue9U-VeRp-dSoz-BBMcMy" TYPE="LVM2_member" PARTUUID="e26d12da-90a3-461a-bb35-01db527a6f19"
/dev/mapper/pve-swap: UUID="2461ce5f-e918-4b0d-bb46-7d2100d15540" TYPE="swap"
/dev/mapper/pve-root: UUID="42991e2f-39f3-4446-ac62-81dea9b8d8a4" BLOCK_SIZE="4096" TYPE="ext4"
/dev/loop0: UUID="dc7a6820-5e11-4848-b21c-16c2a67e450f" BLOCK_SIZE="4096" TYPE="ext4"
/dev/sdc1: PARTUUID="8c87f6dc-b4b3-4177-8477-f1652f7ebddb"
/dev/sde: UUID="25d505cf-f117-4a84-9bd2-5e93844eebe9" BLOCK_SIZE="4096" TYPE="ext4"

 

[Dunuin]

You don't like partitions? Because sda and sde aren't partitioned according to blkid and lsblk.

 

[dasc]

You don't like partitions? Because sda and sde aren't partitioned according to blkid and lsblk.

Ok thanks for your reply .What will be the correction that you purpose to a newbie?

 

[fiona]

Hi,

I tried the drive on a another machine and effectively the mount point and the files were there. By other side I was obliged to remove the missing drive from fstab because if not the server starts only in emergency mode .
Does anybody has an idea about what it's happening?

if the drive was not connected anymore to the system, this is expected. If not everything that's expected to be there can be mounted, it is considered a failure, hence the emergency mode. If the drive was connected, I'd recommend checking /var/log/syslog for messages related to the drive.

You don't like partitions? Because sda and sde aren't partitioned according to blkid and lsblk.

Why would you partition a disk if you intend to use the whole one for a single file system?

 

[dasc]

Hi,

if the drive was not connected anymore to the system, this is expected. If not everything that's expected to be there can be mounted, it is considered a failure, hence the emergency mode. If the drive was connected, I'd recommend checking /var/log/syslog for messages related to the drive.


Why would you partition a disk if you intend to use the whole one for a single file system?

Thank you so much for your reply.

Attached /var/log/syslog extract when I reconnect the faulty HD .Can you please be so kind and help me understand the result .[ICODE][/ICODE]
Mar 10 09:47:35 pve kernel: [48876.605542] usb 2-10: new SuperSpeed USB device number 3 using xhci_hcd
Mar 10 09:47:35 pve kernel: [48876.626473] usb 2-10: New USB device found, idVendor=152d, idProduct=0561, bcdDevice= 1>
Mar 10 09:47:35 pve kernel: [48876.626477] usb 2-10: New USB device strings: Mfr=1, Product=2, SerialNumber=5
Mar 10 09:47:35 pve kernel: [48876.626479] usb 2-10: Product: USB 3.0 Device
Mar 10 09:47:35 pve kernel: [48876.626480] usb 2-10: Manufacturer: USB 3.0 Device
Mar 10 09:47:35 pve kernel: [48876.626481] usb 2-10: SerialNumber: 000000004C83
Mar 10 09:47:35 pve kernel: [48876.632777] scsi host5: uas
Mar 10 09:47:35 pve kernel: [48876.633329] scsi 5:0:0:0: Direct-Access 0105 PQ: 0 ANSI: 6
Mar 10 09:47:35 pve kernel: [48876.634505] sd 5:0:0:0: Attached scsi generic sg3 type 0
Mar 10 09:47:35 pve kernel: [48876.635424] sd 5:0:0:0: [sdd] 7814037168 512-byte logical blocks: (4.00 TB/3.64 TiB)
Mar 10 09:47:35 pve kernel: [48876.635630] sd 5:0:0:0: [sdd] Write Protect is off
Mar 10 09:47:35 pve kernel: [48876.635632] sd 5:0:0:0: [sdd] Mode Sense: 67 00 10 08
Mar 10 09:47:35 pve kernel: [48876.636027] sd 5:0:0:0: [sdd] Write cache: enabled, read cache: enabled, supports DPO a>
Mar 10 09:47:35 pve kernel: [48876.636399] sd 5:0:0:0: [sdd] Optimal transfer size 33553920 bytes
Mar 10 09:47:35 pve kernel: [48876.711697] sdd: sdd1
Mar 10 09:47:35 pve kernel: [48876.746786] sd 5:0:0:0: [sdd] Attached SCSI disk
Mar 10 09:47:35 pve udisksd[830]: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdd': Unexp>
Mar 10 09:47:36 pve kernel: [48878.293512] sd 5:0:0:0: [sdd] Synchronizing SCSI cache
Mar 10 09:47:37 pve kernel: [48878.569582] sd 5:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR >
Mar 10 09:47:37 pve kernel: [48878.865809] usb 2-10: reset SuperSpeed USB device number 3 using xhci_hcd

 

[fiona]

Mar 10 09:47:35 pve udisksd[830]: Error probing device: Error sending ATA command IDENTIFY DEVICE to '/dev/sdd': Unexp>
Mar 10 09:47:36 pve kernel: [48878.293512] sd 5:0:0:0: [sdd] Synchronizing SCSI cache
Mar 10 09:47:37 pve kernel: [48878.569582] sd 5:0:0:0: [sdd] Synchronize Cache(10) failed: Result: hostbyte=DID_ERROR >
Mar 10 09:47:37 pve kernel: [48878.865809] usb 2-10: reset SuperSpeed USB device number 3 using xhci_hcd™

The error seems to be right here, but unfortunately it is cut off. I suspect the DID_ERROR is the real issue (hardware or driver issue?).

Since you said it worked on another machine: What kernel version are you currently using? Can you try booting an older kernel to see if it works then? Or you can also try the 6.1 one if you are not already using it.

Might not be related to your issue here, but udisksd is known to cause high CPU load, so it's not recommended by us.

 

[dasc]

The error seems to be right here, but unfortunately it is cut off. I suspect the DID_ERROR is the real issue (hardware or driver issue?).

Since you said it worked on another machine: What kernel version are you currently using? Can you try booting an older kernel to see if it works then? Or you can also try the 6.1 one if you are not already using it.

Might not be related to your issue here, but udisksd is known to cause high CPU load, so it's not recommended by us.

Once again thank you

Kernel updated but drive still not visible

Is there anyway to try to recover or check the drive integrity?

 

[fiona]

Kernel updated but drive still not visible

What about an older kernel? What did the other machine where it worked have?

Is there anyway to try to recover or check the drive integrity?

The issue seems to be already during initialization/connection. I don't know any tools for that unfortunately, just for checking health once the drive is connected. You can also try and search the internet with the full message containing DID_ERROR.