FrostyOne

Please put warning for filesystem default change when selecting new config in tools, I wiped out my entire array because it did not retain the xfs filesystem that was there and switched to auto. There needs to be a warning to verify file system or verify and keep the one it has instead of going to auto, I missed it and when I formatted the cache pool it erased my drives that were showing auto instead of xfs, now my array is hosed,

Thanks, it rebuilt the 4,5 drives with nothing on them, not a big deal at this point the critical data was on drive 1 anyways, I was able to get 90% of what I had from the trash folder on the other drives before I moved the folder share to 4,5, there's some stuff I lost since the move, but nothing critical mostly psd templates, I do have the original 4,5 drives and will try and get them in as unassigned and see if a fix will work, but won't hold my breath, lol. So once again you live an learn, always keep a current backup separate from the array of the usb drive.

Reset with rebuild usb and added just the lic. I put the drives in the order they were supposed to be except for 4,5 which were replaced wtih two other drives that were slightly larger, all shares data are showing except the one that was on 4,5. It is in process of rebuilding now. I have the original 4,5 disks that were partialy cleared, I tried to access them on linux but not showing, on windows I used disk internals linux reader to see if they would open, showing the drive and partition 1 but won't open.

I appreciate your replies, but you're not really offering any advise other than after the fact, I mean you could have said that don't use a backup on usb drive and instead do xxx to restore data that the array has on it's two parity drives and then when you have all data backed you can try the backup config out. So I guess I'm back to google for a product I paid money for and has zero actual support, I got this because it was easy to set up and I thought it was redundant, if the usb dies and kills the server, this is not redundancy.

From my understanding that unraid cloud is not securely encrypted, so not sure why it is set up that way. Unraid needs redundancy with usb drive, they also need the option to rebuild if it gets hosed, why when the usb drive goes bad it kills the system?

I stopped them clearing right away after I noticed it. So what should I do, reset the usb drive with unraid and do not put a config backup on it? Then set up a new array with the drives in the same order as before and this will restore the array as it was before the usb failed. This usb failure seems like such a problem that there really needs to be somethign added to unraid to prevent this. just assuming people are making manual backups is not enough. Why when the array was running fine and just a usb drive failes it causes such a headache? We should be able to rebuild and replace the usb without taking the array or server down.

Well I put the most recent backup config file on usb drive and booted into unraid, not sure when it 's from. but it's showing everything correct in array except for the two recent drives I added to it. I put them in as disk 4 and 5 and started array, the two drives showed as new and began to clear so I stopped it, I ran parity check but unchecked to write corrections, it immediatly started to pick up errors. I have two drives in parity and three as data drives, I added two ssd disk 4 and 5 and moved a share onto just them. How does the parity work with having put a backup config on unraid disk, If I add back 4,5 and they clear will they rebuild with the data that was on them from the parity drives or do I have to start off from scratch on usb wtihout a backup config and then add drives to array in order they were before?

Ok so I created a new usb drive, should I put one of the backup config folders on it as well or start off from scratch again? Will I be able to get back to my shares and vm's that are set up on the array if I add the disks back in order?

Well it looks like there is no life on the usb drive, it won't checkdisk, it shows up in disk management.

I just put them in an edit, had them on another PC.

Array is still up. I was able to access a vm but cannot access any storage. I found another backup of the flash drive on an external drive I have for redundancy of some data but not sure when it's from. nasp-diagnostics-20220801-1911.zip

What diags would help, I downloaded them but there are a few folders, is there a specific file to post?

Here's a shot of the banner showing flash drive error. Also a shot of a backup I found but it's on a backup that's on the array, lol. I should be able to disconnect that single disk and access it with a sata adapter to my computer correct?

Well I was able to find a backup, idk when it is from exactly. I have made a few changes that I'm not sure are part of this backup. I added a second parity drive, not sure if it is part of the backup or does that matter? I know there are two additional drives I put in the array since this backup, will the licence be part of this file and I just put it on a new drive?

Had server running for couple years, 7 months powered on last stretch before updating to 6.10.3 been running about a week, just signed in to add access to a share and it's saying flashdrive corrupt or offline? 1. Is it possible to just pop in a new flashdrive and import settings to it, if not why? I know it boots from the drive and then it isn't supposed to use it, though some personalized settings in unraid are now gone with the drive like skin colors and vm's not showing. I was under the impression that the drive was loaded into memory on start up and then not accessed? 2. I am still able to sign into the server as I have not taken it offline yet and can get disk assignments, however it is not showing vm's, are they hosed? 3. Although I am able to sign into server, after I noticed the banner about flashdrive all my nas drives are not accessable from computers anymore. 4. If/when this is sorted out and I get another flash drive in there is it possible to setup a dual usb drive boot for redundancy, I can't seem to find info to set this option up and find it odd that for a system that is all about redundancy it does not have that option.