JonathanM

Moderators
  • Posts

    16069
  • Joined

  • Last visited

  • Days Won

    65

Posts posted by JonathanM

  1. I just thought of a another VERY good reason I want the parity drive to be read all the way to the end.

     

    Hidden errors. Unless you run a complete SMART test, that portion of the parity drive beyond the last data drive is NEVER read or written during normal use. The last thing I want is for there to be a bad sector lurking in the last bit of the parity drive, just waiting for me to add a data drive and start exercising it. At least with a parity check that portion of the drive is read regularly.

     

    Count me as 1 vote to keep the current behaviour, for the above reason alone.

  2. 22 hours ago, thatdude78 said:

    The issue is my back up is a year old. During this period i replaced a failed 3TB HDD with an 18TB HDD plus I also had two parities when this backup was created which my current config did not.

    Just be glad that one of your current data drives wasn't in use as a parity with that old backup. That sort of error is generally fatal to the data that was on said drive.

     

    Lesson here, keep current backups, and delete any old backups made before a drive change. You really don't want to accidentally use an old backup.

  3. 16 hours ago, Gragorg said:

    I agree it should skip the portion after the largest data drive. 

    If that were implemented, it would require a change in the drive addition and replacement code, because it would no longer be a given that the full capacity of the parity drive is indeed zeroes. I don't see that kind of code rewrite happening, mainly because what is there now works, and mucking around with such important code that is currently working would require a VERY strong reason, given the amount of work needed to test for edge cases and general bugs that could be introduced.

    • Upvote 1
  4. 2 minutes ago, VanGoghComplex said:

    my server can also come back on automatically after restoration of of the UPS

    I strongly recommend not doing this. There are many reasons, but the most important in my mind is the need to evaluate the entire situation before allowing the server to come back up. If you are not on site to make that evaluation, there very well may be circumstances that you are not aware.

  5. 8 hours ago, Harlo said:

    there is no real drive there?

    You are checking the emulated drive.

     

    Instead of polluting the plugin support thread, please start a new thread in the general area, include your diagnostics and a link back to your post here so anyone wishing to help can see what's happened so far.

  6. 1 hour ago, Harlo said:

    i have a dead drive that is in my unraid server.

    How do you know it's dead? The majority of the time Unraid fails a drive is because of a cabling or power issue, dead drives are relatively rare. When a write fails, for whatever reason, Unraid disables access and emulates the data using all the rest of the drives.

     

    See if you can get a SMART report on the "dead" drive, and see if it will mount in the Unassigned Devices plugin.

  7. 13 hours ago, ehnde said:

    Simply create a VM in proxmox

    Keep in mind that running Unraid as a VM is not supported, if you have issues it's on you to solve them. It's not forbidden, plenty of people do it, but if you have a problem you will be asked to recreate the problem running Unraid bare metal before it will be considered an actual issue that the developers need to look at.

     

    There is a section of this forum dedicated to users helping each other with virtualizing Unraid.