[SOLVED] Add Directory works then disks disappear

wonko6x9

Active Member
Oct 16, 2018
11
1
43
55
USA
I am having a real issue. I have two SATA 16Tb hard drives in the back of my HPE DL380 Gen9. I am running 12 6TB SAS HDs in the front plane in 1=0 raid with a P840 card.

I have tried adding the drives with the native SATA controllers, I have tried adding them through thep840, I have added raid 0 on the drives (I really don't want to do that If I can avoid it).

The best that has happened to this point is I will add the directory and the drive immediately disappears as soon as I try and send a backup.
A lot of the time I get errors similar to this:

# /sbin/sgdisk -n1 -t1:8300 /dev/sdb
Creating new GPT entries in memory.
The operation has completed successfully.
# /sbin/mkfs -t ext4 /dev/sdb1
mke2fs 1.47.0 (5-Feb-2023)
Creating filesystem with 3906469627 4k blocks and 488308736 inodes
Filesystem UUID: 75f5bc01-2fa9-4a4e-8272-be9d31e9ca82
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544, 1934917632,
2560000000, 3855122432

Allocating group tables: 0/119216 done
Writing inode tables: 0/119216 done
Creating journal (262144 blocks): done
Writing superblocks and filesystem accounting information: 0/119216 mkfs.ext4: Input/output error while writing out and closing file system
TASK ERROR: command '/sbin/mkfs -t ext4 /dev/sdb1' failed: exit code 1



# /sbin/sgdisk -n1 -t1:8300 /dev/sdb
Warning! Disk size is smaller than the main header indicates! Loading
secondary header from the last sector of the disk! You should use 'v' to
verify disk integrity, and perhaps options on the experts' menu to repair
the disk.
Warning! Main and backup partition tables differ! Use the 'c' and 'e' options
on the recovery & transformation menu to examine the two tables.

Warning! One or more CRCs don't match. You should repair the disk!
Main header: OK
Backup header: OK
Main partition table: OK
Backup partition table: ERROR

****************************************************************************
Caution: Found protective or hybrid MBR and corrupt GPT. Using GPT, but disk
verification and recovery are STRONGLY recommended.
****************************************************************************
Could not create partition 1 from 34 to 2047
Error encountered; not saving changes.
TASK ERROR: command '/sbin/sgdisk -n1 -t1:8300 /dev/sdb' failed: exit code 4


I was convinced it was AHCI for a bit, but I'm less so now. I'm at a loss. I have tried everything I can find, and nothing seems to do the trick. The second error is interesting, but I haven't figured it out yet. Any thoughts?
 
Last edited:
Well, I think i solved it. It wasn't code, and it wasn't the hard drives. I have G10 3LFF backplane kicking around and after looking at it, I realized that it would fit on the G9, with a bit of compromise. Only one screw fits, but there is a lock that pretty much makes up for that. I swapped out the backplane, and it seems to be rock solid now. I'm running a backup to test it, but I think we are good. So if you are having issues where you cannot get drives to stay showing in the OS the minute you try and write to them, look at your backplane. I'll put it under the microscope and see if there is any obvious damage to the components. I don't see anything at the moment, but there must be something wrong. Anyway, problem solved.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!