trurl

Unraid V7 has Dynamix File Manager built-in.
 
Go to MAIN - Boot Device and click the arrow box icon to the left of flash to browse into the flash drive, and then click on the config folder in that then the shares folder in that, then check the box to the left of MEDIA.cfg and use the DELETE button at the bottom.

Doesn't look like any share has Minimum less than available cache space currently.
 
Did cache get below 100G free during that time?

rootfs is the RAM reserved for the OS files. Filling that can cause lots of problems since the OS has no space left to work in. Also, since it is in RAM, whatever you put there will be gone when you reboot.
 
If a container or something else is writing to a path that isn't actual mounted storage, that path is in rootfs. Most likely you have some container host volume wrong.
 
Mounted storage paths are:
the user shares (/mnt/user/sharename)
the array data disks (/mnt/disk#/sharename)
the pools (/mnt/poolname/sharename)
mounted unassigned devices (/mnt/disks/mountname)
mounted remote shares (/mnt/remotes/mountname).
Or the boot flash drive (/boot). (It is not recommended to write to the boot flash drive.)

Have you tried restarting the array?

And these
Apr 7 13:58:10 MAGI root: Fix Common Problems: Warning: Share appdata set to use pool cache, but files / folders exist on the basic pool Apr 7 13:58:10 MAGI root: Fix Common Problems: Warning: Share backups set to use pool cache, but files / folders exist on the basic pool Apr 7 13:58:10 MAGI root: Fix Common Problems: Warning: Share cloud set to use pool cache, but files / folders exist on the basic pool Apr 7 13:58:10 MAGI root: Fix Common Problems: Warning: Share media set to use pool cache, but files / folders exist on the basic pool Apr 7 13:58:10 MAGI root: Fix Common Problems: Warning: Share media set to use pool cache, but files / folders exist on the storage pool Apr 7 13:58:10 MAGI root: Fix Common Problems: Warning: Share system set to use pool cache, but files / folders exist on the basic pool  
https://docs.unraid.net/unraid-os/manual/shares/user-shares/#primary-and-secondary-storage-unraid-612

Unraid has already determined the drive is unmountable, so you have to use -L

Sorry missed that. It also failed extended test just like the unassigned disk.
 
The procedure you outlined in your first post is wrong. Assuming you intend to replace it with another 4TB disk, here is the correct procedure:
 
https://docs.unraid.net/unraid-os/manual/storage-management/#normal-replacement

Assuming you intend this for a new installation, just make sure you have a copy of config/pro.key to put on the new install.

Looks like something not matching up with your appdata share settings. Put something in the Comments field so it will let you re-save the settings

Not sure what you mean there. You can't delete docker.img with docker enabled.
 
 
 
https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
 
https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
 
 
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

Might be more reliable to copy to something else, install the new SSD, then copy back. A drive taken from a USB enclosure then installed in Unraid might have to be formatted in Unraid before it can be used.

Looks like your static network assignments don't agree with your gateway.
 
Delete or rename config/network.cfg on your flash drive so it will use defaults.
 
Really better if you let your router reserve an IP by MAC address instead of assigning static IP on your server.

Is this from an attached monitor and keyboard?
 
Or when trying to access the webUI from another computer on the network? Maybe a browser issue? Do you have adblocker or anything else that might interfere?

DO NOT FORMAT any disk that has data on it you want to keep.
 
Format is a write operation. It writes an empty filesystem to the disk. This is basically the definition of "format" in any OS.
 
All write operations in the array updates parity at the same time so parity will be in sync. So, after formatting a drive in the array, parity agrees it has an empty filesytem on it, and trying to rebuild at that point can only result in an empty filesytem.
 
Typically, we try to repair unmountable before rebuilding on top of the same disk.That gives more options for recovering data.
 
We will have to check filesystem on the unmountable disk.
 
Attach Diagnostics ZIP to your NEXT post in this thread.

https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself
Or onto a new drive.

SMART for disabled disk2 looks OK. Emulated contents are mounted and have about 1.4T of data so should be OK.
 
None of that will enable a disabled disk. It has to be rebuilt because it is out-of-sync.
https://docs.unraid.net/unraid-os/manual/storage-management/#rebuilding-a-drive-onto-itself
Since you rebooted after the drive became disabled, can't see the cause.
 
 

No, you want appdata, domains, system shares to stay on cache. And those are already all on cache.
Set them to Primary:cache; Secondary:none.
 
The only other shares with files on cache are Media, Music, and Pictures.
Set these shares to Primary:cache; Secondary:array; Mover action:cache->array.

Anything can be bad if it is bad. But good Molex is better than good SATA splitters because it is a tighter connection, can carry more current, and can even avoid the "3.3V" problem because it has none.
 
 
 

Mar 15 14:00:02 Tower move: move: /mnt/cache/data/media/tv-section/anime/I Parry Everything/Season 1/[ToonsHub] I Parry Everything S01E07 1080p AMZN WEB-DL DDP2.0 H.264 (Ore wa Subete wo [Parry] Suru - Gyaku Kanchigai no Sekai Saikyou wa Boukensha ni Naritai, Dual-Audio, Multi-Subs) [1+9] - I.Parry.Everything.S01E07.I.Parry.the.Deadman.1080p.AMZ.nfo File name too long Lots of that sort of thing in your syslog, which probably means a lot of files are stuck on cache.
 
Cache isn't full now though, did you notice if cache had filled up at some point or any other problem with cache?
 
You should set Minimum Free for cache
https://docs.unraid.net/unraid-os/manual/storage-management/#minimum-free-space-for-a-pool
 
And Minimum Free for each of your User Shares
https://docs.unraid.net/unraid-os/manual/shares/user-shares/#minimum-free-space
 
Didn't really see anything else

Also
https://docs.unraid.net/unraid-os/release-notes/7.0.0/#share-secondary-storage-may-be-assigned-to-a-pool
 
So you can move directly from one pool to another.

You shouldn't use root for network access to user shares. root is only for the Unraid webUI and command line.
 

Set data and nextcloud shares to
Primary:cache; Secondary:array; Mover action:cache->array
 
appdata can't be moved until those others have been moved to make room. So for now, set appdata to Secondary:none

https://unraid.net/pricing

If it continues to have crashing
 

rootfs is the RAM reserved for the OS files.
 
The Unraid OS is unpacked from archives on the flash drive into RAM, and the OS runs completely in RAM. Think of it as firmware.
 
If you fill up rootfs, the OS has no space to work in.
 
The actual amount you have used is not all that unusual, but for most users that would be only a few percent of their RAM.