trurl
-
Posts
43900 -
Joined
-
Last visited
-
Days Won
137
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by trurl
-
-
On 1/13/2019 at 2:58 AM, codo1234 said:
what now?
Replace old parity with new parity disk, assign new parity, and start array to build parity on the new parity disk.
-
No problem, @Newbie. That is your name, right?
-
You're still having ethernet problems. Maybe a bad port somewhere.
Not related, but please upgrade your Unraid. You're may get incompatible plugins running such an old version, newer versions have some fixes, and the diagnostics you are posting don't have as much information as later versions.
-
Also, Unraid will need to format any disk it uses in the parity array or as cache.
-
17 minutes ago, Danuel said:
like will unraid run with my CPU ?
Unraid will run on any 64bit CPU that supports linux, so I would assume so.
18 minutes ago, Danuel said:can i adopt same method on unraid ? meaning i would like that 2 HDD that i use for media to be able to sync (reason for not wanting to have a mirrow rais is in case of a HDD coruption)
Unraid is not RAID. Each data disk is independent, with an optional (recommended), independent parity disk.
19 minutes ago, Danuel said:can i use my 500 GB just for downloads and the 150 NVME for applications ?
Yes.
For those disks, the usual method would be to put a 3TB as parity, and the other 3TB and 500GB as data disks in the parity array, with the NVME in a cache slot for your applications to use. Probably not enough capacity for that NVME to be useful for caching user shares, but should be fine for just apps.
-
Put flash in PC and let it checkdisk, then try another USB port on your server, preferably USB2.
-
47 minutes ago, severanced said:
I'm trying to reinstall my key and I keep getting "ERROR (1)" when I try to install it so I can replace the key.
How are you trying to reinstall it and where are you seeing this error?
Just copy the .key file to the config folder on flash.
-
12 minutes ago, careyc said:
I think so. The two hard drives that failed are not detected by another computer, when I plug them in they both make a click kind of noise. I am going to see if I can mount the remaining two working drives on my Windows computer as there really is only a couple of folders that are needed and if the files exist on the two existing drives I am OK.
Windows can't read Unraid filesystems.
You can make a new array in Unraid with the good disks. Tools - New Config, assign disks as you want making sure you don't assign a data drive to the parity slot. Don't check parity valid box, don't check Format box if it appears, and start array to rebuild parity.
-
Close all browsers you have open to your server on all devices and try with just one browser, clear its browser cache, and see if the webUI will come up.
Of course you won't be able to see any shares on the network since you haven't assigned any disks yet.
-
1 hour ago, Squid said:
pull the flash drive and upload the file from another computer (its in the logs folder)
-
4 minutes ago, chris_netsmart said:
So what you are saying is that it is normal for disk1 to be spinning ? And it will only sping down when, none of the dockers are updating.
No I am saying that you should get your system share on cache if you want disk1 to spin down.
Disable docker service, set system share to cache-prefer, run mover. When finished, enable docker service.
-
13 hours ago, codo1234 said:
@trurl so, the parity check completed
Duration: 15 hours, 31 minutes, 32 seconds. Average speed: 71.6 MB/sec
You left out the important part of your parity check results.
-
If you aren't using VMs then isos share doesn't matter and it is empty anyway. You should delete the empty appdata folder on disk1.
system share exists only on disk1, it isn't empty and that is probably where you have it set to put your docker image, which is where the actual code for each of your containers resides.
-
43 minutes ago, Einzigstes said:
This option will delete the image?
yes. Please attach to your post instead of linking to external sites.
44 minutes ago, Einzigstes said:How exactly can I see if there's something left of the dockers?
At the terminal
ls -lah /mnt/cache/system
ls -lah /mnt/disk2/system
Also, please upgrade your Unraid version. Diagnostics has improved since the version you have and there have been some other fixes.
-
3 hours ago, Einzigstes said:
I now backed everything up and added the hdd to the array.
I ordered a 500GB ssd for the cache pool. When this arrives I will reinstall all my dockers to the cache pool only.
When Installing a new docker, will the "cache-only" setting in the appdata share be enough for the docker do just be in the cache pool or will I sometimes have to change paths manually before installing the docker?
appdata is currently all on cache as seen above and since that share is set to cache-only, that is the only place new files will be written.
But system is set to cache-yes which means it will be moved to the array, and as also seen above there is likely a duplicate docker image on disk2. The system share should be set to cache-only also, your docker image deleted (from Settings - Docker), and from the other disk if it is still there. Then you can recreate your docker image and go to Apps - Previous Apps to add them back.
-
1 minute ago, fmp4m said:
Hello,
I am running UR: 6.6.6 and attempted to update "Dynamix System Statistics" and received the following error:
plugin: updating: dynamix.system.stats.plg
plugin: installed Unraid version is too low, require at least version 6.7.0-rc0iI was unable to locate a ver 6.7.0 (and quite frankly would love to get off 6.6.6 but even RC shows 6.6.0-RC4 to me.).
Is this a bug or am I missing a RC release somehow?
Several reports of this, including just 2 posts up from yours on this thread. Apparently that update of the plugin must wait on the new release, which is anticipated.
-
1 hour ago, careyc said:
Does Unraid write complete files to a single disk or can it split it up between multiple drives?
As jonathanm said.
The way Unraid spans drives is by allowing top level folders (user shares) to exist on multiple disks. So if you access a user share, the folders may be coming from multiple disks, but each file in a folder is completely on a single disk.
So have you worked out how to proceed with your problem?
-
Probably not much you can do but reboot. The OS will unpack fresh from the flash drive (assuming you didn't lose the stuff on flash yet). Then you can take a look and see how far it got with your data. Maybe little if any permanent damage if you stopped it quickly.
Do you have a backup of flash? Do you have a backup of any important and irreplaceable data? You should have both.
-
Maybe pretty obvious question, but just in case. Is your phone on the same LAN?
-
1
-
-
Also your Unraid version is extremely out-of-date and many plugins may not work with that version.
-
With one parity you can only have one missing or disabled disk. Only one disk can be rebuilt and it requires parity PLUS all other disks to rebuild. Parity by itself can't do anything. If you're trying to replace disk1 then you will have to have disk4 and all the others.
-
14 minutes ago, hoosierdaddy said:
I am running Unraid 6.4.0.
Out-of-date Unraid plus out-of-date plugins is the likely cause.
-
31 minutes ago, trurl said:
Are all these computers on the same subnet?
-
1
-
-
41 minutes ago, wgstarks said:
This usually happens because of a difference in your container paths on the various dockers. Deluge is mapped to /data unless you changed it. That means that Sonarr, Radarr, etc must also have a /data mapping. If you post your docker run commands people can check your mappings. Be sure to redact passwords.
His mappings are in the screenshot
"Stopped. Invalid configuration" after replacing failed drives
in General Support
Posted
New Config doesn't do anything at all to your data disks. It only lets you change their assignments and (optionally) rebuild parity. I assume you did let it rebuild parity since it would be invalid without those other disks. After a rebuild, whether parity or data, I always recommend a non-correcting parity check to confirm.