Hard disk is no longer recognized in the OS after Proxmox update

[woinqw3]

Hi!

I am currently assembling a new server, which runs after the initial installation of Proxmox 8.1.5 and recognizes everything (including the SATA hard drive (sda)), but can no longer be found after an apt-get update && upgrade with reboot. The hard disk is still recognized in the BIOS, but can no longer be found in the OS.

Configuration:
MB: Biostar B660T-Silver (flashed with current BIOS)
CPU: Intel Core i3-12100
RAM: Corsair Vengeance LPX 64GB, DDR4-3200
HDD: Toshiba MG09

In the attachment I have attached the results of "udevadm info /dev/sda" and "dmesg | grep scsi", after the fresh installation, where the HDD is still recognized and a "lsblk" as it currently looks after the update/upgrade and another "journalctl" from the boot, after the update. I had mounted the HDD with ext4 as a test. I suspect a non-compatible kernel. I also tried it with Proxmox VE 7.4 with the same results.

root@proxmox:~# lspci
00:00.0 Host bridge: Intel Corporation Device 4630 (rev 05)
00:02.0 VGA compatible controller: Intel Corporation Alder Lake-S GT1 [UHD Graphics 730] (rev 0c)
00:0a.0 Signal processing controller: Intel Corporation Platform Monitoring Technology (rev 01)
00:14.0 USB controller: Intel Corporation Alder Lake-S PCH USB 3.2 Gen 2x2 XHCI Controller (rev 11)
00:14.2 RAM memory: Intel Corporation Alder Lake-S PCH Shared SRAM (rev 11)
00:15.0 Serial bus controller: Intel Corporation Alder Lake-S PCH Serial IO I2C Controller #0 (rev 11)
00:15.1 Serial bus controller: Intel Corporation Alder Lake-S PCH Serial IO I2C Controller #1 (rev 11)
00:16.0 Communication controller: Intel Corporation Alder Lake-S PCH HECI Controller #1 (rev 11)
00:17.0 SATA controller: Intel Corporation Alder Lake-S PCH SATA Controller [AHCI Mode] (rev 11)
00:1a.0 PCI bridge: Intel Corporation Alder Lake-S PCH PCI Express Root Port #25 (rev 11)
00:1d.0 PCI bridge: Intel Corporation Device 7ab6 (rev 11)
00:1f.0 ISA bridge: Intel Corporation Device 7a86 (rev 11)
00:1f.3 Audio device: Intel Corporation Alder Lake-S HD Audio Controller (rev 11)
00:1f.4 SMBus: Intel Corporation Alder Lake-S PCH SMBus Controller (rev 11)
00:1f.5 Serial bus controller: Intel Corporation Alder Lake-S PCH SPI Controller (rev 11)
01:00.0 Non-Volatile memory controller: Sandisk Corp WD Blue SN580 NVMe SSD (DRAM-less) (rev 01)
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)

Best regards, woinqw3


EDIT: I pinned my kernel to 6.5.11-8-pve and now it works! I guess something between kernel 6.5.11-8-pve and 6.5.13-3-pve breaks the ACPI Sata Controller for my setup.

 

[BobhWasatch]

Did you really do "apt upgrade" instead of "apt dist-upgrade"? That could be a problem. The lsblk output looks reasonable, your rootfs would be the pve-root logical volume.

Why do you think it is trying to mount /mnt/pve/storage? That isn't a default configuration. What else did you do besides the upgrade?

 

[woinqw3]

Did you really do "apt upgrade" instead of "apt dist-upgrade"? That could be a problem. The lsblk output looks reasonable, your rootfs would be the pve-root logical volume.

Why do you think it is trying to mount /mnt/pve/storage? That isn't a default configuration. What else did you do besides the upgrade?

I used the Proxmox VE Post Install Helper script from here. But the same happends with the fresh install when i manually "apt-get update && upgrade". Ignore the /mnt/pve/storage errors, like I said, I just tested the HDD with random read/write tests making sure the hdd works like intended.

 

[BobhWasatch]

You should always use dist-upgrade or full-upgrade.

 

[milew]

Mar 23 18:37:31 proxmox pvestatd[916]: unable to activate storage 'storage' - directory is expected to be a mount point but is not mounted: '/mnt/pve/storage'

Do you have this directory on /mnt/pve/storage ?

 

[arjones5]

We just had a new admin run apt upgrade on one of the lab nodes and pinning an older kernel worked (6.5.13-5 in our case) to get the raid to show up again, so we're at least pulling backups off. My question is whether we should plan to reimage the node or take a run at a normal dist-upgrade to bring it all back to current?