itimpi

It was always possible to go greater than 32GB but you used to have to use 3rd party tools to handle formatting such drives as Windows used to be limited to a max of 32GB for FAT32 formatting. Interestingly even now using a tool such as Rufus to handle the formatting solves boot issues for some people regardless of drive size.

Do you mean quite this? I would normally expect a single PSU cable to have either Molex or SATA connectors on it (not both) and the PSU to not have included Molex->SATA adapters. A cautionary word - II your PSU is a modular one make sure you use compatible cables. There is no standard for modular supply cables (even for different models from the same manufacturer), and getting the wrong one for your PSU can result in fried drive electronics.

You CAN do that, but you would lose all current contents. Using 2 pools was suggested as then the contents can remain intact so you only need to modify the container paths.

Do not forget that as you have a legacy Basic Licence you still have the option to upgrade to the legacy Plus licence (allowing up to 12 attached drives). Still not cheap but a lot less than switching to the new model.

They might well cause a problem. We tend to never recommend splitting a SATA power connection more than 2-way due to the limited current the SATA connection can carry. If you use Molex->SATA splitters you can normally get away with a 4-way split without issues as the Molex connector is more robust.

The syslog is reporting file system issues on the ‘cache’ pool so it has probably being mounted read-only as a result. You should run a scrub on the pool to see what files have errors. Hopefully that will help, or at least give more information. Also worth considering running a memtest (available from the Unraid boot menu) as the commonest cause of file system corruption seems to be RAM related issues.

Discord was incorrect. A parity rebuild is only required if adding a new parity drive or replacing a parity drive. Simply removing parity1 and restarting the array will bring up the array protected by parity2 against a single drive failure.

It was a requirement in earlier Unraid releases. The ability to use only pools and have no main array was new with Unraid 7 so probably the post was referring to a workaround for an older release.

Good to hear you have a backup so recovery should be relatively painless. I think that an upgrade is one time that a considerable amount of data (I think around 800MB with latest Unraid release) is written to the flash drive so making it more likely to push a borderline drive over the edge.

Unfortunately that suggests an issue with the flash drive as is in FAT32 format which is something Windows should have no problems with.

The screenshot definitely shows an issue with reading the flash drive. I would suggest downloading the zip file for the release and then extracting all the bz* type files overwriting the ones in the root of the flash drive. That often seems to help with this type of error happening just after an upgrade. If that does not help you may have a genuine issue with the flash drive. While doing the action mentioned above I would recommend taking the opportunity to also make a backup of the ‘config’ folder from the flash drive as that contains all your configuration information.

If you are not interested in redundancy then you can run the main Unraid array with no parity drive and the full capacity of the data drives is available so that is one option. It has the advantage that each drive is an independent file system so if a drive fails only the contents of the failed drive are lost. With the current Unraid release you can use only pools - there is no need to have the main array if you do not want it.. I would suggest you do: use the Tools->New config tool to reset the array (do not forget to hit the Apply button). Set the number of slots for the main array to 0. This must be done if you are not going to have any dtives in the main array. Create a new pool with 2 slots and assign drives to the pool. Start the array to commit the changes. Note that by default multiple drive pools are set to provide redundancy and then with the drives you have only the size of the smallest drive is available. However as long as you are prepared to run without redundancy you can use BTRFS as the file system and run without redundancy a non-redundant profile to make all the space available.

The syslog should show whether the Parity Check plugin is pausing the sync (and why). You can turn off the options causing the pause in the plugins settings. If they are temperature related you could also set temperature related pauses to occur at a higher temperature than you currently have set.

That sounds as if you may have failed to hit the Apply button to actually execute the New Config (this is a not uncommon error). If it has been run correctly then the drives will have a blue icon when you return to the Main tab.

You might want to try using the manual setup method but using Rufus to handle the formatting to FAT32. That seems to work for some people.

Your syslog show a docker container continually crashing and being restarted. You can probably work out which one it is by looking at the uptime on the dockers tab.

Have you rebooted since installing the key?

The only errors I see are CRC errors, and these are not drive issues, but connection issues (typically related to power or SATA cabling). Occasional CRC errors are not an issue as they merely trigger a retry of a transfer. Note the CRC count never resets to 0 - you can only stop it from increasing. If you click on the orange icon against the drive on the dashboard and select the ‘acknowledge’ option from the menu displayed then Unraid will only notify you again if the count increases.

Unraid needs to be installed to the USB key - not to a SSD. The diagnostics show UNraid is looking for the USB key and failing to find it. The instructions only talk about doing a manual install to a flash drive.

You CAN have just pool(s) - the array is now optional. Your answer implies otherwise as that was the OP question although it does actually say this (just not very clearly).

Not quite sure what you mean? You need to be below the limit specified at the point a new file is first created before overflow starts happening.

You might want to make the share settings match its location: p--------n shareUseCache="no" # Share exists on cache

The Docker Safe New Permission is not part of standard Unraid. It is added (I think) by the Fix Common Problems plugin.

Your question is the wrong way around! This will only be happening if you have actually configured something to use the flash drive.

According to the diagnostics it looks like it is a 10TB HDD. As to whether the drive is hot enough to pause a check, that is up to the user to decide and to set the temperature that should trigger a pause (although I agree that the chosen value seems lower than one might commonly expect).