-
Posts
16,564 -
Joined
-
Last visited
-
Days Won
65
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by JonathanM
-
-
13 hours ago, Karl Strachan said:
During boot that 1 core is at 100% and boot takes long because - well only one core is used.
You missed my point. If you actually go through with my proposed experiment, you will probably see that boot times are significantly faster with fewer resources bound exclusively to the VM.
Â
Any resources bound to the VM are unavailable for the host, meaning the virtual motherboard that the VM is running is crippled. Slow virtual motherboard = slow I/O = slow boot times, and well as sub-optimal load times as the VM needs to fetch data from the vdisk.
Â
Keep in mind that the CPU usage graph in Unraid includes IOWait, so what you are seeing is the slowness of the data being read from the vdisk into RAM as the guest boots. Give the host more resources so it can feed the VM faster.
-
I've seen controller cards cause it.
-
5 hours ago, shadowlord said:
I want a low-profile one so that it doesn't get physically broken when I'm moving my server around.
Use a full size one and mount it inside the case, that way it can't get misplaced or broken without opening the case.
-
5 hours ago, danielb7390 said:
it correctly powered off when there was 5 minutes remaining.
If the UPS is using typical SLA batteries, draining below 50% capacity regularly will wear them out sooner.
Ideally you should shut down quickly, as soon as you can be sure the power won't come back for several minutes.
https://www.power-sonic.com/wp-content/uploads/2018/12/Technical-Manual.pdf#page=12
-
1
-
-
Reduce the core assignment to a single core, start with the highest number core, and reduce the RAM max to 4GB. Test. Add another core, test. When the VM stops feeling faster with each addition, keep that number of cores and increase RAM by 2GB, test and repeat. VM's typically perform best with much less assigned than seems intuitive.
-
1 minute ago, nrgbistro said:
are there any new config cases where disk data is overwritten, besides the previously mentioned case where I have a parity drive?
Yes, if you define a pool with the "wrong" format and add a disk. If you leave the format type auto it should just work.
-
1
-
-
1 minute ago, nrgbistro said:
I've already done a new config and all my drives are listed as "New Device" now. Is it still safe to add them and start the array if I don't add a parity drive (temporarily, while I make sure my data is still here)?
Yes.
1 minute ago, nrgbistro said:I had an external hard drive added as a pool device for backups.
What format does it have? You should be able to define a new pool and add it just as it was.
-
BTW, ideally you want to use as many of the modular power connections as possible to split the load evenly across as many wires as possible.
-
1 hour ago, mad_dr said:
My PSU is a Corsair RM850x Shift so it has no molex connectors
According to this link https://www.corsair.com/us/en/p/psu/cp-9020252-na/rm850x-shift-80-plus-gold-fully-modular-atx-power-supply-cp-9020252-na
it comes with 2 PATA cables with 4 molex connectors each. It has 5 connectors on the PSU itself, each can take either SATA or PATA cables, so if you order 3 of these,
you can have 20 4 pin molex connectors.
-
1 hour ago, sanfark said:
how would you ensure that all your app data is not lost?
appdata backup plugin
-
1
-
-
You've been doing this tech thing with Unraid for a very long time, relatively speaking. Why not salvage your old hardware and build another Unraid box with used parts? A backup tower would only need to be powered up for the duration of the backup, so heat and power consumption aren't a huge factor. You could use a couple new faster drives in your production box, and move your current smaller drives to the backup unit.
Â
You seem to be focused on the ability to plug the bare drives into a windows box to read natively, but once you add hardware RAID into the mix you lost that already. If the hardware RAID enclosure dies, you would need to source a compatible unit to read the drives. If you run a second Unraid server, the drives are portable to virtually any hardware as you know.
Â
IIRC @Hoopster has something like this set up and running with automatic scripting to do the backups.
-
54 minutes ago, nrgbistro said:
Can I safely add them to my array without losing my data?
As long as parity is not currently installed and valid, yes.
If the array has valid parity added disks will be cleared, which irretrievably erases them.
Tools, new config, preserve all will allow you to add the disks without erasing them and build parity with all the disks.
-
1
-
-
I don't think you can use a vdi directly, I believe it must be converted to a raw image first. After you have a raw image, just define a new VM using the normal GUI and point the primary disk to your image.
-
Please attach your diagnostics zip file as mentioned in the pinned post.
-
Script that checks for the existence of a specifically named file. If that file does not exist, create it. If it does exist, rm -rf. Every time the script runs you need to delete the file.
-
14 hours ago, ZooMass said:
Unplug boot USB and mount the drive on another computer, preferably not Windows because of possible CLRF line ending issues conversions
Theoretically CLRF issues are dealt with automatically, IIRC all system calls to the flash config files are run through the fromdos function.
-
22 hours ago, tucansam said:
Am I going to have to buy a new key?
No, but you will have to contact support to have them manually update the key.
-
2 hours ago, vrytired said:
Did you ever find a solution to this?
Nope, I'm just living with it. The mapping program I use, uNmINeD, gives a permission error for the GUI version, but I can live with that because the CLI version still works fine, and that's what I use on a schedule to generate a webpage for the people using my server.
Â
I'm not happy that the GUI version of the mapping program doesn't work, but it doesn't effect my daily workflow.
Â
There probably is a solution, but I haven't put in the legwork because it works enough for me as is.
-
You have the trial period you can use for 30 days, then you can do the starter subscription for $49. That will give you at least 1 year, probably longer, until you need to pay more for updates. If, at the end of all that, you decide you want lifetime updates, you can change to a lifetime for $209. Total outlay, $258, and only after living with Unraid for much more than a year before you have to make a choice.
Â
So, the "penalty" for not going to lifetime immediately is only $9 net.
Â
Try it out for free, and if it looks good and you want to continue, get the starter license. If at the end of all that, you want to change to lifetime, you aren't spending significantly more than if you fork it all out immediately.
-
1
-
-
You need to ask in the support thread for the specific container you are using, there are several different implementations.
Â
Click on the container icon in Unraid's GUI, and select the support item to get to the correct area.
-
1
-
-
2 minutes ago, gizmo000 said:
binhex please PM me some way that so I can buy you a beer or three
I'll pile on a little. First post of this thread.
Â
-
1
-
-
Keep in mind the slackware version is a moving target, you will likely need to recreate your steps with new versions of Unraid.
-
1 hour ago, dopeytree said:
The path forward is one has to go through each docker 1 by 1 and see which is causing it.Â
Or, if the cause is truly just one container, start roughly half of the containers, check, if the problem is found, start half of the those, if the problem isn't found, start half of the remainder.
Â
Depending on how many items you have to check, elimination by halves can be much quicker than 1 by 1.
-
1
-
-
No, at the moment Unraid only supports LUKS natively. File system level encryption has to be handled manually, which you seem to be doing without issue.
Â
You can certainly look through the feature requests area of the forum, and if it's not already requested, add a topic.
Looking to add additional drives externally.
in Storage Devices and Controllers
Posted
eSATA has strict cable length limits, but can work if each drive has its own eSATA connection. Most eSATA enclosures have a port multiplier instead of individual links, so any operation involving more than one of the disks in the enclosure is going to be severely bandwidth limited. Parity checks would take forever.
Â
USB can be problematic, as Unraid assumes a perfect drive connection and a normal USB reset will cause the drive to be dropped from the array. Also, many USB drive interfaces don't pass SMART data, some even mangle the hardware addressing, causing issues if you later want to move the drive to another connection.
Â
SAS is the only protocol really meant to handle permanently server attached drives that Unraid expects.
Â
There are other issues that I haven't covered with USB.