Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


doron last won the day on September 20 2020

doron had the most liked content!



  • Gender

Recent Profile Visitors

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

doron's Achievements


Enthusiast (6/14)



  1. You are very welcome - thanks for reporting success.
  2. Do you see a "SAS Assist" message about spinning the drive down, and then immediately thereafter a message about reading SMART? There was an issue that started in 6.9.2 (vs. 6.9.1), where some drives are spinning down and immediately back up. It seems to be a kernel issue, I'm not sure it's been resolved yet. It was reported against both SAS and SATA drives.
  3. If you get the i/o errors mentioned above on an array drive, the drive will need a reboot to resume operation (the message is not a warning). So, no. Sent from my tracking device using Tapatalk
  4. Indeed, @madejackson and @francishefeng59, unfortunately some SAS drives (mostly reported with Seagates but with some others as well) do not respond as expected to the spin-down (aka STANDBY) command and require an explicit wake-up call, which is not really applicable in the Unraid realm (expected behavior: Spin up automatically upon next i/o). The result is typically an i/o error with sense 0x2 and ASC/ASCQ 0x4/0x11, recoverable only upon a reboot. I've made some attempts to map the bad actors (seems to be drive+controller related) and exclude them, but can't say it was an overwhelming success. So this is where we stand right now.
  5. Just installed and everything is looking perfect - thanks again @StevenD! This is awesome.
  6. The latter might be related to different work profiles (e.g. often-written files or folders on this sdg drive, etc.). To eliminate that I'd swap cables / ports with the other ones and see whether issue stays with dev (i.e. sdg) or with drive (i.e. S/N / Unraid slot).
  7. And nothing else has changed?
  8. It appears as though your drive misbehaves per the spin down process. "LU not ready, intervention required" means it is spun down and does not spin up automatically when an i/o is directed at it. This piece is kind of vaguely defined in the SAS protocols and different drive/ctrl/firmware combos provide different results. Your downgrading to p16 might have something to do with that.
  9. Your unassigned drives will probably find themselves listed in /var/local/emhttp/devs.ini in a similar manner. Good luck!
  10. If you can parse /var/local/emhttp/disks.ini you should be on the right track.
  11. Understood. Thanks for all your good work on this.
  12. If I understand your question correctly, I'd probably try -- Resize the RAID6 array on OMV to ~30TB (need to resize the fs or lv etc. and then the array itself via mdadm - perhaps OMV provides a nice UI for that?) Take 3 of the drives released from the md array plus the spare and build an Unraid array with 1 parity and 3 data drives. Copy the data. Once you're happy with the state of your Unraid server and data, dismiss the OMV system and add the rest of the drives to Unraid. If you specifically want to use 2+1 drives, then you can create an Unraid array with no parity and perform the copy. The downside is, of course, that without a parity drive, your data is not protected.
  13. As I assume you know, the plugin handles SAS drives. I see that some of your drives are SAS and some are SATA. Can you indicate which of your drives you are having an issue with?
  14. Thanks! Turns out things messed up further with all the back and forth and now I can't get the HD channels on either the PCI or the USB tuners. I'm beginning to suspect something is going on with the DVB-T2 provider(!). They have a reputation of malfunctions... will keep working on that.