-
Content Count
27263 -
Joined
-
Last visited
-
Days Won
87
Content Type
Profiles
Forums
Downloads
Gallery
Bug Reports
Documentation
Landing
Posts posted by trurl
-
-
Your VM problem seems likely unrelated to changing flash.
If possible before rebooting and preferably with the array started
Go to Tools - Diagnostics and attach the complete Diagnostics ZIP file to your NEXT post in this thread. -
Run an extended SMART test on disk2. Also, add SMART attributes 1 and 200 to be monitored on your WD disks.
-
If you have super.dat in the config folder then Unraid will know the disk assignments. The plugins folder contains your docker templates so those will probably work just as they are assuming they are all still there.
Sounds like maybe the go file was missing from config. That is how the webUI gets started.
-
Do you know your disk assignments?
-
The config folder on flash contains everything you need to get going again on a new install. If you didn't have a backup you would have to set things up again but probably most data on your disks should be there.
Unclear what your current situation is, does it boot?
-
post new diagnostics
-
Problems with the flash drive. Put it in your PC and let it checkdisk. Be sure to boot from a USB2 port.
-
1
-
-
Post a screenshot
-
14 hours ago, trurl said:
Your flash backup should have a .key file in the config folder and you need to copy that .key file to the config folder on your new flash
-
no I meant everything, such as the problem you started this thread for
-
I asked in case you wanted to try rebuilding to the same disk. Safest to use another and keep the original in case of problems, but often people don't want to buy another.
Run an extended SMART test on the disk.
-
29 minutes ago, Con said:
I restored my flash back up to another USB. But installing key is not working.
Your flash backup should have a .key file in the config folder and you need to copy that .key file to the config folder on your new flash. Was this a trial key?
-
I think you should reconsider how you are using cache. A 1TB cache should never get full. And making mover run more often will likely just get in the way. Mover is intended for idle time. It is impossible to move from faster cache to slower array as fast as you can write to faster cache, and moving while still writing is going to make things even worse.
I recommend not caching initial data load at all. After that, how much do you really expect to write to your server daily?
If you want more detailed recommendations post your diagnostics.
-
Do you have backups of everything important and irreplaceable?
-
Is everything working currently?
-
Disk3 not responding. Shutdown. Check all connections, power and SATA, both ends, including splitters. Reboot and post new diagnostics.
-
42 minutes ago, 7hr08ik said:
Apart from that I have my other rig, that backs up to there, but thats all SMB
What more can you tell us about that?
-
post new diagnostics
-
Usually in syslog you will see each data disk mount in order, then each pool (cache) mount, then user shares (and user0) mount, then the vdisks for docker.img and libvirt.img mounts.
In your case, after cache mounts, instead of the attempt to mount user shares, you are getting these errors:
Jan 13 16:56:18 Hal-9000 emhttpd: error: get_filesystem_status, 6618: Operation not supported (95): getxattr: /mnt/user/# Backups - Rob
Do you have something that might be trying to access that path before it exists?
-
To change any assignments you have to New Config.
New Config, unassign parity2, assign all other disks as you wish, but make sure all data disks you had before are assigned with none removed and none added. Parity1 will be valid, so check the parity is valid box and start the array.
Then, stop the array, assign parity2, start the array to begin rebuild of parity2.
-
1
-
-
19 minutes ago, dradams said:
Centos7
Is this a VM hosted on Unraid?
-
7 minutes ago, makin said:
Boy, this is like a diary entry again. Last time I also answered my own question. 😅
😁👍
-
When doing New Config, Parity2 is invalid if any data disk assignments are changed in any way, Parity1 is valid as long as no data disks are removed or added.
-
1
-
-
Looks like the problems are on unassigned sdd now. Is everything else working OK?
5 disk array, one disk emulated, another disk with read sector errors at 1.86TB into rebuild. Best course of action?
in General Support
Posted
Should be OK. You have to rebuild parity anyway so might as well do both at once.