itimpi

There have been occasional reports of slow speeds but the vast majority of people do not see this and get very fast speeds. Suggests it could be something in the network link between you and the Amazon servers that is limiting the speed.

Not sure how easy it is to simulate the physical unplug/plug of USB in software. Are you saying that stopping the USB daemon; waiting a short while for the USB to reset; and then restarting the USB daemon is not sufficient? Feels much simpler than trying to emulate a USB unplug/plug sequence

The files are actually stored on the Amazon AWS servers, not on the Unraid web site so any speed issues are there.

OK. You will need to run a file system check/repair to clear the unmountable state. A rebuild does not clear such a state since all the rebuild does is make a physical drive match the emulated one. The check/repair can be run on the ‘emulated’ disk before a rebuild but since you have already done the rebuild it will happen against the new physical disk.

Sounds as if you may have some sort of problem with your flash drives. Your symptoms are consistent with it not being picked up in the later stages of the boot process, or it having file system corruption. I would suggest plugging it into a PC/Mac and running a check on it. Also, while you are at it if you do have not already done so make a backup in case you need to redo the USB stick for any reason.

I am currently working on the code to allow array operations to be restarted (resumed) from where they were as long as: the array was shutdown cleanly there have been no changes to the disk configuration. I have 2 use cases in mind: Restarting after the system has been rebooted Restarting after the array has been stopped/started without a reboot I would be interested in any feedback on how useful users would find each of the use cases; whether there are any special considerations they can think of for either use case; and also whether there any other use cases I should consider.

This was fixed (( believe) in the most recent plugin update. I have configured my test server to flag PHP warnings by adding the following lines to my 'go' file: logger -tgo "enable showing PHP errors/warnings" echo "display_errors = on" >> /etc/php/php.ini so hopefully in the future I will pick it up such an issue before releasing an update.

Unraid does not support ext4 format drives as part of the array so you would need to copy the data to a drive formatted by Unraid. The Unassigned Devices (UD) plugin allows you to mount ext4 format drives on an Unraid server to facilitate copying the files onto the array. Not sure if the fact that the drives have come from OMV affects this in any way not having tried it myself.

You have to carry out a rebuild of parity to remove the ‘disabled’ state. This can be done by following these steps as documented in the online documentation (accessible via the ‘Manual’ link at the bottom of the Unraid GUI).

It is not quite automatic as you then have to start mover from the Main tab to get the files moved from the array to the cache.

Addresses starting 169.x.x.x are what gets allocated when a DHCP server (normally the router) cannot allocate an IP address. there is still some disconnect here - I would expect the router to have 2 addresses - one in the 192.168.0.x range that is used for the connection to the modem, and another one in the 192.168.50.x range that it presents to all your devices. can you run the Unraid GUI? If so can you get your system’s diagnostics zip file (obtained via Tools->Diagnostics) and attach it to your next post. That would allow us to get a better view of what is happening. just had a thought - if it is very new hardware you may need to use the 6.9.0 beta release to get a driver loaded with support for your NIC so what Unraid release are you running? In particular this is likely to be the case if it is a 2.5Gb capable NIC. Your symptoms could be explained by no driver being loaded for the NIC. Telling is more about the hardware might allow us to give feedback on that.

OK - but still sounds like a network related issue with Unraid unable to access a time server. Some questions: what is the IP address of the router on the Unraid side? What is the gateway address set in Unraid (which should be the router's IP address on the 192.168.50.x subnet). Can you reach the internet at all from Unraid?

The licence is tied to a particular USB drive. You basically have 2 options: Copy the config folder and all bz* type files from the one with the trial licence to the old stick to transfer your settings from the trial stick to the one with the pro licence. Copy the pro key file from the one with the pro licence to the config folder on the trial stick and follow the procedure for transferring the pro licence to the new one (which will end up blacklisting the old one)

CRC errors are very rarely a drive problem as they indicate a connection issue.

That is only true if you have more than one drive in the cache (pool). With a single drive it can be any supported file system.

I would expect these to be on the same subnet (probably 192.168.0.x). How is the Unraid server getting its IP address. Does it have a gateway set to allow it to access the 192.168.0.x subnet? the command you probably want will be 'ifconfig'

Was the parity check ever paused? Unraid only shows the time of the time that the check ran after a pause.

Handling a drive shown as Unmountable is covered here in the online documentation that can be accessed by using the ‘Manual’ link at the bottom of the Unraid GUI. The chances are that you have file system corruption. some questions: Did the drive really fail, or did you assume that it had failed because it had a red ‘x’ in the Unraid GUI. Unraid will disable a drive when a write to it fails and often the drive itself is fine and the write failed for other reasons. do you still have the ‘failed’ drive available if needed for data recovery purposes. did the ‘emulated’ drive show as unmountable before you attempted the rebuild? A rebuild just makes a physical drive match the emulated one, it does not fix any file system errors. were any errors shown in the Unraid GUI during the rebuild process?

Not true. You can have as many gaps as you want. Most people prefer not to have gaps but,Unraid does not enforce this.

Unraid itself is 64-bit and has no support for 32-bit code. A container is whatever the user built it for (and is not necessarily Slackware based).

Yes, the calculations for parity2 includes the drive slot number as one of the input variables while that for parity1 does not.

No. Under Unraid each drive is a discrete file system that (if necessary) can be removed from the array and read on any Linux system.

If the issue is solved you can edit the first post in the thread to add “(SOLVED)” to the title.

Diagnostics definitely show all drives are not mounting. If you do not yet have any data on the array I would suggest you use the format option and see what the results are. It will erase any existing data so do not do this if there should already be data there. It should only take minutes to carry out a format.

That is definitely not correct as there should always be a ‘config’ folder and a ‘syslinux’ folder. Did you take a backup before trying to recreate it - if so you can redo the USB stick and then copy the config folder from the backup.