maximusfacq

Members
  • Posts

    37
  • Joined

  • Last visited

Everything posted by maximusfacq

  1. @johnnie.black Thanks for the solution without the judgement! That did the trick!
  2. Once the preclear on the new disk finished (disk11 Now), I added it to the array and started copying files to it, from disk9. disk9 is the disk I want to replace, with what is now disk11. How to I move disk9 out of the array, and keep the files on disk11, that I moved to it from disk9, all while making disk11, the new disk9?
  3. Ok. So, I let my data get ahead of my storage capacity and I now have a problem. I have: A 10 TB Parity Disk Multiple 4TB Data Disks, Multiple 3TB Data Disks, and 2 8TB Data Disks (Now, totaling 11 Data Disks) 2 - 512MB M.2 SSDs as a Cache Pool I had high water settings on my Data Disks for 500GB, so as not to let them get too full. However, multiple disks are now hitting that mark and I needed to move some data around. I was doing some of this while the latest 8TB data disk addition was preclearing. But, there was only so much I could juggle with such limited free space available. disk9 (3TB), in my array is the disk I wanted to use disk11 to replace. However, I ran out of space before I could move all the data off of disk9. Then, the preclearing of disk11 completed, and I had this <sarcasm>Brilliant</sarcasm> idea to add that to the array, and move all the data off of disk9, remove disk9 from the array, and make the new disk11 become disk9. Then, just run the Tools > New Permissions task, and be all set, right? That's where the wheels started turning and I thought myself into a conundrum. If I do try to swap the new disk11 for the current disk9, won't a parity check try to overwrite disk11 with 0s, because I've cleared disk9 before removal? I've searched the forums a bit, and found similar questions, with different answers. I have a problem with that. There should be a definitive answer for this scenario. Will someone please save me from myself and help me with the correct steps to get out of this situation? The end goal is to make the small 3TB disk go away, and replace it with the new 8TB disk, and not suffer any data loss. Appreciate your time, in advance.
  4. I can also confirm this process works. I have converted 6 of my 9 data disks to XFS from ReiserFS. I started by adding a new data disk as XFS. Then, migrated data from one disk to the next, stopped the array, changed the format setting, started the array, and hit the format button. It's really just that simple. Thanks @limetech!
  5. Eureka!! Night and Day difference! 77.1 MB/s Data Rebuild now. Thanks for the head bonk @johnnie.black!! And remember kids... the AOC-SASLP-MV8 Controller DOES NOT LIKE the 16x PCIe slot! Seems to dig the 8x slot on my mobo.
  6. I had the controller in a PCIe 16x slot. I seem to recall reading something about others having issues with that and my controller card. I've moved it to another slot. Will begin testing shortly.
  7. @johnnie.black, Thanks for that info. I have the latest BIOS for my mobo. I have the latest version of unRAID (I only count stable, release versions). I've rebooted several times. At this point, the only option I see, if it's an IRQ issue, is to go into the BIOS and look for crap to disable. I will try that now. If anyone has any other ideas, please feel free to chime in.
  8. Yes. Sorry. That file was generated just after I re-checked the BIOS to see if I'd missed any settings I needed to change, and prior to re-starting the Re-Build. Here's a new one. unraid-diagnostics-20160706-1452.zip
  9. I was attempting to transfer some data from disk1 to disk8 in my array (I want to move all my data disk from ReiserFS to XFS). At some point in this ungodly slow transfer (60 KB/s, at times), disk8 started generating errors. This, of course, angered unRAID and it flagged disk8 as bad. A SMART test of the drive revealed it was fine. Nonetheless, due diligence warranted I replace the power and Sata cables connected to that disk. There was no Trust Array option I could find in 6.x, like I used to see in 5.x. So, I swapped out disk8 with a hot spare, pre-cleared disk, and initiated the Data Rebuild. It started slow, like usual, at 2.5MB/s. When I checked back, a few minutes later, it still was showing the rebuild at 2.5 MB/s. This struck me as odd, because when I upgraded the system last week, one of the first things I did was test the pre-clear process on a new disk. That was running at 170 MB/s, at times (This was an increase over what I'd seen with my old CPU, Mobo, and RAM ~130 MB/s peak). So, my expectation was that Data Rebuilds might also be a little faster than before. The last one I did peaked at ~70 MB/s. The slow rebuild continued for 12 hours overnight, still at 2.5 MB/s. I've attached the unraid-diagnostics report. I'm not sure what the root cause may be. But, this is extremely frustrating and I'm at a loss as to why things would be so slow with the huge upgrades I just did. Old CPU, Mobo, RAM: Intel i3 (Don't recall the model. 2130 perhaps?) Gigabyte Z68MX-UD2H-B3 4GB Ballistix RAM New CPU, Mobo, RAM: Intel i7 6700K Gigabyte Z170X-Gaming 7 Rev 1.0 32GB GSkill Ripjaws Any ideas as to what the issue may be? Thanks, in advance, for your time. P.S. Also running firmware 21 for my SuperMicro AOC-SASLP-MV8 Controller unraid-diagnostics-20160706-1359.zip
  10. @jonathanm, Being that I had already pre-cleared the disk prior to setting it up as the cache disk, I expected to just be able to set it as a data disk and simply format it. I was mistaken. :'(
  11. @RobJ, I posted this here due to the seemingly uncommon knowledge that the above behavior occurs when multiple disks are added as cache disks. There should be some kind of "WARNING:" or "NOTICE:" block of text in the Cache Devices screen that indicates what repercussions could be caused with actions therein.
  12. @jonathanm, After recovering all the data, I re-added the 2 disks as a cache clustered-pair. I was able to force the formatting of the one unmountable cache disk. Then, I added the old cache disk to the data array. I'm now waiting, for who knows how long, for the WebUI to show that the disk is cleared. I wish there was a faster way to do this and still allow access to my shares. >.<
  13. @jonathanm, Thanks for the tip on that plugin. I wasn't aware it existed and it's extremely helpful! I was able to mount my old cache disk and copy over my docker.img file as well as my missing shares and some items I'd forgotten were still waiting on the cache disk to be transferred to the array. Now, I just need to resolve the issues with my new cache disk pair. It looks like they also suffered from my aforementioned issue.
  14. @itimpi, Thanks for the reply! No, I have not attempted to format the disk. I had hopes there might be some way to recover from this. The old format was ReiserFS. How would I go about "setting the format back?"
  15. Couldn't tell you at the moment. Made the mistake of adding extra cache drives today. Docker is currently dead. Hoping to recover. I posted about the issue here: http://lime-technology.com/forum/index.php?topic=50074.0
  16. I swapped out my motherboard, CPU, and RAM today. I added 2 new m.2 SSDs, with the intention to use them as cache drives, in addition to my existing drive. If they worked out well, I planned to use my old cache drive (3TB WD Black) in the data array. Everything seemed fine after boot. All the drives seemed to be in the correct places, with 0 adjustment required. I added the 2 new m.2 SSDs under the Cache Devices section and started the Array. That's when things got ugly. Now, the original cache drive is Unmountable. Unmountable disks present emhttp: mount error: No file system (no btrfs UUID) Syslog is showing this mess: Jun 29 21:25:57 UNRAID emhttp: shcmd (59): mkdir -p /mnt/cache Jun 29 21:25:57 UNRAID emhttp: shcmd (60): set -o pipefail ; mount -t btrfs -o noatime,nodiratime /dev/sdh1 /mnt/cache |& logger Jun 29 21:25:57 UNRAID logger: mount: wrong fs type, bad option, bad superblock on /dev/sdh1, Jun 29 21:25:57 UNRAID logger: missing codepage or helper program, or other error Jun 29 21:25:57 UNRAID logger: In some cases useful info is found in syslog - try Jun 29 21:25:57 UNRAID logger: dmesg | tail or so Jun 29 21:25:57 UNRAID logger: Jun 29 21:25:57 UNRAID emhttp: shcmd: shcmd (60): exit status: 32 Jun 29 21:25:57 UNRAID emhttp: mount error: No file system (32) Jun 29 21:25:57 UNRAID emhttp: shcmd (61): rmdir /mnt/cache The 2 Docker containers I had running are missing. Two if my shares are missing as well. There are files on the cache drive that have not yet been written to the array. I expect that my docker config file is also on the cache drive as well. Is this recoverable? Will I just have to check the format box and lose it all? I've done some reading on the forums. Some are saying that unplugging the cache drive could fix it. It did not. Others are saying that you need to change the drive from btrfs back to reiserFS. Not sure how to do that, but, I did run fsck on the drive to see if that might help. Any assistance would be warmly welcomed!
  17. advancesettings.xml and sources.xml have been added. Not sure what passwords.xpl is used for, but, it doesn't currently hold data on any of my HTPCs.
  18. I ran into some issues post-install. Firstly, after the install completed, I let the container run 10 minutes or so, then modified the advancedsettings.xml file to match the MariaDB IP:Port and user/pass required to connect to my existing DB. Then, restarted the container. Once complete, I noticed that it hadn't scanned in new content. So, I had a look at the kodi.log file. The log file indicated that it did not find my current DBs. This issue was related to the name elements I was missing for the movies and music DBs, which I had in my other advancedsettings.xml files, but they weren't in the pre-packaged file. So, I added these, and restarted again and it found my DBs. However, it did no scraping/updating. - Is there a way to schedule scraping in the Kodi-headless container at an automated interval? - If so, how is this configured? - If this is not how most are configuring their scraping, how are they doing it and how is that configured? Secondly, I've been doing some reading around the forum boards and found others that have had issues with order of operations for container start. - Should I be concerned about MariaDB starting before Kodi-headless or vice versa? - If so, how would I best resolve this issue?
  19. Ahhh!!! Much, much better! Have the correct build now, I believe. At least, tt's building now. We shall see when it's done! I also found that Advanced toggle switch! Thanks @saarg and @CHBMB!! I swear! I'm not daft!
  20. @saarg/@CHBMB, Thanks for the quick replies! Unfortunately, I was unable to find any template, after adding this repo (https://hub.docker.com/r/linuxserver/kodi-headless/) that looks like @CHBMB's screenie. I don't have an Environment Variables section, and I don't see a button or link to enable it. I also don't see a template named precisely the same, nor do I see the same container volume path. So, I clearly am missing something here. I want to get this right. Because the last time I tried this, with an older version, it did absolutely nothing for me. Here's what I see in my list under "Sparklys-Repo" Kodi-headless[helix] kodi-headless[isengard] koma-Isengard koma-Helix I really just want the headless kodi container. I already have a Maria DB container setup and working rather well, for quite some time now. Thanks Again!
  21. What is unclear to me, is how to get a 16.x (Jarvis) Kodi Headless container running. I see stuff all over the place that does 15.x Kodi Headless. But, it's unclear how to get that properly-updated. Question: Is it just as simple as spinning up the 15.x one and doing an apt-get upgrade? If it's more complex, or if anyone else has a pre-built container out there with 16.x that my Google Fu seems to be unable to locate, please let me know! Thankies!
  22. I was running a parity check overnight. When I came back to it, this morning, the check completed with 768 errors on Disk 5 in my array. I was able to recover a portion of the syslog, but, not all I also ran a SMART report: smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Device Model: WDC WD40EFRX-68WT0N0 Serial Number: WD-WCC4E1711392 LU WWN Device Id: 5 0014ee 2b4d397aa Firmware Version: 80.00A80 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: Not in smartctl database [for details use: -P showall] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 3.0 Gb/s) Local Time is: Fri May 8 13:42:03 2015 CDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (51840) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 518) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x703d) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 67 3 Spin_Up_Time 0x0027 182 178 021 Pre-fail Always - 7866 4 Start_Stop_Count 0x0032 099 099 000 Old_age Always - 1050 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 091 091 000 Old_age Always - 6829 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 8 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 2 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3190 194 Temperature_Celsius 0x0022 125 114 000 Old_age Always - 27 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 2 198 Offline_Uncorrectable 0x0030 100 253 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 100 253 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. Is this disk dead? Can I rebuild this disk from parity, or just replace it? I haven't been able to validate if there was a cabling failure yet. While I suppose that's possible, I'm still unsure how I'd proceed to rebuild this disk from parity, without actualy replacing it. Doing a New Config seems to be ill-advised, both on the tool page itself, as well as in this Forum. So, what should I be doing next? Thanks For Your Time! unRAIDsyslog050815.txt
  23. Sorry my profile wasn't fully updated Joe L. I have resolved that issue. I'm leaning towards the drive because that's what's new, aside from the version of the preclear script that I'm running, and the fact that 4TB drives are a fairly new thing, still. I did just update from 0.9.8 to 1.13. I'd had no issue with the old script, but decided that being that we're dealing with these beastly drives, that it might be time to update. All that being said, there was only 1 more drive in the server than there had been, for the last year or so. And as far as I understand, the power supply I have should adequately support 10-12 drives. Currently, in the server, I have all drives drives listed in my profile, in addition to a 4TB WD Black drive. So, 6 drives in total. I am not using any splitters, as this power supply is modular. I only have enough cables plugged in to power 4 drives with their own power connection and 2 molex connectors that plugin to the SuperMicro 5in3. Because I have tried known-working cables and ports on the motherboard, and I've had no other indication of an issue, until now, the disk controller seems to be the most logical culprit to me. But, I'm coming here to seek the opinion of the experts, such as yourself, that have been at his for longer than me. So, feel free to continue picking apart my theory. I hope that between my updated profile and what's in this post, that all your questions are answered and you have further thoughts and/or questions. Thanks Much!
  24. I'm running into a strange issue with a preclear on a brand-spankin' new 4TB Red Drive. So far, it appears to be a communication issue with the drive. I have tried: swapping cables, 3 different ports on the controller card (AOC-SASLP-MV8 - .21 Firmware) (All 3TB Reds and a 3TB Black are connected and functional on this controller), and 2 different ports on the motherboard (Gigabyte Z68MX-UD2H-B3/Z68MX-UD2H-B3, BIOS F10 09/01/2011). Each time, the preclear process fails. Below is a dump of the terminal session I was using for the preclear of the WD 4TB Red. Now, at first I thought this issue might be linked to the fact that I was using a 4TB drive. However, after the first couple failures with the Red, I received and unboxed the shiny new 4TB Black drive, that will become my new Parity drive. This one has run through the initial read and is 94% complete with writing 0's to the disk (Step 2). No issues whatsoever. The Red kept failing, much earlier in the preclear process. I expect the Black will complete as well. So, I'm thinking that it's just a bad controller or port on the drive. Perhaps Joe L. or someone else might be able to confirm my theory? I'd hate to have to RMA this drive. But, I'm not sure what else it may be and what other tests I might be able to do to confirm my theory. = 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 = = = = = = = = Elapsed Time: 11:48:18 ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = 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 = = = = = = = Elapsed Time: 11:48:23 dd: writing `/dev/sdc': Input/output error 1+0 records in 0+0 records out 0 bytes (0 B) copied, 0.000240163 s, 0.0 kB/s ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = 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 = = = = = = = Elapsed Time: 11:48:28 ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = 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 = = = = = = Elapsed Time: 11:48:33 dd: writing `/dev/sdc': Input/output error 1+0 records in 0+0 records out 0 bytes (0 B) copied, 0.000298369 s, 0.0 kB/s ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = 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 = = = = = = Elapsed Time: 11:48:38 ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = 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 = = = = = Elapsed Time: 11:48:43 dd: writing `/dev/sdc': Input/output error 1+0 records in 0+0 records out 0 bytes (0 B) copied, 0.000254822 s, 0.0 kB/s dd: writing `/dev/sdc': Input/output error 1+0 records in 0+0 records out 0 bytes (0 B) copied, 0.000137891 s, 0.0 kB/s ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = 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 = = = = = Elapsed Time: 11:48:45 ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = 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 = = = = Elapsed Time: 11:48:50 dd: writing `/dev/sdc': Input/output error 1+0 records in 0+0 records out 0 bytes (0 B) copied, 0.00133077 s, 0.0 kB/s ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = 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 = = = Elapsed Time: 11:48:55 ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = 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 = = Elapsed Time: 11:49:00 Restarting udevd is STRONGLY discouraged and not supported. If you are sure you want to do this, use 'force-restart' instead. ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = 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 the clear has been successful. = Elapsed Time: 11:49:10 ================================================================== 1.13 = unRAID server Pre-Clear disk /dev/sdc = cycle 1 of 1, partition start on sector 1 = Disk Pre-Clear-Read completed DONE = 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 = Elapsed Time: 11:49:15 ========================================================================1.13 == == SORRY: Disk /dev/sdc MBR could NOT be precleared == == out4= 00000 == out5= 00000 ============================================================================ 0000000 0+0 records in 0+0 records out 0 bytes (0 B) copied, 4.3782e-05 s, 0.0 kB/s root@UNRAID:/boot# preclear_disk.sh /dev/sdc Sorry: Device /dev/sdc is not responding to an fdisk -l /dev/sdc command. You might try power-cycling it to see if it will start responding. root@UNRAID:/boot#
  25. Re-assigning the cache drives to the share by setting them to "Use cache disk: No" and then back to "Use cache disk: Yes" as resolved the issue with the Cache drive. Thanks @sureguy The issue with the Orange Ball on the share was resolved by re-copying everything from the day that the old cache disk failed, until today, back to the server, from my workstation.