Jump to content

Hoopster

Members
  • Content Count

    1233
  • Joined

  • Last visited

  • Days Won

    4

Everything posted by Hoopster

  1. Hoopster

    M1015 freezing and or BIOS conflict

    You really should post full diagnostics (Tools --> Diagnostics in GUI) as log snippets are usually not helpful as they lack important info. M1015s in IT mode are in use successfully by many unRAID users. I also recommend you change the title of your post to something more descriptive of the issues so the experts don't skip over it in skimming the forums.
  2. Obviously, that is the correct answer 😀 Since it was unclear, I just wanted to make sure it was IT firmware. I don't know why the disks are not appearing, but, your answer eliminates one possibility. Paging the experts.
  3. Just to confirm; did you flash it to IT mode or did you flash it with RAID firmware?
  4. Hoopster

    Weird random Drive Dropping.

    True, With unRAID 5 and prior versions Marvell-based controllers were fine. I had one. It worked without issues. However, ever since unRAID 6.x.x, Marvell controllers started having issues with the latest Linux kernels, drivers, etc. There is no danger in cancelling the parity check. Certainly something is amiss. Your "failed" drives may not have actually been failed drives. If you have controller and/or SATA cable issues, that could account for the problems. UnRAID takes a disk offline when writes fail. That could be a drive issue, but, it could also be a controller or cable issue. As far as how to best proceed with hardware upgrades and restoring the health of your array, I do not want to give any erroneous advice and I am not the expert in these matters. Hopefully, someone else will chime in on the best procedure. I do think your system is recoverable and you likely have not lost any data. The first thing I would do is replace the SATA controllers and get one of the ones I mentioned. There are many of them available on eBay. With the problems you currently have, there is no telling what can be attributed to those controllers. After your disks are "stable" you can consider other hardware upgrades.
  5. Hoopster

    Weird random Drive Dropping.

    I am not an expert on disk issues, that would be @johnnie.black but I do see an explanation for your disks randomly dropping; you have a Marvell SATA controller on your MB and it appears, PCIe SATA controller as well. This is not good as they are known to drop disks with unRAID. Any disk connected to SATA ports (whether those are MB ports or a PCIe HBA) controlled by a Marvell chipset may disappear for no apparent reason. They could be fine for a long time and then just go bye bye until a reboot. 02:00.0 SATA controller [0106]: Marvell Technology Group Ltd. 88SE9172 SATA 6Gb/s Controller [1b4b:9172] (rev 12) Subsystem: Gigabyte Technology Co., Ltd 88SE9172 SATA 6Gb/s Controller [1458:b000] 07:00.0 SATA controller [0106]: Marvell Technology Group Ltd. Device [1b4b:9215] (rev 11) Subsystem: Marvell Technology Group Ltd. Device [1b4b:9215] 08:00.0 SATA controller [0106]: Marvell Technology Group Ltd. Device [1b4b:9215] (rev 11) Subsystem: Marvell Technology Group Ltd. Device [1b4b:9215] Unfortunately, you are playing Russian Roulette with disks attached to these controllers. For peace of mind, the experts here recommend LSI chipset-based controllers flashed to IT mode. There are many recommendations in these forums, but, they include models such as LSI 9207-8i, LSI 9211-8i, IBM M105, Dell PERC H200/H310 and others. You may also wish to verify that your SATA cables and connections are all good. As to your disk failure issues, I defer to the experts to diagnose the issues and the solutions.
  6. Hoopster

    Weird random Drive Dropping.

    The complete diagnostics unRAID compiles and downloads when you go to Tools --> Diagnostics in the GUI.
  7. Hoopster

    Weird random Drive Dropping.

    Post diagnostics. With something like this, the experts will want to to see diagnostics.
  8. LSI SAS2008 is the controller chipset. It is used on many HBAs from many manufacturers, such as LSI 9210-8i/9211-8i, IBM M2015, Dell Perc H200/H310 and others. You should look for the latest firmware for your make and model of HBA. Your motherboard manual will be no help since the HBA is a PCIe add-in card. Your cache drive(s) are apparently connected to it. What is it? As @johnnie.black mentioned, you need to search for legacy drivers on on the Broadcom site. For example I found the 9211-8i 20.00.07.00 firmware there. The 20.00.07.00 firmware is available for flashing in Windows or DOS 20.00.00.00 firmware is available for installation via UEFI, Linux and various other OSes You want to make sure you are flashing in IT mode. IT mode firmware flashing instructions are available in these forums and various other websites.
  9. Hoopster

    [Support] binhex - Plex Pass

    Enabling a tuner for Live TV and DVR is a Plex settings function. There are not ports, paths, variables, etc from the docker side that need to be defined or "exposed." Once you get a Plex Pass docker installed in unRAID, you open the Plex webUI and add your tuner(s). As you can see in the screenshot, I have two. Plex should auto detect your tuner(s). It automatically added the first one and then I manually added the second one by IP address. Caveat: I am using a different Plex docker, but, I don't imagine this setup is any different in Binhex Plex Pass. If it is, I apologize in advance for leading you astray 😀
  10. Hoopster

    Thinking about the E-2186G....

    And now it is priced @ $365.43. They must have figured out their error.
  11. Hoopster

    WD - Easystore 10TB External $179.99

    I used an old credit card. Had the drive out of the enclosure in about 45-60 seconds, no broken tabs. In this post is the video I followed.
  12. Hoopster

    Kernel panics

    Do you have macvlan call traces similar to what Subagon posted? These are almost always the result of docker(s) with a custom IP address. It seems to only affect certain hardware/configurations (mine being one of them). Macvlan call traces do not generally cause kernel panics/server crashes, although from time to time they would lock up my server after several days of semi-frequent call traces. It doesn't really matter to which docker the custom IP address is assigned, but, I had call traces more frequently with Pihole. The solution for me was to create a docker VLAN (br0.3). Assigning IP addresses on this VLAN did not produce call traces whereas I got them frequently on br0. You should post diagnostics and/or screen shots of kernel panics if that is what you are experiencing.
  13. The firmware of your LSI HBA. Latest revision is 20.00.07.00 as johnnie.black indicated
  14. Hoopster

    Plex transcode in Ram

    Just to clear up this point, bonienl is referring to the way you defined TRANS_DIR as a variable and not as a path. You make that selection as the bottom of the docker edit screen when you chose Add another Path, Port, Variable, Label or Device. You defined the mapping as a variable when it should have been a path. For reference, below are some of my Plex host path mappings (note that /transcode is defined as a Container Path whereas in your screen shot TRANS_DIR is defined as a Variable:
  15. Hoopster

    Thinking about the E-2186G....

    Bummer, Provantage still screwed up and their site currently says the price for the 2176G is $336.75. If the site is wrong, they owe you one at that price ASAP. Yeah, that is less than the price they have on the 2174G, but, they have not changed it.
  16. Hoopster

    Thinking about the E-2186G....

    The Provantage site specifies it is an OEM/tray processor; not the retail/boxed with a CPU fan. You (almost) got what you ordered, but, it might not have been what you expected. And yes, you want the 2176G not the 2174G. Provantage owes you, they screwed up! https://www.intel.com/content/www/us/en/support/articles/000029613/processors.html
  17. Hoopster

    Plex transcode in Ram

    It all depends on the host path you specify in the mapping configuration. If you specify a host path such as /mnt/user/.../transcode (or /mnt/cache/.../transcode), you are designating a physical path on the array as the location for transcodes. If you specify /tmp or some other path outside of the array, it will be created in RAM as unRAID loads in RAM on boot. And, by the way, you did not specify the proper container path in the Plex transcoder setup. You entered /config/transcode and that is an incorrect host path not a container path. The container path is TRANS_DIR according to your screen shot. You should map TRANS_DIR to /tmp (or some other temporary directory) if you want transoding in RAM or to /mnt/cache/appdata/plex/transcode (or something similar depending on your setup) if you want transcoding to take place on the cache drive.
  18. Hoopster

    Plex transcode in Ram

    Sure that will work as long as you specify in Plex Transcoder settings that your transcoder temporary directory is TRANS_DIR. It will map to a transcode subdirectory of wherever you have /config mapped on the host (unRAID server)
  19. Hoopster

    Plex transcode in Ram

    That depends on how you map /config in the Plex docker. If your /config mapping is something like the screenshot below (or /mnt/cache/appdata/plex/) and you map /transcode to /config/transcode your transcodes end up in the /mnt/cache/appdata/plex/transcode folder.
  20. Hoopster

    WD - Easystore 10TB External $179.99

    The drive will not be recognized. Here is a good explanation of the issues and the various solutions.
  21. Hoopster

    Issues since 6.5.4 now 6.5.5

    Your cache drive has errors and has been marked read only by BTRFS Nov 15 21:49:24 SUN kernel: BTRFS critical (device sds1): corrupt leaf: root=2 block=1082757414912 slot=131, bad key order, prev (11533745240560926720 7 16777096) current (1082759364608 169 0) Nov 15 21:49:24 SUN kernel: BTRFS: error (device sds1) in __btrfs_free_extent:6953: errno=-5 IO failure Nov 15 21:49:24 SUN kernel: BTRFS info (device sds1): forced readonly Nov 15 21:49:24 SUN kernel: BTRFS: error (device sds1) in btrfs_run_delayed_refs:3057: errno=-5 IO failure Nov 15 21:49:24 SUN root: truncate: cannot open '/mnt/cache/system/docker.img' for writing: Read-only file system Your best bet may be to make a backup copy of the cache drive, format the drive and restore from the backup. This has been suggested in other similar cases by the disk/filesystem experts in the forum.
  22. Hoopster

    WD - Easystore 10TB External $179.99

    I did not need to do the Kapton tape fix as my hot-swap backplane is powered by Molex connectors which completely bypasses any 3.3v SATA power reset issue. The only way to know if it would have been necessary would have been to connect it directly to SATA power for pre-clear but, I did not do that. $155 for an 8TB Red/White drive is a great deal. The white drives in my array are no different from the reds in any way that matters. I would not return it just for the color of the label. I imagine future Red drives will have the same SATA 3.3v reset issue with older power supplies.
  23. Hoopster

    Welcome to Unraid.net

    In case it is not obvious - as is usually the case, someone is squatting on the unraid.com domain in order to "extort" payment to put it to legitimate use. The current owner of the domain is not using it, he just wants Limetech to pay him for it. Lots of desirable commercial domain names have been purchased by people who have no intention of using them, they just want to make money selling them to those who want them.
  24. Hoopster

    Plex transcode in Ram

    Open a terminal session in the GUI, SSH or Telnet into your server or go to your console command line If you have a monitor an keyboard attached to your server and type: cd /tmp/Transcode/Sessions If you list files in that folder you will see the session files for any transcodes in progress. You'll see something like this:
  25. Hoopster

    Plex transcode in Ram

    Your configuration is correct. It doesn't actually load the entire movie into RAM. Transcoding sessions are created a chunk at a time and streamed to the client. You can verify that transcoding is happening in RAM by going to /tmp/Transcode/Sessions on your server. You will see transcoding sessions being created on the fly for each stream that is being transcoded.