4Kn drives don't show in OMV

  • I have a problem with SAS 4kn (native) harddrives, connected to my server via a SAS controller.

    The controller can see the HD and it reports correct size 3.7 TB but after booting, in OMV/Debian the drive does not show up at all.

    The drives are 4TB Seagate drives, type  ST4000NM014

    The SAS controller is a HP (725904-001) 9217-4i4e-HP - FH PCIe-x8 RAID Controller running in IT-mode (HBA).


    The controller also has 2 'normal' SAS drives attached and they work well under OMV.


    Is there anything I need to install to make 4Kn drives work?

    OMV6 i5-based PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD CPU)

    • Offizieller Beitrag

    What is the output of: sudo parted --list

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • >> my parted --list output:


    # SATA drive (not scsi)

    Model: ATA TOSHIBA DT01ACA0 (scsi)

    Disk /dev/sda: 500GB

    Sector size (logical/physical): 512B/4096B

    Partition Table: loop

    Disk Flags:


    Number Start End Size File system Flags

    1 0.00B 500GB 500GB btrfs


    # SATA drive (not scsi)

    Model: ATA ST3000VN007-2E41 (scsi)

    Disk /dev/sdb: 3001GB

    Sector size (logical/physical): 512B/4096B

    Partition Table: gpt

    Disk Flags:


    Number Start End Size File system Name Flags

    1 17.4kB 3001GB 3001GB ntfs msftdata


    # SATA SSD

    Model: ATA Corsair Force GT (scsi)

    Disk /dev/sdc: 60.0GB

    Sector size (logical/physical): 512B/512B

    Partition Table: msdos

    Disk Flags:


    Number Start End Size Type File system Flags

    1 1049kB 59.0GB 59.0GB primary ext4 boot

    2 59.0GB 60.0GB 1022MB extended

    5 59.0GB 60.0GB 1022MB logical linux-swap(v1)


    # 'normal SAS drive, non 4Kn

    Model: SEAGATE ST330006CLAR3000 (scsi)

    Disk /dev/sdd: 3001GB

    Sector size (logical/physical): 512B/512B

    Partition Table: gpt

    Disk Flags:


    Number Start End Size File system Name Flags

    1 1049kB 3001GB 3001GB ext4


    # 'normal SAS drive, non 4Kn

    Model: SEAGATE ST33000650SS (scsi)

    Disk /dev/sde: 3001GB

    Sector size (logical/physical): 512B/512B

    Partition Table: gpt

    Disk Flags:


    Number Start End Size File system Name Flags

    1 1049kB 3001GB 3001GB ext4

    OMV6 i5-based PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD CPU)

    • Offizieller Beitrag

    It doesn't look like your kernel "sees" them either.

    sudo dmesg | grep -A3 'Attached SCSI'


    What kernel are you running?

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Kernel 6.1.0-0.deb11.7-amd64

    Here it seems to see 3 disks

    OMV6 i5-based PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD CPU)

    Einmal editiert, zuletzt von MarcS ()

    • Offizieller Beitrag

    Here it seems to see 3 disks

    Those are the same disks that parted is reporting. The kernel does not know about the disks. I would guess something in the SAS controller needs to be configured different. I have never used that controller to offer a suggestion on what to change.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

  • Its a common SAS controller based on the LSI 2308 chip which has widely been reported as supporting 4Kn drives.

    The controller has nothing to setup and the other SAS drives work well. The 4Kn drive shows up there in the list without any issues, even shows the right size 3.7TB so the controller knows about the 4096 sector size. Other SAS controllers I tried did not show the correct disk size as they did not support 4K sectors.


    I will check the firmware. Maybe i need to tweak that.

    thanks

    OMV6 i5-based PC

    OMV6 on Raspberry Pi4

    OMV5 on ProLiant N54L (AMD CPU)

    • Offizieller Beitrag

    Its a common SAS controller based on the LSI 2308 chip which has widely been reported as supporting 4Kn drives.

    I have used plenty of LSI cards (own three) and that chipset before but not with HP's firmware on them.


    The controller has nothing to setup

    It is really hard to know that when I don't have the card and drives in front of me. All I know is that Linux has supported 4kn drives for years. So, I know it is hardware related.

    omv 7.0.5-1 sandworm | 64 bit | 6.8 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.13 | compose 7.2 | k8s 7.1.0-3 | cputemp 7.0.1 | mergerfs 7.0.4


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!