itimpi
-
Posts
19611 -
Joined
-
Last visited
-
Days Won
54
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by itimpi
-
-
2 hours ago, MartynK said:
This must be an issue with the order that the USB disks are found at the hardware level.
I find that if I reboot, normally once, but sometimes twice, everything just works perfectly, all the disks are found in the right order etc.
its a shame this cannot be fixed somehow as using USB enclosures for low throughput needs are a cheap solution with Unraid.
This is not an issue if the USB enclosure passes the drive serial numbers through to Unraid as that is the way that Unraid identifies drives, not by the order in which they initialise.
-
You could simply rename the folder under the appdata share and edit the container settings accordingly. There should be no need to copy the folder in that case. You can use the Dynamix File Manager to do the rename.
-
Rebuilding a drive will not clear an unmountable status. The procedure for this is covered here in the online documentation accessible via the ‘Manual’ link at the bottom of the GUI or the DOCS link at the top of each forum page.
-
57 minutes ago, Milvus said:
In the manual to UNRAID I saw that it is not necessarily recommended to use an encryption. Why ist that?
The problem with using encryption is that if you end up with file system level corruption then encryption can compromise recovery processes so it then becomes critical that you have a good (and tested) backup strategy in place.
-
No, it is always based on the number of folders in the files path.
-
You can use something like UFS Explorer on Windows to do this.
-
1 hour ago, dabbo said:
Yeah I already have another backup for my important files. I'm fine with doing it manually using a script but do you have somewhere I can start? A guide or something to setting up scripts on the server? Thanks
The User Scripts plugin can be used to initiate the scripts on a selected schedule for devices permanently available. Alternatively the Unassigned Devices plugin allows you trigger a script when a particular drive is plugged in.
The content of the script will depend on exactly you want to copy and to where.
-
1 minute ago, suedenimes said:
Do I need to reboot or anything like that?
I would think so to clear out the old syslog (held in RAM and restarted after each boot). Not sure it will clear the problem though.
-
51 minutes ago, RobF285 said:
know i am going to need to upload a diagnostic file but i can't see anywhere to do that? How do i/we/you normally go about it?
You get the zip file via Tools->Diagnostics
FYI: You will often see certain phrases in forum posts (such as the word diagnostics) underlined that are a link to the relevant instructions in the online documentation.
-
You want Secure Boot to be disabled. You do not need it just because you are using UEFI boot and Unraid does not support it anyway.
I would think you could also enable Legacy USB support and CSM support. This would give you the option of alternatively booting in legacy mode (but does not stop UEFI boot). Not sure if it helps in any other way.
-
7 hours ago, ib134866 said:
I have contacted support twice about this issue with about two weeks between requests, but I have never received acknowledgement or a reply.
Which method did you use? Going via the contact support form seems to work reliably but other routes are less reliable for some reason. If you did not get the automated acknowledgement then the request almost certainly did not get through.
If necessary/easier you can do a manual upgrade to 6.12.10 by following the procedure documented here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI.
-
You can do a manual upgrade to the current 6.12.10 release by following the procedure documented here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom. The Unraid OS->Manual section covers most aspects of the current Unraid release.
Having done that the purchase option should now work. If you still encounter problems you will need to contact support as they handle all licencing issues.
-
It is always possible that disk7 is not really dead as the fact it is disabled simply means a write to it failed. This can be caused by external factors such as cabling or power. It is not showing up in the SMART information in the diagnostics so at the very least it is currently offline. Have you taken any action to confirm it is dead?
@JorgeB mentioned using ddrescue with the parity drive. It might also be possible to do it with the disabled drive as an alternative way of recovering its data. I have succeeded in the past with ddrescue on drives that would fail their smart TESTS. Regardless I would keep both of those drives intact until one of the approaches has worked to maximise recovery chances.
-
7 hours ago, Laov said:
From what is the Nth level calculated? Is it from the File being written? Or from the Share base?
The top level is the Share name (which maps onto a folder at the disk level). Each additional folder in the files path adds another potential level.
Looking at your examples you would need '2' to keep all of Breaking Bad on the same drive or '3' if you are happy for each season to potentially be on a different drive.
Your second example has an extra folder in the path so not sure what you want to keep together there?
-
13 hours ago, suedenimes said:
can see it at /boot/config/share.cfg
That is the location from within Unraid (/boot is where the flash drive is mounted).
If you have the Dynamix File Manager plugin installed then it has built-in capability to view/edit such files which might be the easiest way to do it.
-
1
-
-
8 hours ago, Fluxonium said:
not sure why this worked as i thought jumbo packets are normally not required.
They should not be, and often cause problems.
Your initial results suggest at that point you might be getting a 10Gb link in one direction and something like 2.5Gb in the other.
-
1 minute ago, RoyBatty said:
Atm Im a bit stuck with deciding what to do, should I cancel the disk clear, stop the array and remove the faulty drive? Would that increase the speed of adding drive 3?
I would certainly recommend removing stopping the array as with disk4 playing up it will take forever 😞
It is your choice as to whether you want to try and resolve why disk4 is having issues or initially just get disk3 up and running? It is possible that disk4 just has a cabling issue (power or SATA) and the drive is physically OK.
-
Not without some sort of custom script to handle this. Normally it the job of parity to provide some level of hardware redundancy.
Having said that you should still be backing up critical files elsewhere off the server as even parity does not protect against certain types of errors that can result in lost files.
-
5 minutes ago, flowermoron said:
CPU is barely doing anything, but one thing I noticed was that yesterday it crashed at the same time of day, right when I booted up my PC.
I have GoodSync installed on my PC (synchronization app), and the moment it started working the server crashed.
Maybe it's just a coincidence?
That might suggest a PSU overload issue when the server tries to spin up all drives simultaneously? What PSU do you have?
Since you have not provided the diagnostics for us to look there perhaps more information about your configuration would help.
-
1
-
-
Do you mean pre-clear (which happens before you add a drive to the array) of Clear which is what Unraid does by default when adding a new drive if it was not previously pre-cleared? There is a discussion of the difference here in the online documentation accessible via the Manual link at the bottom of the Unraid GUI. In addition every forum page has a DOCS link at the top and a Documentation link at the bottom.
I am guessing from the diagnostics that you mean Clear on disk4? If that is the case you are getting lots of write errors and resets on that drive and in the diagnostics and it appears to have gone offline. I would suspect a cabling issue (power or SATA) but it could be the drive itself but as it is offline we cannot see any SMART information. You will almost certainly have to power-cycle the server to get that drive back online.
-
Did not spot anything obvious in the diagnostics.
The syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field.
-
1 minute ago, flowermoron said:
t goes 'click' and it quickly boots up, but i always get a parity check.
That will almost certainly be hardware related (in which case there is nothing in the log). I looked and could not spot anything.
The most likely culprits would be PSU not coping with the load or something thermal like the CPU overheating.
-
1
-
-
4 hours ago, thearttist said:
here is my scheduled settings
Those look fine from a scheduling perspective.
We do normal, however, recommend that the automatic scheduled checks are set to be non-correcting so that if you have a drive playing up it does not end up corrupting parity before you realise there might be an issue. Then it is only the manual checks that are set as correcting after you have fixed any hardware related issues that might have caused parity to be partly invalid in the first place.
4 hours ago, thearttist said:Im not sure how to get into the flash drive logs
You can get to the flash drive by clicking on the Boot device on the Main tab. If you want it to be visible over the network (by default it is not) then you need to set the SMB settings to allow this (in which case if shows up as the 'flash' share.
-
The log you mention is missing!
Having said that the syslog in the diagnostics is the RAM version that starts afresh every time the system is booted. You should enable the syslog server (probably with the option to Mirror to Flash set) to get a syslog that survives a reboot so we can see what leads up to a crash. The mirror to flash option is the easiest to set up (and if used the file is then automatically included in any diagnostics), but if you are worried about excessive wear on the flash drive you can put your server's address into the remote server field.
When you say 'rebooting' to you mean it actually reboots by itself or do you mean it 'freezes' and you have to manually force a reboot? Asking because if it spontaneously reboots this suggests a hardware issue.
-
1
-
USB drive died - have to recover/start over - have some questions...
in General Support
Posted
This is one of those things that seem to be highly variable. Some seem to to get failure in months, while others get many years - 10 years being reported.
What does seem to help is getting USB2 drives (I suspect because they typically run cooler than USB3 ones) if you can find them nowadays. Also ones with metal casings can help with heat dissipation. Having said that I have some nano form factor ones that I have been using for years and they are too small to have much cooling.
Sounds as if you definitely want to get an automated backup of the flash drive in place going forward. The two standard ways of achieving this are:
There is still the manual backup method of clicking on the boot drive on the Main tab and selecting the backup option from there.