Community Developer
  • Posts

  • Joined

  • Last visited

  • Days Won


Everything posted by doron

  1. babaa abbab babaa ! Sent from my tracking device using Tapatalk
  2. Quite an elusive issue. My drives are old WD and newer HGST and I don't see that problem at all, neither in 6.9 nor in 6.10-rc1/2. Sent from my tracking device using Tapatalk
  3. Just to clarify, this appears to be unrelated to the plugin, and applies to both SATA and SAS drives. Those drives (mainly Seagates) are spun up soon after being spun down. Seems to be kernel related, though not sure. Sent from my tracking device using Tapatalk
  4. I seem to not be able to reproduce. Can you expand on what was the issue you saw? Can you paste the error here?
  5. Ouch. Shouldn't have happened. Will fix when I get a chance (on the road now). Workaround is to use key files. Place old and new passphrases in key files and do the swap. Mind the ending newline (see doc). Keep the "new" key file safe until you are sure you can unlock interactively! Sent from my tracking device using Tapatalk
  6. You are very welcome - thanks for reporting success.
  7. 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.
  8. 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
  9. 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.
  10. Just installed and everything is looking perfect - thanks again @StevenD! This is awesome.
  11. 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).
  12. 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.
  13. Your unassigned drives will probably find themselves listed in /var/local/emhttp/devs.ini in a similar manner. Good luck!
  14. If you can parse /var/local/emhttp/disks.ini you should be on the right track.
  15. Understood. Thanks for all your good work on this.
  16. 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.
  17. 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?
  18. 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.
  19. Hi @alturismo, thanks for responding! The tvheadend log shows nothing... Two standard messages: "tuning on TurboSight TBS 6281SE DVB-T/T2/C #1..." and "HTTP subscribing on channel...", and then it sort-of works but low traffic and no A/V rendered.
  20. I'm trying to figure out an issue, and I thought the cumulative wisdom on this thread may point me at the right direction. Basic issue is: Can't get DVB-T2 streams from a TBS6281SE card with the TBS-OS drivers. Detailed description: I have a DVB-T/T2 USB dongle. I used it with the libreelec driver package of this plugin. Works well, receives both DVB-T and DVB-T2 streams (I need both). Decided to swap it for a PCIe tuner card (stability, etc.), got a TBS6281SE (dual tuner, based on Si2168/57). The libreelec driver package does not seem to support the card, so I moved to the TBS OS. Card recognized, drivers loaded, so far so good(*). I have a tvheadend setup to use the DVB adapters. Using the exact same network/mux/channel setup that works successfully on the USB dongle, I can properly get all the DVB-T streams (SD), but no DVB-T2 (HD) stream. When I try to start a DVB-T2 stream, the tuner seems to accept the tuning just fine, and start "streaming". However, no audio/video is rendered by the client (vlc, or emby, or tvhclient). When I look at the tvh status/stream page, I can see that the input bandwidth reported is extremely low (for comparison, if the proper DVB-T2 stream that I'm looking for reports a bw of ~5000-7000, here I see it dwindling around ~150). Has anyone seen something like that? Is there maybe a setting that affects the TBS6281SE that I may be missing? Could the driver or fw be at fault? Asking another way - do people with TBS8261SE manage to get DVB-T2 streams (as opposed to DVB-T) from this card? Is the libreelec driver package supposed to work with this card? Lotsa questions. Thanks in advance for any insight/pointer/advice. (*) Incidentally and unrelated, with the TBS OS package, the USB dongle is only partially recognized - the Realtek chip is recognized and comes up, the Sony chips are not.
  21. Right. If in fact the issue is as I guessed above, this exercise should go without issues - as the SAS drive(s) will simply not spin down, hence not invoking this phenomena (unable to automatically wake up from a spin down). Let's discuss this for a moment. The adapter you pointed at is a physical connector adapter; it can connect a SAS drive to SAS-capable(!!) ports having SATA form factor, such as those found e.g. on some Supermicro motherboards. Those ports are not SATA ports; they are SAS ports (in fact, SAS-SATA ports, because they can "speak" SATA protocol as well). No adapter can connect a SAS drive to a SATA-only port. Now, I have been assuming that you use this adapter to connect your SAS drive to a SAS controller that has SATA-style ports. Can you re-confirm that this is indeed the case. Assuming we are indeed talking about SAS ports, you can (a) Stop the array (so as not to cause yet another parity panic) (b) Identify the SAS drive. Let's assume it's /dev/sdX (c) Issue these commands from a command line: sdparm -C sense /dev/sdX sg_start -rp3 /dev/sdX sleep 2 # just in case you are copy/pasting the entire sequence sdparm -C sense /dev/sdX dd if=/dev/sdX of=/dev/null bs=1M count=1 sdparm -C sense /dev/sdX # In case the above command(s) hang,... sg_start -rp1 /dev/sdX sdparm -C sense /dev/sdX Paste the results, and the accompanying syslog lines. If there's anything except smooth run of these commands, suggest you reboot before restarting the array.
  22. You're right. If spinning down your /dev/sdd would trigger a similar issue again, then we'd have to conclude that your drive model - HUS72403CLAR3000 - is one of those which do not properly support the STANDBY command, and, sadly, it will need to be added to the list of "excluded" drive models in the plugin. Net-net it would mean that the plugin will not be of value to you. If you want, you can test for this issue, when the array is quiesced so as not to trigger another parity check. Let me know if you want to try that.