jonathanm

Moderators
  • Content Count

    12197
  • Joined

  • Last visited

  • Days Won

    53

jonathanm last won the day on June 29

jonathanm had the most liked content!

Community Reputation

1408 Hero

About jonathanm

  • Rank
    unAdvanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Agreed, out of band management is a must, but that doesn't remove the need to use a physical USB stick for Unraid. Most server grade boards include some form of IPMI so adding an external solution like PiKVM is only needed when using consumer desktop grade parts. If you are choosing parts to buy and not using an existing build, it makes sense to pick a board with IPMI built in rather than fussing with adding it later.
  2. Not precisely. If any TWO of the main drives fail they can be emulated and rebuilt. Parity encompasses all the drives, it requires the remaining drives to emulate the missing drives.
  3. Stock Unraid does not support sleep. Did you add a plugin to enable it?
  4. Depends on the quality of the PSU. Wattage doesn't tell nearly the whole story. If you are talking normal consumer grade power supplies, I would be very worried about even a 500W rated unit with 8 3.5 drives and 4 2.5 drives.
  5. Strange. I tested 2 different Unraid servers, one on my same local subnet, one across the WAN, both responded instantly.
  6. How did you come to this conclusion? I just tested it by putting the name of my Unraid server in the ntp server box for one of my windows laptops, and it synchronized just fine. With the appropriate firewall rule in place, it works over WAN as well.
  7. See title of this thread.
  8. Using it as a drive in a typical non - RAID windows system it would possibly be ok. The issue is in Unraid, every bit of every drive is valuable, as it will be used to rebuild a failed drive. All drives in the Unraid parity array must work perfectly, you can't afford to trust a drive with even seemingly minor issues. I wouldn't RMA it, I would straight up return it for a refund and get another.
  9. sdX designations are subject to change on reboot, so don't rely on them. Any changes will need to be scripted, and run either from the go file or using the User Scripts plugin scheduled on array start.
  10. I recommend looking up Spaceinvader One's videos on youtube, he has several on VM's as well as pretty much any other Unraid topic.
  11. It's been too long since I spun up a box stock version, but I think the monthly schedule is there by default, in any case it's easy to do. There is a plugin to handle more complex scheduling, like pausing the check and resuming at specific times to minimize impact, or other triggers.
  12. Most people schedule parity checks once a month, a parity check reads every bit of every drive in the parity array and confirms the parity calculation.
  13. When a drive fails a read request, all the rest of the drives are read, the failed read request is fulfilled from the resulting parity calculation, and that data is written back to the drive that failed the read request. If that write fails, then the drive is marked as invalid (red X) and the parity calculations are used for all further I/O to that drive slot, the physical drive is no longer accessed. That is the total extent of what Unraid does by default, anything beyond that would need to be handled by recovery from backups.
  14. You should attach the photo and your diagnostics zip file to your next post in this thread. No need to link to outside sites.