JorgeB

There are a lot of active PIDs open when you try to reboot, mostly from Plex, stop all dockers and see if you can reboot normally, if yes enable them one by one until you find the culprit.

That's very far from normal, but I don't have a Mac, there have been been other reports of slow SMB performance with them, if you google mac slow smb you'll find lots of hits, might also find something that helps.

Not if it's currently working, just make sure to always have an updated flash backup, it's very easy to replace the key if it really fails.

Yes. Yes, to replace the drives you just need to have parity assigned and valid. You could replace them one by one with single parity or two by two with dual parity. No VM limits, but Unraid doesn't currently support iSCSI.

You'll need to force it.

Type "poweroff" on the console

Look more like a connection problem, replace/swap cables (both) or slot.

The rebuild should be canceled, but there's a change data can be salvaged, disk5 might have dropped offline. Power down, check/replace cables on disk5, power back on and post diags.

Please post the diagnostics: Tools -> Diagnostics

Reboot

It can if the board has IPMI, usually only server boards have that, e.g. some Supermicro and Asrock Rack boards.

That looks more like IPMI plugin related, and your board doesn't have IPMI, so if that's installed remove it.

One of the cache devices dropped offline before (one or more times): Mar 29 19:14:52 Tower kernel: BTRFS info (device sdg1): bdev /dev/sde1 errs: wr 107909131, rd 5294447, flush 1500255, corrupt 0, gen 0 Since the pool is a mirror all errors are correct automatically, and if the scrub didn't find any it means it's all up to date for now, but see here for better pool monitoring.

No, sorry.

Yes, just make sure the breakout cables are forward breakout, reverse breakout look the same but won't work for this.

Did you just un-pause it? Elapsed time is less than a minute, stats need to stabilized, according to diags it's going close to 50MB/s, which seems about right since it's reaching the slower inner sectors of the 2TB disks. You can also try the diskspeed docker, there might be one more more disks under performing.

Do you mean add an USB drive to the array? It's possible but no recommended.

https://forums.unraid.net/topic/46802-faq-for-unraid-v6/?do=findComment&comment=480421

You can use latest release.

It's the docker image used space, an the image is on disk, not memory.

No, but you can exclude a share from being moved.

