JorgeB

Yes.

Since it's xfs you cannot do a direct replacement, you can use this: https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=511923

Start the array in normal mode, disk should mount now, check contents and look for a lost+found folder.

It involves syncing the existing disks with parity, if the disks have been used before they won't be all zeros so parity needs to be updated accordingly, and even on new disks there are no guarantees they are all zeros, though they usually are, Unraid need to make sure, or there could be data loss later.

Please post the diagnostics after booting v6.11.1

Type: xfs_repair -vL /dev/md4

Sorry, I cannot help more, no experience with that, like mentioned rebuilding to a larger disk might work, other than that and if you have backups format the disk and restore from there.

I don't see any problems in the diags, disks are all there: Oct 6 20:51:34 Tower emhttpd: Device inventory: Oct 6 20:51:34 Tower emhttpd: ST1000DM010-2EP102_Z9AAWBVC (sdd) 512 1953525168 Oct 6 20:51:34 Tower emhttpd: ST1000DM010-2EP102_Z9ADYN2H (sde) 512 1953525168 Oct 6 20:51:34 Tower emhttpd: ST1000DM010-2EP102_Z9AAWHND (sdb) 512 1953525168 Oct 6 20:51:34 Tower emhttpd: ST1000DM010-2EP102_Z9ADYR2Z (sdc) 512 1953525168 Oct 6 20:51:34 Tower emhttpd: Generic_Mass_Storage_CF1AFDF9-0:0 (sda) 512 3911680 Did you try a different browser?

At least SMART looks OK for now.

Sorry, please ignore, I misread.

Do you mean that it was working before with v6.10.3 and if you downgrade now it doesn't work? That would suggest there are other issues.

Try gdisk /dev/sdX and see if it gives the option to fix the partition.

That means UD is also not detecting a valid partition, one way out of this might be replacing the disk with a larger one, though cannot be sure it's going to work.

I would recommend setting it as eth0, or you might run into other issues in the future.

Strange but not wort losing time over that, do it on the command line, start the array in maintenance mode then type: xfs_repair -v /dev/md4

Oct 7 10:39:37 STORMWATCH kernel: mount: attempt to access beyond end of device There's a problem related to the device size in the emulated disk, see if the actual disk mounts with the UD plugin.

Unraid requires that the main NIC be eth0, swap the NICs below in the interface rules section and reboot.

OK, devices changed since the diags you've posted, it was sdc: Oct 7 00:12:30 STORMWATCH emhttpd: WDC_WD30EFRX-68EUZN0_WD-WCC4N1PYS69N (sdc) 512 5860531055 It confirms that the partition is damaged, easiest option it to rebuild the disk since Unraid will recreate the partition, stop array, unassign that disk, start array, post new diags.

Some help below, also easy to find if you google it. https://wiki.unraid.net/Crossflashing_Controllers

There are no NTP servers configured, set pool.ntp.org as NTP server 1.

Disks are being detected, looks more like a config problem, try booting in safe mode, if still issues try with a fresh flash drive install, just to see if the GUI works correctly.

Enable mirror to flash, just don't forget to disable it once it's not needed.

It's not in IT mode: Kernel modules: megaraid_sas

Did we need believe the problem were the NICs?

Click on the disk and set the fs to xfs, then check filesystem.