Jump to content

JonathanM

Moderators
  • Posts

    16,257
  • Joined

  • Last visited

  • Days Won

    65

Posts posted by JonathanM

  1. 17 minutes ago, DeDude said:

    I dont know why Unraid is using Anti-Cheat/DRM techniques to identify a HDD - just do it with the volume ID maybe?

    Couple factors. Unraid runs in RAM, which effectively means each boot is like a new install. The way linux handles drive identification normally is /dev/sdX or a variant, where each drive that is detected gets the next designation. There are so many things that can change that designation from one boot to the next, and also needing the ability to successfully boot on widely different hardware, the choice was made to identify by something that is supposed to be unique and not modifiable by something written to the drive.

     

    Honestly, this is the first time I remember seeing a spinning rust hard drive not give a unique serial number when attached directly to a compatible SATA controller. Many times USB bridges or controllers can manipulate what is passed to the OS, so that's fairly common to need a plain vanilla SATA connection.

  2. 14 minutes ago, jhughes2466 said:

    This is still happening.

     

    On 1/15/2024 at 9:16 PM, novirium said:

    3 times now I've had new drives seemingly fail to format when adding them to the array.

    Are you the same person? If not, please start your own thread and attach your diagnostics. If this is still you, attach new diagnostics covering the time period when this happens.

     

    17 minutes ago, jhughes2466 said:

    I can clear them / kill the partition, format, and rebuild..

    Rebuild negates all previous actions you listed, the emulated disk includes the format.

  3. 24 minutes ago, Milvus said:

    what exactly does it mean?

    It means recovery from corruption can be impossible with encryption in the way.

     

    Corruption can happen with hardware errors, like bad RAM, cables, or power issues. The problem is, you don't know it's going to happen until it does, and RAID (of any sort, not just Unraid) can't always compensate, meaning unless you have complete backups, you will lose data.

     

    Unraid or any RAID can't help with file deletion or overwriting good data with bad, so backups are always needed, but with encryption, the recovery options are even more limited, so backups are even more necessary.

     

    If the data is important enough to encrypt, it's important enough to keep multiple copies in multiple locations.

  4. 2 hours ago, sannitig said:

    I thought the wiping of the disk was the same as formatting.

    Nope. Wiping the disk writes all zeroes, removing any traces of files or filesystem formats. Think of a format as a filing cabinet with drawers and folders. It allows files to be stored in an organized fashion so they can be easily retrieved, as opposed to just tossing the files on the floor in an empty room. Filesystems take up space even when there aren't any files stored.

    • Like 1
  5. 1 hour ago, cosmickatamari said:

    I've sent Unraid support an email for assistance but wondering how fast are they typically on resolving these issues?

    Did you get an auto reply? If not try sending again.

    1 hour ago, cosmickatamari said:

    the dockers were stored in a /mnt in the array

    Generally containers put their executables and other common program parts inside the docker.img file, and their customizable parts live in ./appdata/* and the templates are on the flash drive. Do you have any backups of the flash drive?

    1 hour ago, cosmickatamari said:

    (the parity drive has NOT changed). But do the other drives need to be listed on the array in that order?

    If you only had a single parity drive in Parity1, then data drive order doesn't matter. If for some reason you had that parity drive in Parity2, then order does matter. The two parity slots use different calculations.

     

  6. 2 hours ago, Getting Goin said:

    zero response

    Pick one app to work on, read the first post in that app's thread and follow the troubleshooting steps. When you have the appropriate log file, read through it and XXXX out any credentials then post it in that app's thread with a description of what you have done so far and where you are getting stuck. Since you say you have the same issue on multiple containers, I'm betting if you fix one, you can easily figure out how to deal with the rest.

  7. 39 minutes ago, stainless_steve said:

    I am at 80% (737GB)

    80% is about 16GB, not 737GB

    On 4/15/2024 at 3:22 PM, stainless_steve said:

    I checked and the docker.img file is just 21.5GB big

     

    20 hours ago, JonathanM said:

    It's the percentage of space used INSIDE the docker.img file. Not the free space on the drive holding the image file.

     

×
×
  • Create New...