I am new to Zima. I have it installed v1.6.1 and can access the webUI.
I have a 512GB NVME that has Zima install and 4, 4TB SSD drives attached to an sas to sata HBA
When I try to add my 4, 4TB drives, they are not detected or for that matter, there is no option that allows me to see them
I know the drives are functional because during Zima install, they were visible for installation.
Can anyone help me figure out why they are not able to be added?
What happens when you click on Enable on the second screen shot?
Because the drives were visible during install, the first thing I would check is whether ZimaOS can still see the HBA and the 4 SSDs at the OS level. The WebUI may not show them if the controller/driver is not being detected properly, or if the disks already have partitions/filesystems that ZimaOS is not treating as available for “Create storage”.
Can you SSH into ZimaOS and run these checks?
lsblk -o NAME,SIZE,MODEL,SERIAL,FSTYPE,MOUNTPOINT
lspci | grep -i -E "sas|sata|raid|lsi|hba|storage"
dmesg | grep -i -E "sas|sata|scsi|lsi|megaraid|mpt|ahci|ata|error|fail"
Please paste the output here.
The important thing is to confirm whether the 4 × 4TB SSDs appear as /dev/sdX devices in lsblk.
If they do appear in lsblk, then the issue is probably with how ZimaOS is presenting them in the Storage UI.
If they do not appear in lsblk, then the issue is lower level, likely the HBA/controller driver or how the HBA is presenting the disks to ZimaOS.
Also, if the HBA is a RAID card instead of a true IT-mode HBA, ZimaOS may not see the individual drives correctly. The lspci output should help confirm what controller it is.
No option to enable anything based on the screenshots
Here is the output. Also I previously had TrueNAS installed for the past week with the same HBA and drives.
THe controller card (IBM Lenovo M1210 4-Port 12Gb/s SAS/SATA RAID Controller) is in jbod mode but a TrueNAS raid volume was created.
─── Welcome to Zima OS, root ─── Date: Wednesday, June 03, 2026 | Uptime: up 8 hours, 34 minutes root@ZimaOS:/root ➜ # lsblk -o NAME,SIZE,MODEL,SERIAL,FSTYPE,MOUNTPOINT NAME SIZE MODEL SERIAL FSTYPE MOUNTPOINT loop0 4.5M squashfs loop1 1.1M squashfs loop2 208K squashfs loop3 1.1M squashfs loop4 208K squashfs loop5 4.5M squashfs nbd0 0B nbd1 0B nbd2 0B nbd3 0B nbd4 0B nbd5 0B nbd6 0B nbd7 0B zram0 2G [SWAP] zram1 0B zram2 0B nvme0n1 476.9G WDC PC SN530 SDBPNPZ-512G-1002 201556800602 ├─nvme0n1p1 32M vfat /mnt/boot ├─nvme0n1p2 24M squashfs ├─nvme0n1p3 6G squashfs / ├─nvme0n1p4 24M ├─nvme0n1p5 6G ├─nvme0n1p6 8M ├─nvme0n1p7 96M ext4 /mnt/overlay └─nvme0n1p8 464.8G ext4 /DATA nbd8 0B nbd9 0B nbd10 0B nbd11 0B nbd12 0B nbd13 0B nbd14 0B nbd15 0B root@ZimaOS:/root ➜ # lspci | grep -i -E “sas|sata|raid|lsi|hba|storage” 00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10) 01:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS-3 3008 [Fury] (rev 02) root@ZimaOS:/root ➜ # dmesg | grep -i -E “sas|sata|scsi|lsi|megaraid|mpt|ahci|ata|error|fail” [ 0.000000] Linux version 6.12.25 (root@4f05175143f9) (x86_64-buildroot-linux-gnu-gcc.br_real (Buildroot 2023.02-10700-g0f735ee08d0) 13.4.0, GNU ld (GNU Binutils) 2.43.1) #3 SMP PREEMPT_DYNAMIC Mon Apr 20 05:09:01 UTC 2026 [ 0.000000] BIOS-e820: [mem 0x000000009ad02000-0x000000009adb7fff] ACPI data [ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000009efff] usable [ 0.000000] reserve setup_data: [mem 0x000000000009f000-0x00000000000fffff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x000000008cb4e017] usable [ 0.000000] reserve setup_data: [mem 0x000000008cb4e018-0x000000008cb5ee57] usable [ 0.000000] reserve setup_data: [mem 0x000000008cb5ee58-0x000000008cb5f017] usable [ 0.000000] reserve setup_data: [mem 0x000000008cb5f018-0x000000008cb79e57] usable [ 0.000000] reserve setup_data: [mem 0x000000008cb79e58-0x0000000099214fff] usable [ 0.000000] reserve setup_data: [mem 0x0000000099215000-0x000000009ad01fff] reserved [ 0.000000] reserve setup_data: [mem 0x000000009ad02000-0x000000009adb7fff] ACPI data [ 0.000000] reserve setup_data: [mem 0x000000009adb8000-0x000000009b219fff] ACPI NVS [ 0.000000] reserve setup_data: [mem 0x000000009b21a000-0x000000009bc0efff] reserved [ 0.000000] reserve setup_data: [mem 0x000000009bc0f000-0x000000009bc0ffff] usable [ 0.000000] reserve setup_data: [mem 0x000000009bc10000-0x000000009f7fffff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fe000000-0x00000000fe010fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved [ 0.000000] reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved [ 0.000000] reserve setup_data: [mem 0x0000000100000000-0x000000045e7fffff] usable [ 0.014565] NODE_DATA(0) allocated [mem 0x45e7f9c80-0x45e7fddff] [ 0.128075] Dynamic Preempt: voluntary [ 0.128126] rcu: Preemptible hierarchical RCU implementation. [ 0.143628] MMIO Stale Data: Mitigation: Clear CPU buffers [ 0.155524] Memory: 16227296K/16639696K available (20480K kernel code, 2678K rwdata, 7512K rodata, 3308K init, 4260K bss, 400892K reserved, 0K cma-reserved) [ 0.442594] SCSI subsystem initialized [ 0.442610] libata version 3.00 loaded. [ 0.513560] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) [ 0.531872] aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded [ 0.531900] megasas: 07.727.03.00-rc1 [ 0.532251] megaraid_sas 0000:01:00.0: BAR:0x1 BAR’s base_addr(phys):0x00000000b1300000 mapped virt_addr:0x00000000a2ec868a [ 0.532259] megaraid_sas 0000:01:00.0: Waiting for FW to come to ready state [ 0.552988] megaraid_sas 0000:01:00.0: FW in FAULT state, Fault code:0x40000 subcode:0x0 func:megasas_transition_to_ready [ 0.552997] megaraid_sas 0000:01:00.0: System Register set: [ 0.553123] megaraid_sas 0000:01:00.0: Failed to transition controller to ready from megasas_init_fw! [ 0.553136] megaraid_sas 0000:01:00.0: Failed from megasas_init_fw 6546 [ 0.553394] mpt3sas version 48.100.00.00 loaded [ 0.553661] VMware PVSCSI driver - version 1.0.7.0-k [ 0.554451] ahci 0000:00:17.0: version 3.0 [ 0.554789] ahci 0000:00:17.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode [ 0.554796] ahci 0000:00:17.0: 6/6 ports implemented (port mask 0x3f) [ 0.554800] ahci 0000:00:17.0: flags: 64bit ncq sntf pm clo only pio slum part ems deso sadm sds apst [ 0.608614] scsi host0: ahci [ 0.609043] scsi host1: ahci [ 0.609427] scsi host2: ahci [ 0.609722] scsi host3: ahci [ 0.609976] scsi host4: ahci [ 0.610183] scsi host5: ahci [ 0.610239] ata1: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539100 irq 125 lpm-pol 3 [ 0.610245] ata2: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539180 irq 125 lpm-pol 3 [ 0.610249] ata3: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539200 irq 125 lpm-pol 3 [ 0.610252] ata4: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539280 irq 125 lpm-pol 3 [ 0.610256] ata5: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539300 irq 125 lpm-pol 3 [ 0.610260] ata6: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539380 irq 125 lpm-pol 3 [ 0.916825] ata6: SATA link down (SStatus 4 SControl 300) [ 0.916868] ata2: SATA link down (SStatus 4 SControl 300) [ 0.916909] ata4: SATA link down (SStatus 4 SControl 300) [ 0.916941] ata1: SATA link down (SStatus 4 SControl 300) [ 0.916972] ata5: SATA link down (SStatus 4 SControl 300) [ 0.917004] ata3: SATA link down (SStatus 4 SControl 300) [ 1.097734] Write protecting the kernel read-only data: 28672k [ 1.098779] Freeing unused kernel image (rodata/data gap) memory: 680K [ 1.422174] EXT4-fs (nvme0n1p7): mounted filesystem b7128bdd-d08d-4c85-a13d-a019466e3d66 r/w with ordered data mode. Quota mode: none. [ 4.733733] systemd[1]: Expecting device /dev/disk/by-label/casaos-data… [ 4.751978] systemd[1]: var.mount: Directory /var to mount over is not empty, mounting anyway. [ 4.796716] systemd[1]: One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi). [ 4.796756] systemd[1]: Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore). [ 5.797901] EXT4-fs (nvme0n1p8): mounted filesystem 6074e13b-1d63-42a1-be47-05508ef742e0 r/w with ordered data mode. Quota mode: none. [ 6.484626] i915 0000:00:02.0: [drm] [ENCODER:98:DDI A/PHY A] failed to retrieve link info, disabling eDP [ 7.369519] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 7.380552] Adding 5414940k swap on /DATA/.swapfile. Priority:10 extents:42 across:6243964k SS [ 9.089610] Loading iSCSI transport class v2.0-870. [ 55.669059] nvme nvme0: using unchecked data buffer
Thanks for posting the output. This helps a lot.
At the moment ZimaOS is not seeing the 4 × 4TB SSDs at all. lsblk only shows the NVMe system drive, so the Storage UI has nothing to add.
The important part is this from dmesg:
megaraid_sas 0000:01:00.0: FW in FAULT statemegaraid_sas 0000:01:00.0: Failed to transition controller to ready
So ZimaOS can see the controller:
Broadcom / LSI MegaRAID SAS-3 3008 [Fury]
But the controller firmware is not coming online properly, which is why no disks appear.
Because this card previously had TrueNAS using the same drives, I would check the controller BIOS/firmware first. There may be a foreign configuration, RAID metadata, or the card may not actually be exposing the drives cleanly as individual JBOD disks to ZimaOS.
A few safe checks you can run next:
ls /dev/sd*
lspci -nnk -s 01:00.0
dmesg | grep -i megaraid
If /dev/sd* shows nothing, then the drives are still not being presented to the OS.
My next step would be to reboot and enter the controller’s RAID/HBA configuration utility, then check:
1. Does the controller show all 4 SSDs?2. Are they marked JBOD / Unconfigured Good?3. Is there any Foreign Configuration from TrueNAS?4. Is the controller firmware reporting any fault?
Do not wipe or initialise anything yet unless you are happy to lose the old TrueNAS data. First confirm whether the controller itself can see the disks and whether it is presenting them individually to the OS.
Thanks and will check later this evening. But here is the output from the commands below.
The HBA is in my pc riser slot of my Lenovo m720Q i5 tiny machine.
Since I am testing out various NAS type software, the data on these drives are copies of some of my original files from my QNAP so it’s not required.
root@ZimaOS:/root ➜ # ls /dev/sd*
ls: cannot access ‘/dev/sd*’: No such file or directory
root@ZimaOS:/root ➜ # lspci -nnk -s 01:00.0
01:00.0 RAID bus controller [0104]: Broadcom / LSI MegaRAID SAS-3 3008 [Fury] [1000:005f] (rev 02)
Subsystem: Lenovo ServeRAID M1210 SAS/SATA Controller [1d49:04db]
root@ZimaOS:/root ➜ # dmesg | grep -i megaraid
[ 0.532251] megaraid_sas 0000:01:00.0: BAR:0x1 BAR’s base_addr(phys):0x00000000b1300000 mapped virt_addr:0x00000000a2ec868a
[ 0.532259] megaraid_sas 0000:01:00.0: Waiting for FW to come to ready state
[ 0.552988] megaraid_sas 0000:01:00.0: FW in FAULT state, Fault code:0x40000 subcode:0x0 func:megasas_transition_to_ready
[ 0.552997] megaraid_sas 0000:01:00.0: System Register set:
[ 0.553123] megaraid_sas 0000:01:00.0: Failed to transition controller to ready from megasas_init_fw!
[ 0.553136] megaraid_sas 0000:01:00.0: Failed from megasas_init_fw 6546
root@ZimaOS:/root ➜ #
So I can’t seems to get in to the bios using Ctrl+C as many manuals state.
I might have to put the hba into a windows machine and flash it to a newer bios version. btw, it does appear to indicate it has four drives connected.
Thanks for posting the output and the photo.
The good news is that the four SSDs do appear to be physically connected to the controller. Your MegaRAID BIOS screen can see them:
4 JBOD(s) found on the host adapter
4 JBOD(s) handled by BIOS
0 Virtual Drive(s) found
So the card itself can detect the drives at BIOS/controller level.
The problem is that the controller does not appear to be handing those drives over to ZimaOS/Linux. This part of your output is the key issue:
megaraid_sas: FW in FAULT state
megaraid_sas: Failed to transition controller to ready
megaraid_sas: Failed from megasas_init_fw
That means ZimaOS can detect the ServeRAID/MegaRAID card, but the card firmware is failing before Linux can use it properly. Because of that, the drives never appear in ZimaOS as normal disk devices.
That is also why /dev/sd* does not exist. It does not mean the SSDs are unplugged. It means the controller has not exposed them to the operating system.
So I do not think this is a ZimaOS Storage page issue yet. The next step is to troubleshoot the Lenovo ServeRAID M1210 / MegaRAID card itself, especially the firmware and controller mode.
I would check whether the controller firmware can be updated or reflashed using Lenovo/Broadcom MegaRAID tools, probably from Windows or another standard Linux install. Also confirm whether the card can properly expose the drives in JBOD/HBA-style mode.
Once the controller is healthy, boot back into ZimaOS and run:
lsblk -o NAME,SIZE,MODEL,SERIAL,FSTYPE,MOUNTPOINT
The target result is that the SSDs appear to ZimaOS as normal disks, for example /dev/sda, /dev/sdb, etc.
Until that happens, ZimaOS Storage will not be able to add them, because the disks are visible to the RAID card BIOS but not yet usable by ZimaOS.
The drives are still not being seen on the controller
Inserted the HBA into a Windows 11 desktop and using the MegaRAID Storage Manager, I was able to see the controller and the drives. Note that this was before flashing the BIOS.
I then upgraded the BIOS
I’ve placed the hba back in my M720q and at post it recognizes the HBA and 4 disks attached
After logging in to Zima the disks are still not appearing.
Below is the output from the commands I previously ran:
Date: Thursday, June 04, 2026 | Uptime: up 3 minutes
root@ZimaOS:/root ➜ # lsblk -o NAME,SIZE,MODEL,SERIAL,FSTYPE,MOUNTPOINT
NAME SIZE MODEL SERIAL FSTYPE MOUNTPOINT
loop0 1.1M squashfs
loop1 208K squashfs
loop2 4.5M squashfs
loop3 1.1M squashfs
loop4 208K squashfs
loop5 4.5M squashfs
nbd0 0B
nbd1 0B
nbd2 0B
nbd3 0B
nbd4 0B
nbd5 0B
nbd6 0B
nbd7 0B
zram0 2G [SWAP]
zram1 0B
zram2 0B
nvme0n1 476.9G WDC PC SN530 SDBPNPZ-512G-1002 201556800602
├─nvme0n1p1 32M vfat /mnt/boot
├─nvme0n1p2 24M squashfs
├─nvme0n1p3 6G squashfs /
├─nvme0n1p4 24M
├─nvme0n1p5 6G
├─nvme0n1p6 8M
├─nvme0n1p7 96M ext4 /mnt/overlay
└─nvme0n1p8 464.8G ext4 /DATA
nbd8 0B
nbd9 0B
nbd10 0B
nbd11 0B
nbd12 0B
nbd13 0B
nbd14 0B
nbd15 0B
root@ZimaOS:/root ➜ # lspci | grep -i -E “sas|sata|raid|lsi|hba|storage”
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10)
01:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS-3 3008 [Fury] (rev 02)
root@ZimaOS:/root ➜ # dmesg | grep -i -E “sas|sata|scsi|lsi|megaraid|mpt|ahci|ata|error|fail”
[ 0.000000] Linux version 6.12.25 (root@4f05175143f9) (x86_64-buildroot-linux-gnu-gcc.br_real (Buildroot 2023.02-10700-g0f735ee08d0) 13.4.0, GNU ld (GNU Binutils) 2.43.1) #3 SMP PREEMPT_DYNAMIC Mon Apr 20 05:09:01 UTC 2026
[ 0.000000] BIOS-e820: [mem 0x000000009ad02000-0x000000009adb7fff] ACPI data
[ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000005efff] usable
[ 0.000000] reserve setup_data: [mem 0x000000000005f000-0x000000000005ffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000000060000-0x000000000009ffff] usable
[ 0.000000] reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x000000008cb3d017] usable
[ 0.000000] reserve setup_data: [mem 0x000000008cb3d018-0x000000008cb4de57] usable
[ 0.000000] reserve setup_data: [mem 0x000000008cb4de58-0x000000008cb4e017] usable
[ 0.000000] reserve setup_data: [mem 0x000000008cb4e018-0x000000008cb5e057] usable
[ 0.000000] reserve setup_data: [mem 0x000000008cb5e058-0x000000008cb5f017] usable
[ 0.000000] reserve setup_data: [mem 0x000000008cb5f018-0x000000008cb79e57] usable
[ 0.000000] reserve setup_data: [mem 0x000000008cb79e58-0x0000000099214fff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000099215000-0x000000009ad01fff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000009ad02000-0x000000009adb7fff] ACPI data
[ 0.000000] reserve setup_data: [mem 0x000000009adb8000-0x000000009b219fff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x000000009b21a000-0x000000009bc0efff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000009bc0f000-0x000000009bc0ffff] usable
[ 0.000000] reserve setup_data: [mem 0x000000009bc10000-0x000000009f7fffff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000100000000-0x000000045e7fffff] usable
[ 0.015359] NODE_DATA(0) allocated [mem 0x45e7fbc80-0x45e7ffdff]
[ 0.128803] Dynamic Preempt: voluntary
[ 0.128854] rcu: Preemptible hierarchical RCU implementation.
[ 0.143959] MMIO Stale Data: Mitigation: Clear CPU buffers
[ 0.159860] Memory: 16229004K/16639696K available (20480K kernel code, 2678K rwdata, 7512K rodata, 3308K init, 4260K bss, 400948K reserved, 0K cma-reserved)
[ 0.447536] SCSI subsystem initialized
[ 0.447550] libata version 3.00 loaded.
[ 0.519542] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[ 0.537937] aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded
[ 0.537966] megasas: 07.727.03.00-rc1
[ 0.538333] megaraid_sas 0000:01:00.0: BAR:0x1 BAR’s base_addr(phys):0x00000000b1300000 mapped virt_addr:0x00000000b76cb8e0
[ 0.538342] megaraid_sas 0000:01:00.0: FW now in Ready state
[ 0.538345] megaraid_sas 0000:01:00.0: 63 bit DMA mask and 32 bit consistent mask
[ 0.538685] megaraid_sas 0000:01:00.0: firmware supports msix : (96)
[ 0.538961] megaraid_sas 0000:01:00.0: requested/available msix 7/7 poll_queue 0
[ 0.538967] megaraid_sas 0000:01:00.0: current msix/online cpus : (7/6)
[ 0.538970] megaraid_sas 0000:01:00.0: RDPQ mode : (disabled)
[ 0.538974] megaraid_sas 0000:01:00.0: Current firmware supports maximum commands: 272 LDIO threshold: 237
[ 0.539727] megaraid_sas 0000:01:00.0: Performance mode :Latency (latency index = 1)
[ 0.539731] megaraid_sas 0000:01:00.0: FW supports sync cache : Yes
[ 0.539735] megaraid_sas 0000:01:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x40000009
[ 0.560573] megaraid_sas 0000:01:00.0: Init cmd return status FAILED for SCSI host 0
[ 0.561290] megaraid_sas 0000:01:00.0: Failed from megasas_init_fw 6546
[ 0.570698] mpt3sas version 48.100.00.00 loaded
[ 0.571048] VMware PVSCSI driver - version 1.0.7.0-k
[ 0.571823] ahci 0000:00:17.0: version 3.0
[ 0.572214] ahci 0000:00:17.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
[ 0.572221] ahci 0000:00:17.0: 6/6 ports implemented (port mask 0x3f)
[ 0.572225] ahci 0000:00:17.0: flags: 64bit ncq sntf pm clo only pio slum part ems deso sadm sds apst
[ 0.624200] scsi host0: ahci
[ 0.624593] scsi host1: ahci
[ 0.624903] scsi host2: ahci
[ 0.625157] scsi host3: ahci
[ 0.625417] scsi host4: ahci
[ 0.625620] scsi host5: ahci
[ 0.625677] ata1: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539100 irq 125 lpm-pol 3
[ 0.625683] ata2: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539180 irq 125 lpm-pol 3
[ 0.625686] ata3: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539200 irq 125 lpm-pol 3
[ 0.625690] ata4: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539280 irq 125 lpm-pol 3
[ 0.625694] ata5: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539300 irq 125 lpm-pol 3
[ 0.625698] ata6: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539380 irq 125 lpm-pol 3
[ 0.933847] ata4: SATA link down (SStatus 4 SControl 300)
[ 0.933874] ata6: SATA link down (SStatus 4 SControl 300)
[ 0.933894] ata1: SATA link down (SStatus 4 SControl 300)
[ 0.933913] ata5: SATA link down (SStatus 4 SControl 300)
[ 0.933933] ata3: SATA link down (SStatus 4 SControl 300)
[ 0.933952] ata2: SATA link down (SStatus 4 SControl 300)
[ 0.946952] Write protecting the kernel read-only data: 28672k
[ 0.947594] Freeing unused kernel image (rodata/data gap) memory: 680K
[ 1.292180] EXT4-fs (nvme0n1p7): mounted filesystem b7128bdd-d08d-4c85-a13d-a019466e3d66 r/w with ordered data mode. Quota mode: none.
[ 4.578034] systemd[1]: Expecting device /dev/disk/by-label/casaos-data…
[ 4.592054] systemd[1]: var.mount: Directory /var to mount over is not empty, mounting anyway.
[ 4.643882] systemd[1]: One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi).
[ 4.643920] systemd[1]: Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore).
[ 5.885431] EXT4-fs (nvme0n1p8): mounted filesystem 6074e13b-1d63-42a1-be47-05508ef742e0 r/w with ordered data mode. Quota mode: none.
[ 6.403241] i915 0000:00:02.0: [drm] [ENCODER:98:DDI A/PHY A] failed to retrieve link info, disabling eDP
[ 7.476527] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 7.494324] Adding 5414940k swap on /DATA/.swapfile. Priority:10 extents:44 across:7495676k SS
[ 9.230751] Loading iSCSI transport class v2.0-870.
[ 58.765189] nvme nvme0: using unchecked data buffer
Thanks for posting the new output.
This is actually a useful update because the controller is no longer showing the exact same fault as before.
Previously it showed:
megaraid_sas: FW in FAULT state
megaraid_sas: Failed to transition controller to ready
In your latest boot, the controller gets further and shows:
megaraid_sas: FW now in Ready state
So the card is being detected by ZimaOS, and the firmware is at least reaching a ready state now.
However, it still fails immediately after that:
megaraid_sas: Init cmd return status FAILED for SCSI host 0
megaraid_sas: Failed from megasas_init_fw 6546
That means the Linux driver still cannot properly initialise the MegaRAID controller, so the drives are still not being handed over to ZimaOS.
This also matches your lsblk output. ZimaOS only sees the NVMe system disk. There are still no /dev/sdX disks showing for the SSDs behind the RAID card.
So the diagnosis is still basically the same:
The SSDs are visible to the RAID controller BIOS, but the controller is not successfully exposing them to ZimaOS/Linux yet.
At this point I would still focus on the Lenovo ServeRAID M1210 / MegaRAID card itself, not the ZimaOS Storage page.
The next things I would check are:
After checking the controller configuration, boot back into ZimaOS and run:
lsblk -o NAME,SIZE,MODEL,SERIAL,FSTYPE,MOUNTPOINT
Also check:
ls /dev/sd*
The target result is that the SSDs appear as normal disks, for example /dev/sda, /dev/sdb, /dev/sdc, /dev/sdd.
Until the SSDs appear in lsblk, ZimaOS Storage has nothing to add. The issue is still before the Storage page, at the RAID controller / driver initialisation stage.
Thanks, and some more information on the controller card.
The IBM M1210 is an OEM variant of the LSI 3004 / 9300-4i HBA. It appears to already be in IT Mode. The standard BIOS configuration screen (using CTRL+C) does not exist.
I can manage the hard drives directly from the operating system or via the MegaRAID software, or flash utility software like storcli, but I don’t think I can install this on ZimaOS.
There is no foreign RIAD config when connected from Windows
I’ll load up a Ubuntu Live image and see what it detects.
Thanks, and some more information on the controller card.
The IBM M1210 is an OEM variant of the LSI 3004 / 9300-4i HBA. It appears to already be in IT Mode. The standard BIOS configuration screen (using CTRL+C) does not exist.
I can manage the hard drives directly from the operating system or via the MegaRAID software, or flash utility software like storcli, but I don’t think I can install this on ZimaOS.
There is no foreign RIAD config when connected from Windows
I’ll load up a Ubuntu Live image and see what it detects.
I have now tested with Ubuntu 22.04.4LTS and can confirm the drivers are detected and seen in the OS.
At this point it appears that ZimaOS is on able to properly detect the disks attached to the HBA
I also then rebooted in the ZimaOS and this single drive now appears however, using the commands you referenced, I cannot see this drive or any others.
When I click on Manage, if does not appear to be listed.
root@ZimaOS:/root ➜ # lsblk -o NAME,SIZE,MODEL,SERIAL,FSTYPE,MOUNTPOINT
NAME SIZE MODEL SERIAL FSTYPE MOUNTPOINT
loop0 1.1M squashfs
loop1 208K squashfs
loop2 4.5M squashfs
loop3 1.1M squashfs
loop4 4.5M squashfs
loop5 208K squashfs
nbd0 0B
nbd1 0B
nbd2 0B
nbd3 0B
nbd4 0B
nbd5 0B
nbd6 0B
nbd7 0B
zram0 2G [SWAP]
zram1 0B
zram2 0B
nvme0n1 476.9G WDC PC SN530 SDBPNPZ-512G-1002 201556800602
├─nvme0n1p1 32M vfat /mnt/boot
├─nvme0n1p2 24M squashfs
├─nvme0n1p3 6G squashfs /
├─nvme0n1p4 24M
├─nvme0n1p5 6G
├─nvme0n1p6 8M
├─nvme0n1p7 96M ext4 /mnt/overlay
└─nvme0n1p8 464.8G ext4 /DATA
nbd8 0B
nbd9 0B
nbd10 0B
nbd11 0B
nbd12 0B
nbd13 0B
nbd14 0B
nbd15 0B
root@ZimaOS:/root ➜ # lspci | grep -i -E “sas|sata|raid|lsi|hba|storage”
00:17.0 SATA controller: Intel Corporation Cannon Lake PCH SATA AHCI Controller (rev 10)
01:00.0 RAID bus controller: Broadcom / LSI MegaRAID SAS-3 3008 [Fury] (rev 02)
root@ZimaOS:/root ➜ # dmesg | grep -i -E “sas|sata|scsi|lsi|megaraid|mpt|ahci|ata|error|fail”
[ 0.000000] Linux version 6.12.25 (root@4f05175143f9) (x86_64-buildroot-linux-gnu-gcc.br_real (Buildroot 2023.02-10700-g0f735ee08d0) 13.4.0, GNU ld (GNU Binutils) 2.43.1) #3 SMP PREEMPT_DYNAMIC Mon Apr 20 05:09:01 UTC 2026
[ 0.000000] BIOS-e820: [mem 0x000000009ad02000-0x000000009adb7fff] ACPI data
[ 0.000000] reserve setup_data: [mem 0x0000000000000000-0x000000000005efff] usable
[ 0.000000] reserve setup_data: [mem 0x000000000005f000-0x000000000005ffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000000060000-0x000000000009ffff] usable
[ 0.000000] reserve setup_data: [mem 0x00000000000a0000-0x00000000000fffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000000100000-0x000000008cb3d017] usable
[ 0.000000] reserve setup_data: [mem 0x000000008cb3d018-0x000000008cb4de57] usable
[ 0.000000] reserve setup_data: [mem 0x000000008cb4de58-0x000000008cb4e017] usable
[ 0.000000] reserve setup_data: [mem 0x000000008cb4e018-0x000000008cb5e057] usable
[ 0.000000] reserve setup_data: [mem 0x000000008cb5e058-0x000000008cb5f017] usable
[ 0.000000] reserve setup_data: [mem 0x000000008cb5f018-0x000000008cb79e57] usable
[ 0.000000] reserve setup_data: [mem 0x000000008cb79e58-0x0000000099214fff] usable
[ 0.000000] reserve setup_data: [mem 0x0000000099215000-0x000000009ad01fff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000009ad02000-0x000000009adb7fff] ACPI data
[ 0.000000] reserve setup_data: [mem 0x000000009adb8000-0x000000009b219fff] ACPI NVS
[ 0.000000] reserve setup_data: [mem 0x000000009b21a000-0x000000009bc0efff] reserved
[ 0.000000] reserve setup_data: [mem 0x000000009bc0f000-0x000000009bc0ffff] usable
[ 0.000000] reserve setup_data: [mem 0x000000009bc10000-0x000000009f7fffff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000f0000000-0x00000000f7ffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fed00000-0x00000000fed03fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] reserve setup_data: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
[ 0.000000] reserve setup_data: [mem 0x0000000100000000-0x000000045e7fffff] usable
[ 0.015893] NODE_DATA(0) allocated [mem 0x45e7fbc80-0x45e7ffdff]
[ 0.129350] Dynamic Preempt: voluntary
[ 0.129403] rcu: Preemptible hierarchical RCU implementation.
[ 0.144588] MMIO Stale Data: Mitigation: Clear CPU buffers
[ 0.158493] Memory: 16229004K/16639696K available (20480K kernel code, 2678K rwdata, 7512K rodata, 3308K init, 4260K bss, 400948K reserved, 0K cma-reserved)
[ 0.445477] SCSI subsystem initialized
[ 0.445490] libata version 3.00 loaded.
[ 0.517110] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249)
[ 0.535513] aic94xx: Adaptec aic94xx SAS/SATA driver version 1.0.3 loaded
[ 0.535542] megasas: 07.727.03.00-rc1
[ 0.535892] megaraid_sas 0000:01:00.0: BAR:0x1 BAR’s base_addr(phys):0x00000000b1300000 mapped virt_addr:0x00000000465a0a54
[ 0.535900] megaraid_sas 0000:01:00.0: FW now in Ready state
[ 0.535903] megaraid_sas 0000:01:00.0: 63 bit DMA mask and 32 bit consistent mask
[ 0.536236] megaraid_sas 0000:01:00.0: firmware supports msix : (96)
[ 0.536532] megaraid_sas 0000:01:00.0: requested/available msix 7/7 poll_queue 0
[ 0.536538] megaraid_sas 0000:01:00.0: current msix/online cpus : (7/6)
[ 0.536541] megaraid_sas 0000:01:00.0: RDPQ mode : (disabled)
[ 0.536545] megaraid_sas 0000:01:00.0: Current firmware supports maximum commands: 272 LDIO threshold: 237
[ 0.537287] megaraid_sas 0000:01:00.0: Performance mode :Latency (latency index = 1)
[ 0.537290] megaraid_sas 0000:01:00.0: FW supports sync cache : Yes
[ 0.537295] megaraid_sas 0000:01:00.0: megasas_disable_intr_fusion is called outbound_intr_mask:0x40000009
[ 0.557420] megaraid_sas 0000:01:00.0: Init cmd return status FAILED for SCSI host 0
[ 0.558123] megaraid_sas 0000:01:00.0: Failed from megasas_init_fw 6546
[ 0.567785] mpt3sas version 48.100.00.00 loaded
[ 0.568123] VMware PVSCSI driver - version 1.0.7.0-k
[ 0.568764] ahci 0000:00:17.0: version 3.0
[ 0.569085] ahci 0000:00:17.0: AHCI vers 0001.0301, 32 command slots, 6 Gbps, SATA mode
[ 0.569092] ahci 0000:00:17.0: 6/6 ports implemented (port mask 0x3f)
[ 0.569096] ahci 0000:00:17.0: flags: 64bit ncq sntf pm clo only pio slum part ems deso sadm sds apst
[ 0.621311] scsi host0: ahci
[ 0.621737] scsi host1: ahci
[ 0.622102] scsi host2: ahci
[ 0.622363] scsi host3: ahci
[ 0.622589] scsi host4: ahci
[ 0.622862] scsi host5: ahci
[ 0.622919] ata1: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539100 irq 125 lpm-pol 3
[ 0.622925] ata2: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539180 irq 125 lpm-pol 3
[ 0.622929] ata3: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539200 irq 125 lpm-pol 3
[ 0.622932] ata4: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539280 irq 125 lpm-pol 3
[ 0.622936] ata5: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539300 irq 125 lpm-pol 3
[ 0.622940] ata6: SATA max UDMA/133 abar m2048@0xb1539000 port 0xb1539380 irq 125 lpm-pol 3
[ 0.926525] ata3: SATA link down (SStatus 4 SControl 300)
[ 0.926568] ata4: SATA link down (SStatus 4 SControl 300)
[ 0.926599] ata2: SATA link down (SStatus 4 SControl 300)
[ 0.926633] ata1: SATA link down (SStatus 4 SControl 300)
[ 0.926664] ata5: SATA link down (SStatus 4 SControl 300)
[ 0.934588] ata6: SATA link down (SStatus 4 SControl 300)
[ 1.110483] Write protecting the kernel read-only data: 28672k
[ 1.111550] Freeing unused kernel image (rodata/data gap) memory: 680K
[ 1.429084] EXT4-fs (nvme0n1p7): mounted filesystem b7128bdd-d08d-4c85-a13d-a019466e3d66 r/w with ordered data mode. Quota mode: none.
[ 4.731189] systemd[1]: Expecting device /dev/disk/by-label/casaos-data…
[ 4.745385] systemd[1]: var.mount: Directory /var to mount over is not empty, mounting anyway.
[ 4.795693] systemd[1]: One time configuration for iscsi.service was skipped because of an unmet condition check (ConditionPathExists=!/etc/iscsi/initiatorname.iscsi).
[ 4.795729] systemd[1]: Platform Persistent Storage Archival was skipped because of an unmet condition check (ConditionDirectoryNotEmpty=/sys/fs/pstore).
[ 5.788551] EXT4-fs (nvme0n1p8): mounted filesystem 6074e13b-1d63-42a1-be47-05508ef742e0 r/w with ordered data mode. Quota mode: none.
[ 6.385326] i915 0000:00:02.0: [drm] [ENCODER:98:DDI A/PHY A] failed to retrieve link info, disabling eDP
[ 7.386186] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 7.416106] Adding 5414940k swap on /DATA/.swapfile. Priority:10 extents:44 across:7495676k SS
[ 9.170095] Loading iSCSI transport class v2.0-870.
[ 2383.953074] nvme nvme0: using unchecked data buffer
Thanks for testing Ubuntu Live. That result is very important.
Now we have a much clearer comparison:
Ubuntu 22.04.4 LTS can see the HBA and the attached disks.
ZimaOS 1.6.1 can see the controller, but does not expose the attached disks as block devices.
In ZimaOS, lsblk still only shows the NVMe system drive:
nvme0n1 476.9G WDC PC SN530
There are still no /dev/sdX drives for the SSDs behind the HBA.
The key ZimaOS log is still here:
megaraid_sas 0000:01:00.0: FW now in Ready statemegaraid_sas 0000:01:00.0: Init cmd return status FAILED for SCSI host 0megaraid_sas 0000:01:00.0: Failed from megasas_init_fw 6546
So at this point, I would say the controller and disks appear to be basically functional, because Ubuntu can see them. This now looks more like a ZimaOS 1.6.1 kernel / driver compatibility issue with this IBM / Lenovo M1210, rather than a normal Storage UI problem.
The single drive appearing in the ZimaOS UI is also misleading, because it does not appear in lsblk and does not show properly under Manage. I would not rely on the UI display until the disks appear at OS level.
I think this one may need IceWhale to look at it, because ZimaOS is detecting the card but failing to initialise it fully.
For IceWhale, the key evidence is:
ZimaOS version: 1.6.1Kernel: 6.12.25Controller: Lenovo ServeRAID M1210 / Broadcom LSI MegaRAID SAS-3 3008 [Fury]PCI ID: 1000:005fUbuntu 22.04.4 LTS: disks visibleZimaOS 1.6.1: disks not visible in lsblkZimaOS dmesg error: Failed from megasas_init_fw 6546
That is probably enough to show this is not just a user configuration issue. Ubuntu seeing the disks is the strongest comparison test.
Ok thanks. Should I wait for a patch to correct this or will this hba not be supported?
bump
I have been searching but is it fair at this point since no further replies, ZimaOS will not support this HBA?