Aeonofgods
-
Posts
20 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Aeonofgods
-
-
1 minute ago, johnnie.black said:
You need to copy the data on that disk elsewhere, using e.g. UD, then you can add the disk to the array and have Unraid re-format it.
Ahh ok that makes sense, alright I'll move it over. I'm just hoping my docker containers/settings can come out of all of this mostly unscathed
-
2 minutes ago, johnnie.black said:
Alternately, and likely a better idea, try to mount the disk outside the array with UD, UD doesn't care about the correct partition layout.
Yeah that seems to be the case. I'll mount it, pull what I need, format it, and then add it to the array
1 minute ago, trurl said:So where exactly does preclear fit into this narrative?
When my original drive failed I bought this 2tb drive. From all that I read it seemed as though I needed to preclear the new drive before I did anything with it. Originally it was NTFS but after the preclear UD said it was xfs (and still does).
-
2 minutes ago, trurl said:
Preclear doesn't format a disk, and neither does UD unless you tell it to. After a preclear a disk can't be XFS or any other filesystem
Ahh well I'm an idiot, so what do I do now? Do I start a new config without the new drive, mount it, and move everything from it using Midnight Commander to an external, format it, then put everything back on?
-
Just now, trurl said:
What said it was XFS? Unassigned Devices?
Yeah UD said XFS after I precleared it
-
-
8 minutes ago, trurl said:
I don't think Unraid will clear a disk unless there is parity. There certainly is no reason for it to do so since the whole point of clearing a disk is so parity will remain valid.
Since I do not have a parity drive and there's no rebuild process, how do I get past this? It won't let me start the array with the new one nor assigning no device to that slot
-
3 minutes ago, trurl said:
I don't think Unraid will clear a disk unless there is parity. There certainly is no reason for it to do so since the whole point of clearing a disk is so parity will remain valid.
Ahh ok that makes a lot more sense to me then, thanks!
-
Just now, johnnie.black said:
If there's no parity you can add the drive to the array, it won't be cleared.
Oh alright I'll give that a shot. Thanks for all your help so far I really do appreciate it!
-
16 minutes ago, trurl said:
So did you ever setup a parity drive? Some of the discussion after that really only applies if you have a parity drive. For example, your very next post, and the response it got:
None of that makes any sense unless you do actually have parity.
Also, are you still trying to use USB for any of your array (or cache) disks? The unreliability of USB connections pretty much defeats the purpose of having parity. In fact, USB in an array with parity will likely result in constant rebuilds.
Sorry I will try to clarify. I did not have a parity drive when all of this happened. My 1.5tb external drive failed so I bought a 2tb internal drive to replace it. I used ddrescue to transfer whatever I could from the 1.5tb to the 2tb drives. Now in my array I need to add the 2tb drive, but Unraid will clear it of any data before adding I'm assuming. Since there's no parity drive, there's nothing to rebuild. So I'm moving whatever data that was recovered to yet another external drive, separate from the failed one, so that I can add the 2tb into the array and then transfer the data back on to it. After that I will be adding the 12tb drive I bought for parity. Overall its a very convoluted problem that I could have avoided with having a parity drive. After all of this there will be no more usb drives in the array
-
16 minutes ago, johnnie.black said:
You don't need dockers, you can use midnight commander (mc on the console)
Ahh I did not know that, I'm very new to Unraid. I'm trying it now, I'm going to move the stuff to an external drive, add the new 2tb drive to the array, and then transfer everything back to the new 2tb drive
-
2 minutes ago, johnnie.black said:
Alternatively you can mount it with UD and copy the data to the array.
That was my idea as well, but I don't have any dockers with the failed drive assigned in the array. I'll have to try installing a new Krusader docker and see if I can do it that way
-
7 hours ago, johnnie.black said:
Any drive normally added to Unraid will be either rebuilt (if replacing another one) or cleared (if added to a new slot), so any data there will be deleted, not clear to me if that's what you want, to keep the existing data on an added drive you'd need to no a new config and re-sync parity.
No I would definitely not like for it to be cleared since it was the destination for my ddrescue operation. How am I supposed to get the data from it then?
-
On 2/20/2020 at 10:46 AM, johnnie.black said:
Disk1 is failing, you don't have parity so not possible to do a rebuild, xfs_repair won't normally repair a disk with bad sectors, you can clone with with ddrescue, then run xfs_repair to copy everything you can from it.
P.S. array devices using USB is not recommend.
Hey I just had a followup question. So I bought a 2tb internal drive to copy the data from the failed 1.5tb external drive and i ran ddrescue. Seemingly it went well. I want to unassign the 1.5tb drive and add the 2tb one in it's place, will Unraid clear it before making it usable? Or will it just add it so i can see if the copied data was successful?
-
4 minutes ago, johnnie.black said:
Likely if the Appdata folder is recovered without corruption, you should have a backup of that, look for the CA appdata backup plugin, the docker image itself can be easily recreated.
Alright once I try ddrescue, hopefully it works, then I will make sure to set that up along with a parity drive
-
4 minutes ago, johnnie.black said:
Disk1 is failing, you don't have parity so not possible to do a rebuild, xfs_repair won't normally repair a disk with bad sectors, you can clone with with ddrescue, then run xfs_repair to copy everything you can from it.
P.S. array devices using USB is not recommend.
Yeah it's definitely not an ideal setup at all. I have to get a drive to be able to clone to and give it a try. Would this potentially fix my docker containers as well?
-
So last night I logged into my server to see that there was an error with one of my disks and now it is telling me it has no filesystem and is unmountable. Unfortunately when I saw the error I restarted hoping to fix the problem, so my log file for that drive is empty. All of my docker containers are gone as well and I'm not really sure what to do since I am very new to Unraid. Any suggestions?
-
16 minutes ago, binhex said:
certainly worth a shot, you got nothing to loose at this point, just make sure it is database corruption first, see here Q3:-
https://github.com/binhex/documentation/blob/master/docker/faq/plex.md
I’ll give it a shot, I appreciate the help!
-
13 minutes ago, binhex said:
the fix for database corruption (if this indeed is your issue again) is to upgrade to unraid 6.8.0, unraid 6.7.x caused random sqlite database corruption.
Dang I did not know that, so I still have to delete my database files? I know it was set to back up every day, could I restore from that?
-
Hey I’m hoping you guys can help me out. Plex is no longer functional for me, giving me an error about too many retries and it entered a fatal state. This happened once before and I had to fix it with deleting my database files. I would really like to avoid that this time. Does anyone know of a fix and can I avoid this in the future?
[Support] Linuxserver.io - Radarr
in Docker Containers
Posted · Edited by Aeonofgods
problem fixed
I am having a similar issue after updating to Unraid 6.9
Edit: switching to nightly build and rebooting my system fixed it for me