Jump to content

Simon

Members
  • Content Count

    133
  • Joined

  • Last visited

Community Reputation

10 Good

About Simon

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

  1. So I created a 8GB RAM disk under /tmp/, set Plex to use it and kicked off a 4K movie in a Web Browser to ensure it was Transcoding. Monitoring the directory I saw it grow to 100% usage (about an hour into the movie) and then it emptied itself and has started growing again. I assume (dangerous I know) that it will continue doing this and that multiple transcoding streams will just cause this to happen sooner. I'll leave it like this for a while and monitor. Edit: Kicked off two transcoding streams (from 4K, which I'm impressed my system managed - see attached image) and my observation was that the usage grew to 8GB (100%) and then dropped to 4GB (50%). So it seems Plex might be dividing the available transcode space evenly between jobs and purging history once they fill their "allowance".
  2. I'm playing around with this on my setup. I notice the Plex support site says: Wouldn't that be way more than 4GB?
  3. I also just ran the Enable Testing (just for debugging) option with the latest Plugin (2019.11.27) and it finished fine. Thanks @gfjardim !
  4. My 10TB cleared successfully using the Docker plugin.
  5. My 10TB Seagate failed in the same manner again. I'm going to try the Docker preclear and will report back...
  6. edit: So I figured out the below is a partition. I tried deleting it using Unassigned Devices in destructive mode, but it didn't remove it. So I removed it using fdisk and confirmed it was no longer showing in the UI. I've tried kicking off another preclear run to see if it makes a difference. Possibly related? This is the only disk I've ever noticed a 'child' dropdown for in Unassigned Devices. It's a shucked Seagate drive.
  7. Doh. Thanks. I thought I had, but had this open from searching for a solution, so must have had the wrong browser tab 🙂
  8. Using plugin version 2019.11.22, I just tried to preclear a 10tb and it failed with: ############################################################################################################################ unRAID Server Preclear of disk ZA2XXXXX # # Cycle 1 of 2, partition start on sector 64. # # Step 1 of 5 - Verifying unRAID's Preclear signature: FAIL # # Step 2 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 3 of 5 - Zeroing the disk: [14:40:54 @ 189 MB/s] SUCCESS # # Step 4 of 5 - Pre-read verification: [14:43:57 @ 188 MB/s] SUCCESS # ############################################################################################################################ # Cycle elapsed time: 29:24:54 | Total elapsed time: 29:24:54 # ############################################################################################################################ ############################################################################################################################ # # S.M.A.R.T. Status (device type: default) # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 0 - # # 184-End-to-End_Error 0 - # # 187-Reported_Uncorrect 0 - # # 190-Airflow_Temperature_Cel 21 - # # 197-Current_Pending_Sector 0 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 0 - # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> FAIL: unRAID's Preclear signature not valid. Anything useful I can provide? preclear.disk.log
  9. Using plugin version 2019.11.22, I just tried to preclear a 10tb and it failed with: unRAID's signature on the MBR failed - Aborted ############################################################################################################################ unRAID Server Preclear of disk ZA2XXXXX # # Cycle 1 of 2, partition start on sector 64. # # Step 1 of 5 - Verifying unRAID's Preclear signature: FAIL # # Step 2 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 3 of 5 - Zeroing the disk: [14:40:54 @ 189 MB/s] SUCCESS # # Step 4 of 5 - Pre-read verification: [14:43:57 @ 188 MB/s] SUCCESS # ############################################################################################################################ # Cycle elapsed time: 29:24:54 | Total elapsed time: 29:24:54 # ############################################################################################################################ ############################################################################################################################ # # S.M.A.R.T. Status (device type: default) # ATTRIBUTE INITIAL STATUS # # 5-Reallocated_Sector_Ct 0 - # # 9-Power_On_Hours 0 - # # 184-End-to-End_Error 0 - # # 187-Reported_Uncorrect 0 - # # 190-Airflow_Temperature_Cel 21 - # # 197-Current_Pending_Sector 0 - # # 198-Offline_Uncorrectable 0 - # # 199-UDMA_CRC_Error_Count 0 - # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> FAIL: unRAID's Preclear signature not valid. Anything useful I can provide? preclear.disk.log
  10. I believe I only have LSIO images so never noticed this. Ugh.. this could make the fix messy.
  11. It's just two commands. One to download @ljm42's shell script and another to run it. So really your're trusting @ljm42here 🙂
  12. You should never paste random code from the Internet into your computer without understanding what it does... but that aside, if you open up a terminal and paste in the following line: wget https://gist.githubusercontent.com/ljm42/74800562e59639f0fe1b8d9c317e07ab/raw/387caba4ddd08b78868ba5b0542068202057ee90/fix_docker_client -O /tmp/dockfix.sh; sh /tmp/dockfix.sh Then the fix should be applied until you reboot.
  13. Just found the email with my original key - Apr 26, 2010! Been running the same Atom D510 motherboard from then... until today! I literally just fired up a dual CPU Xeon processor in a Supermicro 24-bay chassis because I want to start running Docker / VMs to consolidate other servers in my house. Looking forward to a new era of rock solid stability.
  14. I've been running a Atom based system since April 2010 and I think it's time for an upgrade... I'm planning to start with the chassis, and want a 24 bay removable drive system as the cheap Roswell case I currently have is a pain to work with. I've been doing some reading and think something like this CSE-846E1-R900B would work but I'd need to swap out the backplane to a BPN-SAS2-846EL1. Can anyone confirm?