Unraid is not detecting a valid partition, most likely a connection problem, does it happen to just a few drives, e.g., are they on the same controller? This is most likely because you're still using reiserfs on most disks, convert to xfs. Is that one using reiserfs? If yes see above. At least parity and disk17 need a new SATA cable. You didn't mention this, multiple disks on multiple controllers dropped offline, was this something you did on purpose? Mar 16 15:32:11 unRAID kernel: mdcmd (1): import 0 Mar 16 15:32:11 unRAID kernel: md: import_slot: 0 missing Mar 16 15:32:11 unRAID kernel: mdcmd (2): import 1 Mar 16 15:32:11 unRAID kernel: md: import_slot: 1 missing Mar 16 15:32:11 unRAID kernel: mdcmd (3): import 2 sdk 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K4UH3DN6 Mar 16 15:32:11 unRAID kernel: md: import disk2: (sdk) WDC_WD40EFRX-68N32N0_WD-WCC7K4UH3DN6 size: 3907018532 Mar 16 15:32:11 unRAID kernel: mdcmd (4): import 3 sdf 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K5UHE0A9 Mar 16 15:32:11 unRAID kernel: md: import disk3: (sdf) WDC_WD40EFRX-68N32N0_WD-WCC7K5UHE0A9 size: 3907018532 Mar 16 15:32:11 unRAID kernel: mdcmd (5): import 4 sdb 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K3THYYLS Mar 16 15:32:11 unRAID kernel: md: import disk4: (sdb) WDC_WD40EFRX-68N32N0_WD-WCC7K3THYYLS size: 3907018532 Mar 16 15:32:11 unRAID kernel: mdcmd (6): import 5 Mar 16 15:32:11 unRAID kernel: md: import_slot: 5 missing Mar 16 15:32:11 unRAID kernel: mdcmd (7): import 6 Mar 16 15:32:11 unRAID kernel: md: import_slot: 6 missing Mar 16 15:32:11 unRAID kernel: mdcmd (8): import 7 Mar 16 15:32:11 unRAID kernel: md: import_slot: 7 missing Mar 16 15:32:11 unRAID kernel: mdcmd (9): import 8 sdl 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K5RYNAFT Mar 16 15:32:11 unRAID kernel: md: import disk8: (sdl) WDC_WD40EFRX-68N32N0_WD-WCC7K5RYNAFT size: 3907018532 Mar 16 15:32:11 unRAID kernel: mdcmd (10): import 9 sdg 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K6SKEZ5C Mar 16 15:32:11 unRAID kernel: md: import disk9: (sdg) WDC_WD40EFRX-68N32N0_WD-WCC7K6SKEZ5C size: 3907018532 Mar 16 15:32:11 unRAID kernel: mdcmd (11): import 10 sde 64 5860522532 0 WDC_WD60EFRX-68L0BN1_WD-WX71DC8F5THF Mar 16 15:32:11 unRAID kernel: md: import disk10: (sde) WDC_WD60EFRX-68L0BN1_WD-WX71DC8F5THF size: 5860522532 Mar 16 15:32:11 unRAID kernel: mdcmd (12): import 11 Mar 16 15:32:11 unRAID kernel: md: import_slot: 11 missing Mar 16 15:32:11 unRAID kernel: mdcmd (13): import 12 Mar 16 15:32:11 unRAID kernel: md: import_slot: 12 missing Mar 16 15:32:11 unRAID kernel: mdcmd (14): import 13 Mar 16 15:32:11 unRAID kernel: md: import_slot: 13 missing Mar 16 15:32:11 unRAID kernel: mdcmd (15): import 14 Mar 16 15:32:11 unRAID kernel: md: import_slot: 14 missing Mar 16 15:32:11 unRAID kernel: mdcmd (16): import 15 sdh 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K2PSAY1U Mar 16 15:32:11 unRAID kernel: md: import disk15: (sdh) WDC_WD40EFRX-68N32N0_WD-WCC7K2PSAY1U size: 3907018532 Mar 16 15:32:11 unRAID kernel: mdcmd (17): import 16 sdc 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K2RK8FFU Mar 16 15:32:11 unRAID kernel: md: import disk16: (sdc) WDC_WD40EFRX-68N32N0_WD-WCC7K2RK8FFU size: 3907018532 Mar 16 15:32:11 unRAID kernel: mdcmd (18): import 17 Mar 16 15:32:11 unRAID kernel: md: import_slot: 17 missing Mar 16 15:32:11 unRAID kernel: mdcmd (19): import 18 Mar 16 15:32:11 unRAID kernel: md: import_slot: 18 missing Mar 16 15:32:11 unRAID kernel: mdcmd (20): import 19 Mar 16 15:32:11 unRAID kernel: md: import_slot: 19 missing Mar 16 15:32:11 unRAID kernel: mdcmd (21): import 20 sdj 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K5SV0HP3 Mar 16 15:32:11 unRAID kernel: md: import disk20: (sdj) WDC_WD40EFRX-68N32N0_WD-WCC7K5SV0HP3 size: 3907018532 Mar 16 15:32:11 unRAID kernel: mdcmd (22): import 21 sdi 64 5860522532 0 WDC_WD60EFRX-68L0BN1_WD-WX71DC8AV0CY Mar 16 15:32:11 unRAID kernel: md: import disk21: (sdi) WDC_WD60EFRX-68L0BN1_WD-WX71DC8AV0CY size: 5860522532 Mar 16 15:32:11 unRAID kernel: mdcmd (23): import 22 sdd 64 3907018532 0 WDC_WD40EFRX-68N32N0_WD-WCC7K0PDA4XL Mar 16 15:32:11 unRAID kernel: md: import disk22: (sdd) WDC_WD40EFRX-68N32N0_WD-WCC7K0PDA4XL size: 3907018532 Also there's an LSI with firmware 20.00.02.00, it should be updated to 20.00.07.00 as all p20 firmwares except the latest one have known issues.

First thing to try is redoing the original flash drive, backup config folder, re-create flash and restore config folder, if that still doesn't work, restore the config folder to a new flash drive and transfer the key.

You can increase the current vdisk(s), assuming there's space available on the underlying device.