Jump to content

JonathanM

Moderators
View Profile Find content

Posts posted by JonathanM

    Unraid must have direct access to your licensed USB stick.

     

    Running Unraid virtualized is unsupported, it's intended to be run bare metal and used to host VM's, docker containers, and storage pools.

     

    It's not forbidden, you are certainly welcome to experiment with it, but just know that any issues you encounter will need to be demonstrated to happen when running bare metal, as no official support is offered for running Unraid as a VM.

     

    There are plenty of folks virtualizing Unraid, so look around this section of the forum for tips and tricks discovered by other users.

    Normally the docker.img file would be on a pool, not on a parity array disk, and mover should not be attempting to move it. Does that docker.img file exist both on disk1 and on a pool,  /mnt/<poolname>/system/docker/docker.img? If so, only one would be actually in use, so the latest dated file should be kept and the older file should be deleted.

    13 hours ago, Masterwishx said:

    Can we use user script on system shutdown ? only stop array is available (seems also good for it) .. 

    Wanted to save fish-shell history file to boot disk ...

    Why not use the "stop" file? Doesn't exist by default, but if you create a file formatted the same as the go file in the same location (USB boot stick) it will be run on shutdown.

    • Like 1

    22 hours ago, JorgeB said:

    For Seagate drives, you can check to see if the SMART values were clocked with:

      

    smartctl -l farm /dev/sdX

     

    smartmontools 7.4 or higher required, in this case., Unraid 7.0.0+

    Would it be worth adding an automated check with a warning, so people unaware of the situation would get a heads up when they first install said disk in Unraid?

    12 hours ago, Wody said:

    parity can replace any drive, but a data drive is only itself.

    Parity can only replace a drive if all other data drives are good. Parity drives by themselves are worthless, they contain no data. To rebuild a data drive all the other data drives are needed, plus parity.

     

    Consider this scenario.

    2 Parity drives, 10 data drives. For some reason, doesn't matter how for this example, 3 drives die. If all three dead drives are data drives, you just lost all the data on all three drives. If, however, both parity drives died, and only 1 data drive, you only lost that single drive of data.

     

    If data loss is inevitable, as it is when you exceed the failure tolerance of a RAID or Unraid array, only Unraid gives you the opportunity to keep the data on the drives that didn't fail. I'd rather lose the parity drives than the data drives.

    On 2/7/2025 at 9:09 PM, Wody said:

    Keeping parity drives separate on different controllers and different backplanes makes sense for safety,

    Why? I'd rather lose 2 parity drives than 2 data drives. Losing parity means recalculating it from known good data drives, losing data drives means trusting that parity was perfectly in sync when the data drives dropped, which is not always a sure bet.

    15 minutes ago, Braulio Dias Ribeiro said:

    How do I do this on Ubuntu Server? How do I increase the disk partition?

    Assuming you already made the allocation larger and want to expand the partition to fill it, the easiest way is to create a "utility" VM with all your management tools like gparted and such, then add the Ubuntu Server virtual disk as a second disk to the utility VM. Obviously the server VM must not be running while you work on it.

     

    I'm sure there are command line utilities to accomplish it inside the server itself, but it's easier for me to just mount it to another VM.

    On 1/31/2025 at 6:22 PM, kimnach said:

    All, I thank you for your responses.  I may set up another smaller (fewer and larger drives) system and copy files over to it, and then upgrade the current system. 

    Keep in mind that your license key file on your USB stick is still valid for current versions, so what you could do is build your new system, get it running with a trial key, migrate your data, then when you are done with the old system you can use the old key and license with the new install. As long as you make good labeled copies of the USB sticks each time you make changes, we can help you accomplish pretty much any end goal configuration you desire.

    On 1/31/2025 at 6:22 PM, kimnach said:

    Certainly would have been easier with active links.

    I don't think it's fair to expect information from an almost 10 year old thread to still be perfectly valid. Technology has moved a long way since then.

     

    When you get ready to move forward, I recommend you create a new post in the main general support area, briefly outlining where you are and where you want to end up. Include the details of the hardware you are currently using and are willing to purchase for your updated setup.

     

    As JorgeB said, migrating just the license key file and super.dat to a fresh install would be best to accomplish an upgrade. Also keep in mind that the file system used in V5, reiserfs, is no longer being updated, doesn't support very large disks, and is going to be removed in the not too distant future. You will need to copy your data to disks with current filesystems.

     

    Perhaps it would be better to set up a new install with fresh disks, then copy the data from the old drives using the Unassigned Devices plugin.

    10 hours ago, TimTheSettler said:

    To me it's overkill and not worth it

    Opinions vary.

     

    If your budget is limiting, a good backup strategy is more important, but if you can afford it, ECC is an insurance policy.

    • Upvote 3