Hello,

I'm sure this was asked a lot of times, but I can't find anything in particular about my case. So, I own an IBM x3650 M4, and I don't know how to flash the LSI board to make it expose the disk straight into Unraid, so what I did was I created a virtual drive managed by Mega RAID with all my disks and then used Unraid. However, yesterday after a power outage, the server went down, and now the array says "Unmountable disk - No File System". I tried maintenance mode and changed the disk slot to see if it would solve it, but not really. The file system is ZFS, and it detected it but won't let me change it to anything else; it is greyed out. I really do not want to format this disk; it has a lot of personal stuff and backups. Any solution to this problem?

Really appreciated,

Augusto

syslog.txt concorde-diagnostics-20251108-0711.zip

Edited November 8, 2025Nov 8 by gustolf

1 hour ago, gustolf said:

I created a virtual drive managed by Mega RAID with all my disks and then used Unraid

This is a terrible idea.

Nov 7 17:17:56 Concorde kernel: md: disk1 read error, sector=0

RAID volume is giving read errors; I'm not sure if/how to resolve that. Look in the controller BIOS/Sofware to see if there are any issues reported with the RAID volume.

11 minutes ago, JorgeB said:

This is a terrible idea.

I know but I really do not have the knowledge to flash it and I dont find any easy enough tutorial or one that works

12 minutes ago, JorgeB said:

RAID volume is giving read errors; I'm not sure if/how to resolve that. Look in the controller BIOS/Sofware to see if there are any issues reported with the RAID volume.

I'll have a look and come back to you

Okay, so I managed to find a very old tutorial on the web archive on how to flash the M5110e into IT mode, and that has been done successfully... However, now whenever I boot into Unraid, all my disks don't show up or take a huge amount of time to appear. When they do appear, and I try to make an array, some disks cannot be formatted, and the ones that can only produce errors when I'm trying to build the parity. I have no idea what triggers the disks to appear when they do... I saw somewhere here in the forum to add append pci=realloc=off initrd=/bzroot. I did. I have no idea if that makes any difference.

I appreciate any help. I'm very lost.

default menu.c32
menu title Lime Technology, Inc.
prompt 0
timeout 50
label Unraid OS
  menu default
  kernel /bzimage
  append pci=realloc=off initrd=/bzroot
label Unraid OS GUI Mode
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui
label Unraid OS Safe Mode (no plugins, no GUI)
  kernel /bzimage
  append initrd=/bzroot unraidsafemode
label Unraid OS GUI Safe Mode (no plugins)
  kernel /bzimage
  append initrd=/bzroot,/bzroot-gui unraidsafemode
label Memtest86+
  kernel /memtest

syslog.txt concorde-diagnostics-20251111-1825.zip

Edited November 11, 2025Nov 11 by gustolf

Sorry this upload is just to show the crazy amount of errors...

Devices are dropping left and right, are they connected directly to the controller or using a backplane/expander?

They’ve on an IBM SAS expander backplane, not direct.

If you can, connect one or two disks directly and retest.

Okay I will try that today and let you know thank you.

Could it be because I gave a random SAS address during the flashing? Also I don’t know if it helps in anyway troubleshooting this but the tutorial I followed was this in the attachment.

1. INSTRUCTIONS.pdf

2 hours ago, JorgeB said:

If you can, connect one or two disks directly and retest

The problems still persists when directly connected.

Post new diags, please.

Okay, I went down to the basement to recheck the cabling, and I realised that I forgot to power the SAS board without the expanded plate, so that’s why the disks were not being recognised anyways. Whoever, one of them still shows errors when I'm trying to format. The diagnostics and system log are attached. I still don't know if it's something I'm doing wrong or just hardware incompatibility.

Plus, in the IMM, the system detects eight drives while Unraid only sees seven?

concorde-diagnostics-20251112-1202.zip syslog.txt

No longer seeing the constant errors as before, there are read errors with disk1, they are logged as device problem, but you can try swapping cables/slots with another disk, then try again, and see where the issue follows.

For the missing disk, also try swapping with a different one.

Thank you for all your help so far!

Now, the fact that the disks show without the expander does this mean that the expander is not compatible with the new firmware?

It's possible, they were being detected, but there were apparent issues while initializing them, but LSI IT mode is probably the most common SAS/SATA controller out there, so it's weird it would have issues with that.