itimpi

Yes. You would need to temporarily disconnect the 7th drive until the array has been started, although after the array is started you can add in additional drives that are being handled by Unassigned Devices. This would apply any time you reboot the system.

As you noticed, the syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead.

With the current (new?) terminology to get the share moved to the array you would need Primary Storage=Cache, Secondary `storage=Array, and mover direction as Cache->Array.

Docker containers can set their own permissions, so it is not unusual to not be able to access their contents over the network. You WILL be able to access the contents using the Dynamix File Manager that is built into Unraid 7..

No data drive can be larger than the smallest parity drive so you need to use at least 1 of the 8TB drive for parity which will protect against 1 drive failing. You can (optionally) use the second 8TB drive for parity if you want to allow for 2 drives failing at the same time. At that point add the remaking HDD as data drives. The usable space will be the sum of the data drives (less a small amount for file system overhead. You can later add additional data drives up to what your licence allows (your current drives require support for at least 8 drives). If you ever want to use data drives larger than 8TB you would have to upgrade your parity drives to match. The SSD is best used in a pool. This would then typically used for hosting docker containers and/or hosting VMs and/or acting as a write cache to the array data drives It is probably not worth adding the 500GB drives to the main array, although they could well be useful as pool drives if you want multiple pools.

Not quite sure what you mean? You did the following? Stopped the array (if started) Went to Tools->New Config Set Preserve Current Assignments to All Checked “yes, I want to do this” box Clicked the Apply button to actually do the New Config Hit the Done button to return to the main screen At that point you should have all your drives listed with blue icons waiting for you to make changes. At that point you can add/remove drives and reorder existing ones. You would then start the array to commit any changes and rebuild parity based on the drive set currently assigned. If you did all that and got nowhere perhaps you need to supply screenshots so we can see exactly what is happening and where things are going wrong.

That has only set the syslog server into ‘listen’ mode! To get it to actually start recording you either need to set the mirror to Flash option OR put your server IP address into the Remote Server field as mentioned in the link.

The syslog in the diagnostics is the RAM copy and only shows what happened since the reboot. It could be worth enabling the syslog server to get a log that survives a crash/reboot so we can see what happened prior to the reboot. The mirror to flash option is the easiest to set up, but if you are worried about excessive wear on the flash drive you can put your server’s address into the Remote Server field.

After you have done a New Config then the drives should have blue icons. If they do not this suggests you forgot too press the Apply button during the New Config process.

I have some text that I want to set on a <span> element in one of my .page files and use the recommended Unraid variants and I am testing with Unraid 7.2-beta2. I want to use the recommended method of using Unraid specified colours with a fallback colour. I tried using <style "color:blue; color:--orange-500" markdown="1"> but this always comes out as blue rather than the --orange-500 colour I wanted. I checked that I was correctly specifying a fallback colour by using <style "color:"blue; color:orange markdown="1"> and this came out as orange I am obviously doing something wrong and I suspect the answer is going to be obvious when pointed out 😀 For instance do I have to do something special to get the Unraid specified colours to work?

You can have multiple image files per container, and also any image file can be shared between containers so you cannot go by the number you see at the file system level.

yes. Afterwards when you restart the array in normal mode the drive should mount fine. You might want to check if there is now a lost+found folder on the drive which is where the repair process would put any file/folder it finds for which it could not find the directory entry. Not having this folder is a good sign that things went well during the repair.

This is required. No. Normally when you get this then parity also reflects the same file system corruption (unless perhaps you are also showing the disk as disabled and being emulated) . When you run the repair from the GUI then parity is automatically updated accordingly to reflect the repair.

Have you tried the suggested option of trying to mount the original drive with Unassigned Devices? If so what was the result?

You might find that a file recovery program like UFS Explorer on Windows can still recover data from the newly formatted/rebuilt drive. It is not free for actually recover data but does have a free option for checking the drive to show what it thinks is recoverable. I would think trying your get the data of the old drive via Unassigned Devices is your best bet (and the least effort to try).

Unraid treats a 'format' like any other write operation and updates parity to reflect that the format has happened.

You should not need to remove the new disk1 What you are trying to do here is see if the old disk1 can be mounted by the unassigned devices plugin. In your earlier posts you mentioned a drive showing as 'unreadable? This is not a standard Unraid status so did you mean 'Unmountable'? Checking so we can be sure when trying to give advice.

The process is as easy as that. On Unraid 7 you only need to install the Unassigned Devices plugin to handle mounting the drive in the dock. Dynamix File manager to handle the copying is now built in, although you are free to use other copying tools if you prefer.

Unfortunately after a crash there is nothing useful logged as the syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to the problem. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field and log to a share instead. One other thing that occurs to me - have you checked there is no power related issue. A Parity Check is one time the system has all drives active so can be under maximum power draw. There can also be power cabling issues to the drives themselves - particularly if you use Power Splitters to get the required number of connectors.

It might be worth investing in a SATA dock that connects via USB to allow the old drives to be plugged (1 at a time) into the new one. On a different note it is worth pointing out that Unraid (even with parity) is not a substitute to having backups of anything important to you. You should always have backups that are external to the server itself of such material. The Unassigned Devices plugin to handle mounting the external drive in conjunction with the Dynamix File Manager plugin to handle the copying (both built into Unraid 7) would achieve this.

This is a special case where you have 1 data disk and parity1. No other combination allows this.

Sounds as if you should have left the licence key on the flash drive to which it is linked and then obtained a trial key for the new flash drive.

Each server will have its own IP address, so you open two separate browser windows - one for each server. The Unassigned Devices plugin provides facilities for mounting shares from a remote server if you want the two servers being able to see each others shares.

@Carlyj303 As well as diagnostics it could be worth giving the name of a share you think is misbehaving.

OK. You might try giving it much less (i.e something like 8GB) to see if that avoids the issue. I would suggest leaving something like 4GB for the base OS, plus more if you run docker containers. It could also be worth installing the swapfile plugin as that can help if memory fragmentation is aggravating the issue.