acurcione

Members
  • Posts

    272
  • Joined

  • Last visited

Everything posted by acurcione

  1. So after I posted this I rebooted the thing and ran a single preclear. It finished successfully so the mystery deepens. I still have new memory that should arrive today and since this would be the second unexplained incident, I'll go ahead and swap it. Then test the hell out of it. And I should probably run another preclear cycle once that's all done just to be extra sure, but that might be overkill.
  2. Ah. Well, I ordered some new ram anyway. I haven't had any errors elsewhere, but it can't hurt. I'll run a very long memtest when I get them and then run preclear again. If I still have problems it's either the drive or something else as you state. I just don't want a chance for data corruption!
  3. Wow. Ram prices sure have dropped since my build. Should I just buy new ram anyway? Honestly have nothing else to go on, but Ram was the first suggestion to my other issue as well. Figured a 3 hour passed memtest was good though.
  4. Been running with it for 2 years and I just ran a memtest for 3 hours with no errors. How the heck do I determine if that's indeed the problem?
  5. I didn't know this post existed so I started a new one - sorry about that. I can always remove that one if needed. Anyway, here's the post in it's entirety: I added a new drive (4TB WD Red) to the array so I can use it to do the file system swap thing so first thing I did was try to preclear it. I used the plugin this time instead of doing it on the console and I just used it with the defaults. I'm pretty sure when I first built this in 2014 I used some parameters with the preclear script, but darned if I can remember what or why. Anyway, I ran a 3 pass preclear and after 84+ hours it says it failed because it detected non-zero bytes. I have no idea what to do at this point. Should I run it again with some parameters? If so, could someone enlighten me as to what cause I can't seem to find that part anymore. Attaching the output from the preclear. It doesn't seem to allow me to paste it all in here. Also, before anyone says check RAM, I recently did a 3 hour memtest at someones suggestion for trying to determine the cause of another issue which led to me wanting to change the file system over to XFS. The memtest came back fine, BTW. Just found this, if it helps: = Post-Read in progress: 99% complete. ( 3,998,790,656,000 of 4,000,787,030,016 bytes read ) 66.7 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:15 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,998,990,745,600 of 4,000,787,030,016 bytes read ) 67.0 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:21 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,190,835,200 of 4,000,787,030,016 bytes read ) 66.4 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:27 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,390,924,800 of 4,000,787,030,016 bytes read ) 65.7 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:32 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,591,014,400 of 4,000,787,030,016 bytes read ) 66.8 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:38 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,791,104,000 of 4,000,787,030,016 bytes read ) 67.3 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:44 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,991,193,600 of 4,000,787,030,016 bytes read ) 65.4 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:50 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 4,000,191,283,200 of 4,000,787,030,016 bytes read ) 66.7 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:55 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 4,000,391,372,800 of 4,000,787,030,016 bytes read ) 66.1 MB/s Disk Temperature: 31C, Elapsed Time: 84:59:01 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 4,000,591,462,400 of 4,000,787,030,016 bytes read ) 67.5 MB/s Disk Temperature: 31C, Elapsed Time: 84:59:07 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 31C, Elapsed Time: 84:59:13 ========================================================================1.15 == WDCWD40EFRX-68WT0N0 WD-WCC4E7ZUZET9 == Disk /dev/sde has NOT been precleared successfully == skip=2273000 count=200 bs=1000448 returned 00008 instead of 00000 skip=2287200 count=200 bs=1000448 returned 00008 instead of 00000 skip= 2301600 count=200 bs=1000448 returned 00008 instead of 00000 skip=2316000 count=200 bs=1000448 returned 00008 instead of 00000 skip=2330200 count=200 bs=1000448 returned 00008 instead of 00000 skip=2344600 count=200 bs=1000448 returned 00008 instead of 00000 skip=2358800 count=20 0 bs=1000448 returned 00008 instead of 00000 skip=2373200 count=200 bs=1000448 returned 00008 instead of 00000 skip=2387400 count=200 bs=100 0448 returned 00008 instead of 00000 skip=2401800 count=200 bs=1000448 returned 00008 instead of 00000 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 121 123 0 ok 31 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. root@Tower:/usr/local/emhttp# preclear-052016.txt
  6. I added a new drive (4TB WD Red) to the array so I can use it to do the file system swap thing so first thing I did was try to preclear it. I used the plugin this time instead of doing it on the console and I just used it with the defaults. I'm pretty sure when I first built this in 2014 I used some parameters with the preclear script, but darned if I can remember what or why. Anyway, I ran a 3 pass preclear and after 84+ hours it says it failed because it detected non-zero bytes. I have no idea what to do at this point. Should I run it again with some parameters? If so, could someone enlighten me as to what cause I can't seem to find that part anymore. Attaching the output from the preclear. It doesn't seem to allow me to paste it all in here. Also, before anyone says check RAM, I recently did a 3 hour memtest at someones suggestion for trying to determine the cause of another issue which led to me wanting to change the file system over to XFS. The memtest came back fine, BTW. Just found this, if it helps: = Post-Read in progress: 99% complete. ( 3,998,790,656,000 of 4,000,787,030,016 bytes read ) 66.7 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:15 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,998,990,745,600 of 4,000,787,030,016 bytes read ) 67.0 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:21 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,190,835,200 of 4,000,787,030,016 bytes read ) 66.4 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:27 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,390,924,800 of 4,000,787,030,016 bytes read ) 65.7 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:32 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,591,014,400 of 4,000,787,030,016 bytes read ) 66.8 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:38 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,791,104,000 of 4,000,787,030,016 bytes read ) 67.3 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:44 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 3,999,991,193,600 of 4,000,787,030,016 bytes read ) 65.4 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:50 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 4,000,191,283,200 of 4,000,787,030,016 bytes read ) 66.7 MB/s Disk Temperature: 31C, Elapsed Time: 84:58:55 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 4,000,391,372,800 of 4,000,787,030,016 bytes read ) 66.1 MB/s Disk Temperature: 31C, Elapsed Time: 84:59:01 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Post-Read in progress: 99% complete. ( 4,000,591,462,400 of 4,000,787,030,016 bytes read ) 67.5 MB/s Disk Temperature: 31C, Elapsed Time: 84:59:07 ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 3 of 3, partition start on sector 1 = = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Verifying if the MBR is cleared. DONE = Disk Post-Clear-Read completed DONE Disk Temperature: 31C, Elapsed Time: 84:59:13 ========================================================================1.15 == WDCWD40EFRX-68WT0N0 WD-WCC4E7ZUZET9 == Disk /dev/sde has NOT been precleared successfully == skip=2273000 count=200 bs=1000448 returned 00008 instead of 00000 skip=2287200 count=200 bs=1000448 returned 00008 instead of 00000 skip= 2301600 count=200 bs=1000448 returned 00008 instead of 00000 skip=2316000 count=200 bs=1000448 returned 00008 instead of 00000 skip=2330200 count=200 bs=1000448 returned 00008 instead of 00000 skip=2344600 count=200 bs=1000448 returned 00008 instead of 00000 skip=2358800 count=20 0 bs=1000448 returned 00008 instead of 00000 skip=2373200 count=200 bs=1000448 returned 00008 instead of 00000 skip=2387400 count=200 bs=100 0448 returned 00008 instead of 00000 skip=2401800 count=200 bs=1000448 returned 00008 instead of 00000 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Temperature_Celsius = 121 123 0 ok 31 No SMART attributes are FAILING_NOW 0 sectors were pending re-allocation before the start of the preclear. 0 sectors were pending re-allocation after pre-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 3. 0 sectors were pending re-allocation after post-read in cycle 1 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 2 of 3. 0 sectors were pending re-allocation after post-read in cycle 2 of 3. 0 sectors were pending re-allocation after zero of disk in cycle 3 of 3. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 0 sectors had been re-allocated before the start of the preclear. 0 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. root@Tower:/usr/local/emhttp# preclear-052016.txt
  7. I can't give you an exact time, but it wasn't recent. Once it became non-beta I upgraded. This is the first hiccup I've had.
  8. I think I've talked myself into buying another drive to do this in as safe a fashion as I can. I'll have to read up on that process now too! Haven't added a drive after the initial build!
  9. Thanks. I guess if I buy a new drive this would be the way to do the conversion.
  10. Alright. I read over the meat of the post on the first page and since my situation doesn't match that criteria I'd to spell out what I "think" I need to do based on it. And if this is getting way too complicated I may just go back to my first option, but this in theory should be cleaner and safer. I think. I have 3 4TB drives + 4TB Parity. 2 drives are 50% full (so 2TB). The last drive, disk3, has only 1.21TB on it with 2.79TB free. This would be my target disk for copy/swapping since it's the only one with space. Step 1 would be step 6 in the guide, create the temp directory on disk3. Step 2 would be to run the rsync command to copy disk1 over to the temp directory on disk3 and then verify that there were no corruptions in the output file. Step 3, providing there were no errors, I stop the array and change the file system on disk1 to XFS. Step 4, start the array back up. Step 5, format disk1 XFS (weird that it's 2 steps, but that's just me...). Step 6 is now back to step 6 in the guide, with [dest] now disk1 a the source ONLY the temp directory on disk3. Follow through to step 10, but I actually do need to delete the temp directory now on disk3 to make room for disk2. Rinse and repeat for disk2. The process would be the same for disk3 except I'd be copying it to disk1 or disk2. It's going to be a really tight fit though and a little scary to be honest... but again that might just be me. Or should I just say F it and buy another 4TB WD Red and put it in to do this swapping?? Thanks all. Sorry this thready has now kind of strayed a bit.
  11. Thanks. I'll take a closer look at that. I do have enough free space on one drive that I could use to shuffle initially. Not sure I understand how the shuffle would work though. It would have to be at the disk device level and not the share level. I think Anyway, I'll take a good read through that and pick a direction. This would certainly be faster than copying 6TB over my network again!
  12. it is really up to you. Disabling parity speeds up the process but lleaves you susceptible to data loss if a disk fails (and you are probably working the system harder than normal during this process). I think most people leave parity enabled for safety as it can be a long process from a time-elapsed perspective. Typically a copy is started and then left to run while you get on with something else. I'm going to follow this up and say, if you've got good backups or this is only a backup server (I think you said that) then I think you are at very low risk of data loss if you disable the parity when you are copying the data on the drive. My main media is on a Raid 5 array and this box is my backup. For now anyway.
  13. it is really up to you. Disabling parity speeds up the process but lleaves you susceptible to data loss if a disk fails (and you are probably working the system harder than normal during this process). I think most people leave parity enabled for safety as it can be a long process from a time-elapsed perspective. Typically a copy is started and then left to run while you get on with something else. Alright. Cool. I hate having to destroy my media backup in order to do this, but it doesn't look like I have a choice. I haven't seen anyone else suggest anything else for the problem I had.
  14. Finished checking all drives and none showed any issues. Is it everyone's consensus I should take the opportunity to change over to XFS? If yes, I'd need to backup my cache drive data and copy that back over after the change. Also, and I apologize for the question but it's been too long... Do I disable parity before I start changing the drives and leave it off until all the data is copied back into the array so it doesn't slow down the process? Or is that a bad idea?
  15. Technically, now would be an OK time to do that if everyone thinks it's a good idea, regardless of current issue. My unRaid box is just a backup and a server for one app currently. So I can fairly easily copy all my media back over to it after reformatting. It'll take several days though! [emoji4] Thoughts?
  16. Alright. I ran a memtest that lasted 3 hours (2 passes) and had no errors. After this when I restarted I was getting some strange error so I unplugged the box, waited a few seconds, jumped in the BIOS to make sure nothing was hinky, and then restarted again. Booted right up. I checked the filesystem on both the cache and the drive that was being written too via mover and both had no errors. I'm going to check the other disks (not the parity) anyway and then start everything up again. Probably run a parity check on it, too. Failing any of that coming back with errors, any other ideas?
  17. Ok... I managed to get the thing to reboot after killing a few processes left over from the failed mover thing. When it came back up it immediately started a Parity check. I stopped that and am trying a "clean" reboot. What should I do after this thing comes back up?
  18. Telneted in to try and reboot that way and the damn thing won't shutdown. It seems to be completely hung up now in the UI and I don't know what else to try via command line. Even tried a shutdown command, but it's just not cooperating. Help?
  19. And more info. Mover did actually move the file in question, but never removed it from the cache drive.
  20. Well crap. I can't stop the array cause it thinks mover is still running. Spinning down the drives isn't actually doing anything now even though it looks like they're all spun down already. How the heck to get this to allow me to reboot to see if it helps???
  21. So I checked my logs like I do every morning and saw an error I'd never seen before. I went back in the log and it started when Mover was initiated and then just keeps repeating itself. And the file that needs moving never actually got moved either. Can someone have a look at a snippet from the logs (below) and tell me what's going on? I'm going to reboot the thing in the meantime. May 11 03:40:01 Tower logger: mover started May 11 03:40:01 Tower logger: skipping "Downloads" May 11 03:40:01 Tower logger: moving "Media" May 11 03:40:01 Tower logger: ./Media/tv/Blindspot/Season 1/Blindspot.S01E21.Of.Whose.Uneasy.Route.mkv May 11 03:40:01 Tower logger: .d..t...... ./ May 11 03:40:01 Tower logger: .d..t...... Media/ May 11 03:40:01 Tower logger: .d..t...... Media/tv/ May 11 03:40:01 Tower logger: .d..t...... Media/tv/Blindspot/ May 11 03:40:01 Tower logger: .d..t...... Media/tv/Blindspot/Season 1/ May 11 03:40:01 Tower logger: >f+++++++++ Media/tv/Blindspot/Season 1/Blindspot.S01E21.Of.Whose.Uneasy.Route.mkv May 11 03:40:13 Tower kernel: BUG: unable to handle kernel paging request at 000020000000001c May 11 03:40:13 Tower kernel: IP: [<ffffffff810b1322>] find_get_entry+0x41/0x7d May 11 03:40:13 Tower kernel: PGD 0 May 11 03:40:13 Tower kernel: Oops: 0000 [#1] PREEMPT SMP May 11 03:40:13 Tower kernel: Modules linked in: xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod r8169 ahci mii i2c_i801 libahci May 11 03:40:13 Tower kernel: CPU: 2 PID: 2391 Comm: shfs Not tainted 4.1.18-unRAID #1 May 11 03:40:13 Tower kernel: Hardware name: MSI MS-7846/H87M-E35 (MS-7846), BIOS V17.5 07/19/2014 May 11 03:40:13 Tower kernel: task: ffff8800d4690860 ti: ffff88040bbc0000 task.ti: ffff88040bbc0000 May 11 03:40:13 Tower kernel: RIP: 0010:[<ffffffff810b1322>] [<ffffffff810b1322>] find_get_entry+0x41/0x7d May 11 03:40:13 Tower kernel: RSP: 0018:ffff88040bbc3c28 EFLAGS: 00010246 May 11 03:40:13 Tower kernel: RAX: ffff880002659c98 RBX: 0000200000000000 RCX: 00000000fffffffa May 11 03:40:13 Tower kernel: RDX: ffff880002659c98 RSI: ffff880002659c98 RDI: 0000000000000000 May 11 03:40:13 Tower kernel: RBP: ffff88040bbc3c48 R08: ffff880002659b60 R09: ffff88040bbc3c10 May 11 03:40:13 Tower kernel: R10: 0000000000000026 R11: ffffffff81170ff6 R12: 0000000000036d22 May 11 03:40:13 Tower kernel: R13: ffff8801883b30b8 R14: ffff8801883b30b0 R15: 0000000000036d22 May 11 03:40:13 Tower kernel: FS: 00002b917f13c700(0000) GS:ffff88041eb00000(0000) knlGS:0000000000000000 May 11 03:40:13 Tower kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 May 11 03:40:13 Tower kernel: CR2: 000020000000001c CR3: 000000040bb2a000 CR4: 00000000001406e0 May 11 03:40:13 Tower kernel: Stack: May 11 03:40:13 Tower kernel: 000000000000000f ffff8801883b2f60 000000000000000f 00000000000200da May 11 03:40:13 Tower kernel: ffff88040bbc3c98 ffffffff810b1b01 ffff88040bbc3d08 ffffffff810ba20e May 11 03:40:13 Tower kernel: ffff88040bbc3d08 ffff8801883b2f60 0000000000001000 ffff8801883b30b0 May 11 03:40:13 Tower kernel: Call Trace: May 11 03:40:13 Tower kernel: [<ffffffff810b1b01>] pagecache_get_page+0x28/0x153 May 11 03:40:13 Tower kernel: [<ffffffff810ba20e>] ? balance_dirty_pages_ratelimited+0x1c/0x74d May 11 03:40:13 Tower kernel: [<ffffffff810b1dda>] grab_cache_page_write_begin+0x24/0x3b May 11 03:40:13 Tower kernel: [<ffffffff81159cca>] reiserfs_write_begin+0x5a/0x1bc May 11 03:40:13 Tower kernel: [<ffffffff810b1990>] generic_perform_write+0xd1/0x185 May 11 03:40:13 Tower kernel: [<ffffffff810b2a1f>] __generic_file_write_iter+0x9f/0x147 May 11 03:40:13 Tower kernel: [<ffffffff810b2bd9>] generic_file_write_iter+0x112/0x17d May 11 03:40:13 Tower kernel: [<ffffffff810fd986>] __vfs_write+0x8f/0xb8 May 11 03:40:13 Tower kernel: [<ffffffff810fdf05>] vfs_write+0xad/0x165 May 11 03:40:13 Tower kernel: [<ffffffff810fe76a>] SyS_pwrite64+0x50/0x81 May 11 03:40:13 Tower kernel: [<ffffffff815f7b2e>] system_call_fastpath+0x12/0x71 May 11 03:40:13 Tower kernel: Code: 68 cb fc ff 4c 89 e6 4c 89 ef e8 dc 3e 2a 00 48 85 c0 48 89 c6 74 2d 48 8b 18 48 85 db 74 38 f6 c3 03 74 07 f6 c3 01 74 2e eb d9 <8b> 53 1c 85 d2 74 d2 8d 7a 01 89 d0 f0 0f b1 7b 1c 39 d0 74 08 May 11 03:40:13 Tower kernel: RIP [<ffffffff810b1322>] find_get_entry+0x41/0x7d May 11 03:40:13 Tower kernel: RSP <ffff88040bbc3c28> May 11 03:40:13 Tower kernel: CR2: 000020000000001c May 11 03:40:13 Tower kernel: ---[ end trace 90a15233e4f0355e ]--- May 11 03:41:13 Tower kernel: INFO: rcu_preempt detected stalls on CPUs/tasks: {} (detected by 0, t=60002 jiffies, g=93716631, c=93716630, q=7744) May 11 03:41:13 Tower kernel: All QSes seen, last rcu_preempt kthread activity 0 (7461739593-7461739593), jiffies_till_next_fqs=3, root ->qsmask 0x0 May 11 03:41:13 Tower kernel: swapper/0 R running task 0 0 0 0x00000000 May 11 03:41:13 Tower kernel: 0000000000000000 ffff88041ea03de8 ffffffff81063526 ffffffff8182a500 May 11 03:41:13 Tower kernel: ffff88041ea169c0 ffff88041ea03e68 ffffffff81081a7e 0000000000000000 May 11 03:41:13 Tower kernel: ffffffff810662bc ffffffff81883030 ffffffff81804450 ffffffff8182a558 May 11 03:41:13 Tower kernel: Call Trace: May 11 03:41:13 Tower kernel: <IRQ> [<ffffffff81063526>] sched_show_task+0xd2/0xd7 May 11 03:41:13 Tower kernel: [<ffffffff81081a7e>] rcu_check_callbacks+0x52a/0x679 May 11 03:41:13 Tower kernel: [<ffffffff810662bc>] ? __update_cpu_load+0xa8/0xac May 11 03:41:13 Tower kernel: [<ffffffff8108f3dd>] ? tick_sched_handle+0x34/0x34 May 11 03:41:13 Tower kernel: [<ffffffff8108368c>] update_process_times+0x2a/0x4f May 11 03:41:13 Tower kernel: [<ffffffff8108f3db>] tick_sched_handle+0x32/0x34 May 11 03:41:13 Tower kernel: [<ffffffff8108f413>] tick_sched_timer+0x36/0x5f May 11 03:41:13 Tower kernel: [<ffffffff81083bf8>] __run_hrtimer.isra.29+0x57/0xb0 May 11 03:41:13 Tower kernel: [<ffffffff81084141>] hrtimer_interrupt+0xd8/0x1c6 May 11 03:41:13 Tower kernel: [<ffffffff810339d6>] local_apic_timer_interrupt+0x4e/0x52 May 11 03:41:13 Tower kernel: [<ffffffff81033ec7>] smp_apic_timer_interrupt+0x3a/0x4b May 11 03:41:13 Tower kernel: [<ffffffff815f895e>] apic_timer_interrupt+0x6e/0x80 May 11 03:41:13 Tower kernel: <EOI> [<ffffffff81012756>] ? native_sched_clock+0x28/0x8e May 11 03:41:13 Tower kernel: [<ffffffff814ddef1>] ? cpuidle_enter_state+0xb9/0x114 May 11 03:41:13 Tower kernel: [<ffffffff814dde87>] ? cpuidle_enter_state+0x4f/0x114 May 11 03:41:13 Tower kernel: [<ffffffff814ddf6e>] cpuidle_enter+0x12/0x14 May 11 03:41:13 Tower kernel: [<ffffffff810728dc>] cpu_startup_entry+0x1e2/0x2b2 May 11 03:41:13 Tower kernel: [<ffffffff815e56b1>] rest_init+0x85/0x89 May 11 03:41:13 Tower kernel: [<ffffffff818a7ed4>] start_kernel+0x415/0x422 May 11 03:41:13 Tower kernel: [<ffffffff818a78b5>] ? set_init_arg+0x56/0x56 May 11 03:41:13 Tower kernel: [<ffffffff818a7120>] ? early_idt_handler_array+0x120/0x120 May 11 03:41:13 Tower kernel: [<ffffffff818a74c6>] x86_64_start_reservations+0x2a/0x2c May 11 03:41:13 Tower kernel: [<ffffffff818a75ae>] x86_64_start_kernel+0xe6/0xf5 May 11 03:44:13 Tower kernel: INFO: rcu_preempt detected stalls on CPUs/tasks: {} (detected by 0, t=240007 jiffies, g=93716631, c=93716630, q=30592) May 11 03:44:13 Tower kernel: All QSes seen, last rcu_preempt kthread activity 0 (7461919598-7461919598), jiffies_till_next_fqs=3, root ->qsmask 0x0 May 11 03:44:13 Tower kernel: swapper/0 R running task 0 0 0 0x00000000 May 11 03:44:13 Tower kernel: 0000000000000000 ffff88041ea03de8 ffffffff81063526 ffffffff8182a500 May 11 03:44:13 Tower kernel: ffff88041ea169c0 ffff88041ea03e68 ffffffff81081a7e 0000000000000000 May 11 03:44:13 Tower kernel: ffffffff810662bc ffffffff81883030 ffffffff81804450 ffffffff8182a558 May 11 03:44:13 Tower kernel: Call Trace: May 11 03:44:13 Tower kernel: <IRQ> [<ffffffff81063526>] sched_show_task+0xd2/0xd7 May 11 03:44:13 Tower kernel: [<ffffffff81081a7e>] rcu_check_callbacks+0x52a/0x679 May 11 03:44:13 Tower kernel: [<ffffffff810662bc>] ? __update_cpu_load+0xa8/0xac May 11 03:44:13 Tower kernel: [<ffffffff8108f3dd>] ? tick_sched_handle+0x34/0x34 May 11 03:44:13 Tower kernel: [<ffffffff8108368c>] update_process_times+0x2a/0x4f May 11 03:44:13 Tower kernel: [<ffffffff8108f3db>] tick_sched_handle+0x32/0x34 May 11 03:44:13 Tower kernel: [<ffffffff8108f413>] tick_sched_timer+0x36/0x5f May 11 03:44:13 Tower kernel: [<ffffffff81083bf8>] __run_hrtimer.isra.29+0x57/0xb0 May 11 03:44:13 Tower kernel: [<ffffffff81084141>] hrtimer_interrupt+0xd8/0x1c6 May 11 03:44:13 Tower kernel: [<ffffffff810339d6>] local_apic_timer_interrupt+0x4e/0x52 May 11 03:44:13 Tower kernel: [<ffffffff81033ec7>] smp_apic_timer_interrupt+0x3a/0x4b May 11 03:44:13 Tower kernel: [<ffffffff815f895e>] apic_timer_interrupt+0x6e/0x80 May 11 03:44:13 Tower kernel: <EOI> [<ffffffff81012756>] ? native_sched_clock+0x28/0x8e May 11 03:44:13 Tower kernel: [<ffffffff814ddef1>] ? cpuidle_enter_state+0xb9/0x114 May 11 03:44:13 Tower kernel: [<ffffffff814dde87>] ? cpuidle_enter_state+0x4f/0x114 May 11 03:44:13 Tower kernel: [<ffffffff814ddf6e>] cpuidle_enter+0x12/0x14 May 11 03:44:13 Tower kernel: [<ffffffff810728dc>] cpu_startup_entry+0x1e2/0x2b2 May 11 03:44:13 Tower kernel: [<ffffffff815e56b1>] rest_init+0x85/0x89 May 11 03:44:13 Tower kernel: [<ffffffff818a7ed4>] start_kernel+0x415/0x422 May 11 03:44:13 Tower kernel: [<ffffffff818a78b5>] ? set_init_arg+0x56/0x56 May 11 03:44:13 Tower kernel: [<ffffffff818a7120>] ? early_idt_handler_array+0x120/0x120 May 11 03:44:13 Tower kernel: [<ffffffff818a74c6>] x86_64_start_reservations+0x2a/0x2c May 11 03:44:13 Tower kernel: [<ffffffff818a75ae>] x86_64_start_kernel+0xe6/0xf5 May 11 03:47:13 Tower kernel: INFO: rcu_preempt detected stalls on CPUs/tasks: {} (detected by 0, t=420012 jiffies, g=93716631, c=93716630, q=53316) May 11 03:47:13 Tower kernel: All QSes seen, last rcu_preempt kthread activity 0 (7462099603-7462099603), jiffies_till_next_fqs=3, root ->qsmask 0x0 May 11 03:47:13 Tower kernel: swapper/0 R running task 0 0 0 0x00000000 May 11 03:47:13 Tower kernel: 0000000000000000 ffff88041ea03de8 ffffffff81063526 ffffffff8182a500 May 11 03:47:13 Tower kernel: ffff88041ea169c0 ffff88041ea03e68 ffffffff81081a7e 0000000000000000 May 11 03:47:13 Tower kernel: ffffffff819d86c0 ffffffff81883030 ffffffff81804450 ffffffff8182a558 May 11 03:47:13 Tower kernel: Call Trace: May 11 03:47:13 Tower kernel: <IRQ> [<ffffffff81063526>] sched_show_task+0xd2/0xd7 May 11 03:47:13 Tower kernel: [<ffffffff81081a7e>] rcu_check_callbacks+0x52a/0x679 May 11 03:47:13 Tower kernel: [<ffffffff8108f3dd>] ? tick_sched_handle+0x34/0x34 May 11 03:47:13 Tower kernel: [<ffffffff8108368c>] update_process_times+0x2a/0x4f May 11 03:47:13 Tower kernel: [<ffffffff8108f3db>] tick_sched_handle+0x32/0x34 May 11 03:47:13 Tower kernel: [<ffffffff8108f413>] tick_sched_timer+0x36/0x5f May 11 03:47:13 Tower kernel: [<ffffffff81083bf8>] __run_hrtimer.isra.29+0x57/0xb0 May 11 03:47:13 Tower kernel: [<ffffffff81084141>] hrtimer_interrupt+0xd8/0x1c6 May 11 03:47:13 Tower kernel: [<ffffffff810339d6>] local_apic_timer_interrupt+0x4e/0x52 May 11 03:47:13 Tower kernel: [<ffffffff81033ec7>] smp_apic_timer_interrupt+0x3a/0x4b May 11 03:47:13 Tower kernel: [<ffffffff815f895e>] apic_timer_interrupt+0x6e/0x80 May 11 03:47:13 Tower kernel: <EOI> [<ffffffff81012756>] ? native_sched_clock+0x28/0x8e May 11 03:47:13 Tower kernel: [<ffffffff814ddef1>] ? cpuidle_enter_state+0xb9/0x114 May 11 03:47:13 Tower kernel: [<ffffffff814dde87>] ? cpuidle_enter_state+0x4f/0x114 May 11 03:47:13 Tower kernel: [<ffffffff814ddf6e>] cpuidle_enter+0x12/0x14 May 11 03:47:13 Tower kernel: [<ffffffff810728dc>] cpu_startup_entry+0x1e2/0x2b2 May 11 03:47:13 Tower kernel: [<ffffffff815e56b1>] rest_init+0x85/0x89 May 11 03:47:13 Tower kernel: [<ffffffff818a7ed4>] start_kernel+0x415/0x422 May 11 03:47:13 Tower kernel: [<ffffffff818a78b5>] ? set_init_arg+0x56/0x56 May 11 03:47:13 Tower kernel: [<ffffffff818a7120>] ? early_idt_handler_array+0x120/0x120 May 11 03:47:13 Tower kernel: [<ffffffff818a74c6>] x86_64_start_reservations+0x2a/0x2c May 11 03:47:13 Tower kernel: [<ffffffff818a75ae>] x86_64_start_kernel+0xe6/0xf5 May 11 03:50:13 Tower kernel: INFO: rcu_preempt detected stalls on CPUs/tasks: {} (detected by 0, t=600017 jiffies, g=93716631, c=93716630, q=75877) May 11 03:50:13 Tower kernel: All QSes seen, last rcu_preempt kthread activity 3 (7462279608-7462279605), jiffies_till_next_fqs=3, root ->qsmask 0x0 May 11 03:50:13 Tower kernel: swapper/0 R running task 0 0 0 0x00000000 May 11 03:50:13 Tower kernel: 0000000000000000 ffff88041ea03de8 ffffffff81063526 ffffffff8182a500 May 11 03:50:13 Tower kernel: ffff88041ea169c0 ffff88041ea03e68 ffffffff81081a7e 0000000000000000 May 11 03:50:13 Tower kernel: ffffffff810662bc ffffffff81883030 ffffffff81804450 ffffffff8182a558 May 11 03:50:13 Tower kernel: Call Trace: May 11 03:50:13 Tower kernel: <IRQ> [<ffffffff81063526>] sched_show_task+0xd2/0xd7 May 11 03:50:13 Tower kernel: [<ffffffff81081a7e>] rcu_check_callbacks+0x52a/0x679 May 11 03:50:13 Tower kernel: [<ffffffff810662bc>] ? __update_cpu_load+0xa8/0xac May 11 03:50:13 Tower kernel: [<ffffffff8108f3dd>] ? tick_sched_handle+0x34/0x34 May 11 03:50:13 Tower kernel: [<ffffffff8108368c>] update_process_times+0x2a/0x4f May 11 03:50:13 Tower kernel: [<ffffffff8108f3db>] tick_sched_handle+0x32/0x34 May 11 03:50:13 Tower kernel: [<ffffffff8108f413>] tick_sched_timer+0x36/0x5f May 11 03:50:13 Tower kernel: [<ffffffff81083bf8>] __run_hrtimer.isra.29+0x57/0xb0 May 11 03:50:13 Tower kernel: [<ffffffff81084141>] hrtimer_interrupt+0xd8/0x1c6 May 11 03:50:13 Tower kernel: [<ffffffff810339d6>] local_apic_timer_interrupt+0x4e/0x52 May 11 03:50:13 Tower kernel: [<ffffffff81033ec7>] smp_apic_timer_interrupt+0x3a/0x4b May 11 03:50:13 Tower kernel: [<ffffffff815f895e>] apic_timer_interrupt+0x6e/0x80 May 11 03:50:13 Tower kernel: <EOI> [<ffffffff81012756>] ? native_sched_clock+0x28/0x8e May 11 03:50:13 Tower kernel: [<ffffffff814ddef1>] ? cpuidle_enter_state+0xb9/0x114 May 11 03:50:13 Tower kernel: [<ffffffff814dde87>] ? cpuidle_enter_state+0x4f/0x114 May 11 03:50:13 Tower kernel: [<ffffffff814ddf6e>] cpuidle_enter+0x12/0x14 May 11 03:50:13 Tower kernel: [<ffffffff810728dc>] cpu_startup_entry+0x1e2/0x2b2 May 11 03:50:13 Tower kernel: [<ffffffff815e56b1>] rest_init+0x85/0x89 May 11 03:50:13 Tower kernel: [<ffffffff818a7ed4>] start_kernel+0x415/0x422 May 11 03:50:13 Tower kernel: [<ffffffff818a78b5>] ? set_init_arg+0x56/0x56 May 11 03:50:13 Tower kernel: [<ffffffff818a7120>] ? early_idt_handler_array+0x120/0x120 May 11 03:50:13 Tower kernel: [<ffffffff818a74c6>] x86_64_start_reservations+0x2a/0x2c May 11 03:50:13 Tower kernel: [<ffffffff818a75ae>] x86_64_start_kernel+0xe6/0xf5 May 11 03:53:13 Tower kernel: INFO: rcu_preempt detected stalls on CPUs/tasks: {} (detected by 0, t=780022 jiffies, g=93716631, c=93716630, q=98834) May 11 03:53:13 Tower kernel: All QSes seen, last rcu_preempt kthread activity 0 (7462459613-7462459613), jiffies_till_next_fqs=3, root ->qsmask 0x0 May 11 03:53:13 Tower kernel: swapper/0 R running task 0 0 0 0x00000000 May 11 03:53:13 Tower kernel: 0000000000000000 ffff88041ea03de8 ffffffff81063526 ffffffff8182a500 May 11 03:53:13 Tower kernel: ffff88041ea169c0 ffff88041ea03e68 ffffffff81081a7e 0000000000000000 May 11 03:53:13 Tower kernel: ffffffff810662bc ffffffff81883030 ffffffff81804450 ffffffff8182a558 May 11 03:53:13 Tower kernel: Call Trace: May 11 03:53:13 Tower kernel: <IRQ> [<ffffffff81063526>] sched_show_task+0xd2/0xd7 May 11 03:53:13 Tower kernel: [<ffffffff81081a7e>] rcu_check_callbacks+0x52a/0x679 May 11 03:53:13 Tower kernel: [<ffffffff810662bc>] ? __update_cpu_load+0xa8/0xac May 11 03:53:13 Tower kernel: [<ffffffff8108f3dd>] ? tick_sched_handle+0x34/0x34 May 11 03:53:13 Tower kernel: [<ffffffff8108368c>] update_process_times+0x2a/0x4f May 11 03:53:13 Tower kernel: [<ffffffff8108f3db>] tick_sched_handle+0x32/0x34 May 11 03:53:13 Tower kernel: [<ffffffff8108f413>] tick_sched_timer+0x36/0x5f May 11 03:53:13 Tower kernel: [<ffffffff81083bf8>] __run_hrtimer.isra.29+0x57/0xb0 May 11 03:53:13 Tower kernel: [<ffffffff81084141>] hrtimer_interrupt+0xd8/0x1c6 May 11 03:53:13 Tower kernel: [<ffffffff810339d6>] local_apic_timer_interrupt+0x4e/0x52 May 11 03:53:13 Tower kernel: [<ffffffff81033ec7>] smp_apic_timer_interrupt+0x3a/0x4b May 11 03:53:13 Tower kernel: [<ffffffff815f895e>] apic_timer_interrupt+0x6e/0x80 May 11 03:53:13 Tower kernel: <EOI> [<ffffffff81012756>] ? native_sched_clock+0x28/0x8e May 11 03:53:13 Tower kernel: [<ffffffff814ddef1>] ? cpuidle_enter_state+0xb9/0x114 May 11 03:53:13 Tower kernel: [<ffffffff814dde87>] ? cpuidle_enter_state+0x4f/0x114 May 11 03:53:13 Tower kernel: [<ffffffff814ddf6e>] cpuidle_enter+0x12/0x14 May 11 03:53:13 Tower kernel: [<ffffffff810728dc>] cpu_startup_entry+0x1e2/0x2b2 May 11 03:53:13 Tower kernel: [<ffffffff815e56b1>] rest_init+0x85/0x89 May 11 03:53:13 Tower kernel: [<ffffffff818a7ed4>] start_kernel+0x415/0x422 May 11 03:53:13 Tower kernel: [<ffffffff818a78b5>] ? set_init_arg+0x56/0x56 May 11 03:53:13 Tower kernel: [<ffffffff818a7120>] ? early_idt_handler_array+0x120/0x120 May 11 03:53:13 Tower kernel: [<ffffffff818a74c6>] x86_64_start_reservations+0x2a/0x2c May 11 03:53:13 Tower kernel: [<ffffffff818a75ae>] x86_64_start_kernel+0xe6/0xf5 May 11 03:56:13 Tower kernel: INFO: rcu_preempt detected stalls on CPUs/tasks: {} (detected by 0, t=960027 jiffies, g=93716631, c=93716630, q=121531) May 11 03:56:13 Tower kernel: All QSes seen, last rcu_preempt kthread activity 3 (7462639618-7462639615), jiffies_till_next_fqs=3, root ->qsmask 0x0 May 11 03:56:13 Tower kernel: swapper/0 R running task 0 0 0 0x00000000 May 11 03:56:13 Tower kernel: 0000000000000000 ffff88041ea03de8 ffffffff81063526 ffffffff8182a500 May 11 03:56:13 Tower kernel: ffff88041ea169c0 ffff88041ea03e68 ffffffff81081a7e 0000000000000000 May 11 03:56:13 Tower kernel: ffffffff810662bc ffffffff81883030 ffffffff81804450 ffffffff8182a558 And it just keeps repeating the same thing...
  22. IIRC all you have to do is download the ubooquity.js file and toss it into the appdata (overwrite the existing file) Thank you!
  23. here see search tips in my sig Thanks! No idea why I only came up with 2 posts when I searched for "ubooquity". Weird.
  24. Are you going to be updating the Ubooquity Docker with the latest version (1.9.0)? I got a message in Ubooquity about a new version available. It hasn't been available long though. Or is it simple enough to manually update it? I thought I had seen that somewhere, but haven't been able to find it this morning with searching. So if someone knows and can spell it out for me, that would be wonderful. Thanks.