Boot Volume Degraded Need advice please

[asb2106]

Hi all, real quick intro, FreeNAS newb, linux beginner at best.

Recently moved to a FreeNAS setup at the house for main data storage, and so far its been great. Got a few plugins going even and really enjoying it, however I keep getting failures and even the occasional crash from it.

I installed on a matching pair of SanDisk Cruser flash drives, day 1 went great no problems, day 2 experienced my first failure, but honestly pulling the offending drive, and replacing with a different, it fixed the problem on its own!?

So now, after 4 days of swapping back and forth between 5 different flash drives, all of which have failed at some point, I scooped up some 120gb kingston SSDs on amazon for 35 each, and until they get here tomorrow, i grabbed a 500gb ssd i had laying the office to try and stabilize this for the mean time. I have already copied some 18TB over to the array, so its quite critical at this point!
SO ON TO THE PROBLEM
I replaced an offending drive with the 500gb drive, it said it took, said it was being added, etc..

But its still giving me these errors? What should i do next to repair this? Also, what should i do when my 120s come in, to migrate over to those drives? ALSO, when i try and detach the drive listed as numbers, i just get a failure, ill post the photo below of it.
Any help is GREATLY appreciated! THANKS!

EDIT! da11 is a flash drive the ada0p2 is the 500g ssd

Once i can confirm the 500gb SSD has the OS on it tonight, ill remove all 4 flash drives i have plugged into the system and have it just run the SSD unless anyone thinks thats a bad idea?

Thanks again all!

 

[asb2106]

With the Online status of the ada0p2 (500gb SSD), and da11p2 (Cruser16gb Flash)

would i be safe to assume pulling everything besides the two mentioned above would clean up the unavail numbered drive? Then if i were to pull all flash drives, would that result in a clean boot and a degraded state with only the ada0p2 drive?

Then basically go through this same process tomorrow with the new SSDs?

 

[Stux]

Few things

1) your data is safe.
2) you can backup your config and restore it to a new install
3) you replace a failing boot disk following the instructions in the manual

 

[asb2106]

Few things

1) your data is safe.
2) you can backup your config and restore it to a new install
3) you replace a failing boot disk following the instructions in the manual

Looked in the manual. I'll have to look again it didn't really cover what I thought.

Thanks for assurance.

I do have config backed up just incase.

Waiting on the drives to come in. Everything was humming around fine and now I get a re watchdog timeout error. So overnighted an Intel nic!

Sent from my Pixel 2 XL using Tapatalk

 

[asb2106]

Well, for anyone wondering, I was not able to transition to the new drives off the working system. And now i see why thats totally a waste of my time...

I downloaded the config file to my laptop, ran the iso on the server and installed fresh copy on the new 120s, took 4 minutes, rebooted into the system, restored config (i think took longer than install), and it booted perfectly.

Moral of the story, don't bother trying to transition to new drives and tap dance around it.

If anyone is still reading i would like to pose a question - If I were to move up to a server mobo/proc/ram and move my drives over would this process of restoring a config file work? Or will teh change in hardware not mingle properly?

 

[MrToddsFriends]

If I were to move up to a server mobo/proc/ram and move my drives over would this process of restoring a config file work? Or will teh change in hardware not mingle properly?

Either restoring the config or reusing the boot device(s) does work.
https://forums.freenas.org/index.php?resources/moving-freenas-to-new-hardware.89/