Home Assistant runing on Proxmox not detecting second drive

Installation
#1

I followed this guide to set up Home Assistant on Proxmox: Installing Home Assistant using Proxmox

Now I’ve added a second drive to my system and added it to Proxmox. The hardware tab on the VM now looks like this:

However, when I try to run ‘fdisk -l’ or ‘sudo fdisk -l’ over SSH, the output is empty. This leads me to believe it isn’t detecting the drive somehow. I’m still very much a beginner when it comes to Proxmox, so I have no idea what could be causing this. I want to mount the second drive and use it to store recordings from Frigate. Anyone know how I can fix this?

#2

What does dmesg and ls -l /dev/sd* tell you?

#3

I found the following in dmesg:

[    1.226831] ata6: SATA link down (SStatus 0 SControl 300)
[    1.228507] ata2: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.230211] ata2.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
[    1.231177] ata2.00: 1073741824 sectors, multi 16: LBA48 NCQ (depth 32)
[    1.232310] ata2.00: applying bridge limits
[    1.233053] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
[    1.233802] ata1.00: ATA-7: QEMU HARDDISK, 2.5+, max UDMA/100
[    1.234435] ata1.00: 419430400 sectors, multi 16: LBA48 NCQ (depth 32)
[    1.235110] ata1.00: applying bridge limits
[    1.235823] ata3: SATA link down (SStatus 0 SControl 300)
[    1.236596] ata4: SATA link down (SStatus 0 SControl 300)
[    1.237335] ata5: SATA link down (SStatus 0 SControl 300)
[    1.238032] ata2.00: configured for UDMA/100
[    1.238605] ata1.00: configured for UDMA/100
[    1.239208] scsi 0:0:0:0: Direct-Access     ATA      QEMU HARDDISK    2.5+ PQ: 0 ANSI: 5
[    1.240128] sd 0:0:0:0: Attached scsi generic sg0 type 0
[    1.240150] sd 0:0:0:0: [sda] 419430400 512-byte logical blocks: (215 GB/200 GiB)
[    1.240822] scsi 1:0:0:0: Direct-Access     ATA      QEMU HARDDISK    2.5+ PQ: 0 ANSI: 5
[    1.241453] sd 0:0:0:0: [sda] Write Protect is off
[    1.242263] sd 1:0:0:0: Attached scsi generic sg1 type 0
[    1.242286] sd 1:0:0:0: [sdb] 1073741824 512-byte logical blocks: (550 GB/512 GiB)
[    1.242290] sd 1:0:0:0: [sdb] Write Protect is off
[    1.242291] sd 1:0:0:0: [sdb] Mode Sense: 00 3a 00 00
[    1.242298] sd 1:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.242778] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[    1.245905] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.246380] sd 1:0:0:0: [sdb] Attached SCSI disk
[    1.250075]  sda: sda1 sda2 sda3 sda4 sda5 sda6 sda7 sda8
[    1.250967] sd 0:0:0:0: [sda] Attached SCSI disk

And the other command:

➜  ~ ls -l /dev/sd*
brw-rw----    1 root     disk        8,   0 Apr 25 09:53 /dev/sda
brw-rw----    1 root     disk        8,   1 Apr 25 09:53 /dev/sda1
brw-rw----    1 root     disk        8,   2 Apr 25 09:53 /dev/sda2
brw-rw----    1 root     disk        8,   3 Apr 25 09:53 /dev/sda3
brw-rw----    1 root     disk        8,   4 Apr 25 09:53 /dev/sda4
brw-rw----    1 root     disk        8,   5 Apr 25 09:53 /dev/sda5
brw-rw----    1 root     disk        8,   6 Apr 25 09:53 /dev/sda6
brw-rw----    1 root     disk        8,   7 Apr 25 09:53 /dev/sda7
brw-rw----    1 root     disk        8,   8 Apr 25 09:53 /dev/sda8
brw-rw----    1 root     disk        8,  16 Apr 25 09:53 /dev/sdb

If I’m understanding these logs correctly, the disk is being detected. How should I mount it?

#4

/dev/sdb is the second drive, but it is not partitioned. Once it is you’ll have /dev/sdb1 etc.

I can’t recall exactly how proxmox is put together, but isn’t there an underlying debian system which will have partitioning tools.

#5

As that line show to you
[ 1.242286] sd 1:0:0:0: [sdb] 1073741824 512-byte logical blocks: (550 GB/512 GiB)

Your 512GiB or 550GB is identified as sdb.

You don’t really need to partition it,
you could directly format it with mkfs.ext4 /dev/sdb

#6

Im having the exact same problem at the moment, I have my secondary disk identified as sdb but HA ssh doesn’t identifies mkfs or mkfs.ext4 as a valid operation. How can I format it then?

#7

@MisterMelDev did you managed to solved this?

#8

You can read this article

#9

Thanks! Still I wasn’t able to solve it yet