Issue with HDD

  • I noticed a strange issue that I initially blamed it on a few power outages. I am using the latest available OMV 6 with the latest Proxmox kernel 6.2.16-11-bpo11-pve. The HDD in question is new, it was purchased last year with another one. I know that the issues shown in dmesg should mean that the HDD turned bad and today I booted into GParted Live and Seatools Bootable to check all HDDs. None of the tools are showing any errors with the HDD in question, I let it run the Short Generic Test. SMART information is clean and I cannot see any dmesg errors in GParted Live, Seatools Bootable or Ubuntu 22.04 Live. I even tried changing the SATA port. I don't know when the issue appeared, but I noticed sometime at the end of last year that my snapraid sync and scrub jobs were hung for a long time and that the snapraid.content on the affected drive is different than the ones on the other content drives.


    Could this be related to the installation or the kernel? I have not tried booting into the mainline OMV kernel or any other older kernels. I also realized I didn't change the SATA cable with a new one to rule out a bad cable. What puzzles me the most is that booting into anything else but OMV shows no error on the affected drive. One strange behavior of the affected drive is that it appeared as not mounted at some point - mountpoint was completely empty. All data on it was visible after a reboot - that scared me the most and then I started doing some basic checks that led me to running Seatools Bootable and checking it in a Live CD environment. I can read and write on it now without any issues. I fear that if I were to send it for warranty I would just get it back as functional.


    I am pasting the dmesg logs below.



    Edit: I just booted with the non Proxmox kernel 6.1.0-0.deb11.13-amd64 and I cannot see any issue with any disks. I ran snapraid and I also copied a large file to the affected disk for testing. I need to be able to use OpenCL, that is why I want to use Proxmox kernel.

    Riddle me this, riddle me that
    Who is afraid of the big, black bat?
    I write on a blog (Romanian mostly)
    Using latest OMV 7.x (HURRAY) on an Intel i5820K NAS (currently with proxmox kernel 6.11 with Nvidia GPU acceleration enabled)

    Edited once, last by tmihai20: Added more info ().

  • I work for one of the drive companies and can tell you that you are correct. If the drive passes SMART and Seatools tests, has nothing flagged in the SMART logs, then it won't be an automatic warranty replacement. These tests are designed to put the drives through base functionality tests that cover several file sizes, speed, error counts, etc. It's a hard sell to claim the drive is having a particular issue with one particular software. It takes several people turning in similar observations with that software before we would take the time to figure out if there is a vulnerability in the firmware.


    With that said, if you can somehow get your hands on the same exact model with same firmware and are able to demonstrate the same issue with that drive, that should get someone's attention. But you'll still be asked to perform many things on your system since you are the one who discovered it. :) Did you search Reddit for similar issue?

    7.4.16-1 (Sandworm)

    Raspberry Pi 4 Model B Rev 1.5

    Linux 6.6.62+rpt-rpi-v8

    Edited once, last by Barney ().

  • I did not search on Reddit. I lost a lot of time with this issue and for now it seems to not manifest itself anymore. I rebooted with the Proxmox kernel and I cannot see any issues now.

    Riddle me this, riddle me that
    Who is afraid of the big, black bat?
    I write on a blog (Romanian mostly)
    Using latest OMV 7.x (HURRAY) on an Intel i5820K NAS (currently with proxmox kernel 6.11 with Nvidia GPU acceleration enabled)

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!