dboonthego

Nevermind. It can't be done. Right after posting this, I saw this thread: https://lime-technology.com/forum/index.php?topic=37490.0

Thanks for your support guys. I unassigned disk2 and ran it through 3 preclear cycles. It looks to have corrected the pending sector; results attached. I am about to add it back to the array and let it rebuild from parity. Is it possible to format XFS before rebuilding? The format option is greyed out.

Try starting the array with the disk unassigned. The disk assignments don't actually get updated until the array is started. That was it. Thanks!

I just installed yesterday, the log has just 4 lines. Feb 02 23:53:05 preclear_disk_sdd_11145: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 3 --frequency 2 --cycles 3 --no-prompt /dev/sdd Feb 02 23:53:05 preclear_disk_sdd_11145: Preclear Disk Version: 0.8.4-beta Feb 02 23:53:05 preclear_disk_sdd_11145: S.M.A.R.T. info type: default Feb 02 23:53:05 preclear_disk_sdd_11145: S.M.A.R.T. attrs type: default It looks like preclear does not want to clear my drive that has been part of the array already. I want to rebuild disk2 from parity back to itself, but I want to run a few preclear cycles it before doing that; the drive is suspect. The array is stopped and disk2=no device. If I try to clear this disk, it gets stuck. I have a brand new unformatted unassigned disk that has never been part of the array. I am able to successfully kick off a preclear of this disk. Did I miss a step or is this not normal? I'm running unRAID v6.2.4

I just installed yesterday, the log has just 4 lines. Feb 02 23:53:05 preclear_disk_sdd_11145: Command: /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh --notify 3 --frequency 2 --cycles 3 --no-prompt /dev/sdd Feb 02 23:53:05 preclear_disk_sdd_11145: Preclear Disk Version: 0.8.4-beta Feb 02 23:53:05 preclear_disk_sdd_11145: S.M.A.R.T. info type: default Feb 02 23:53:05 preclear_disk_sdd_11145: S.M.A.R.T. attrs type: default

Was there a solution for this? I'm experiencing the same issue.

I had the exact same issue. Cycling the setting resolved it for me.

Thank you guys for your responses. They have been very helpful. Maybe it was a parity check that I could not do while disk2 had the drive error. It is all fuzzy in my head now. I'm second guessing what I really did, but I know I did a "--rebuild-tree" twice and each time there were corrections. I saved the report. This was of course after directed to do so by the "--check" switch. I think it went like this: [*]disk2 has drive error (red x) [*]re-seat cables w/ no improvement [*]unassign disk2 [*]replace sata cable [*]run reiserfsck --check /dev/md2 [*]run reiserfsck --rebuild-tree /dev/md2 [*]assign disk2 [*]rebuild disk2 [*]run reiserfsck --check /dev/md2 [*]run reiserfsck --rebuild-tree /dev/md2 [*]start array The other disks are in good shape, no SMART issues. I did buy an extra drive over Christmas with the forethought that I may need it so I have that option also. I don't totally understand the preclear stuff. It seems unRAID will zero additional disks when added to the array, but if those disks are precleared, they can be added to the array more quickly? But, if replacing a disk, unRAID must write all bytes to the replacement disk anyway so it isn't necessary? Is that right? Other than being a time saver, are there other benefits like more passes; pre-read, write, post-read? Is preclearing my suspect drive the way to go? If I replace suspect disk2 now, then decide to "add" it back later as disk3, what will a preclear do for me as opposed to just adding it and letting unRAID zero it then?

Do you mean preclearing a brand new disk and replacing the suspect disk with the brand new one? Or unassign, preclear, and reassign the suspect disk? I'm not sure of the difference between the two procedures, but if I recall correctly from a few months ago, the array would not not start because of the filesystem errors; I had the red X for disk2. I unassigned it (probably not the right thing to do). This is when I executed the smartctl and reiserfsck commands. After that completed, I re-assigned disk2 and started the array. I don't remember exactly, but I think disk2 was rebuilt from parity at this point. Either that or parity was recalculated. Is that the same procedure as "rebuiding with the pending sector?"

Some background... I was using the free 3 disk unRAID 5.0-beta14. My hardware except for the drives was made up of spare parts including a case with no side panel. All my drive issues seem to have been due to the SATA cables; mostly because the case was exposed and problems have always happened right after I have messed with the case somehow. Re-seating cables always resolved any errors. Disk 2 always seemed to have the issue. This past November, re-seating cables was not enough. I had to replace the SATA cable for disk 2 and execute these commands. It fixed some stuff, but I have been skeptical of the drive integrity ever since. reiserfsck --check /dev/md2 reiserfsck --rebuild-tree /dev/md2 All three of the disks are the same, but disk 2 had the file system errors. It makes a slight clicking noise during spin up, but does not repeat the clicking like a dead drive usually does. The other two drives don't do this. It seemed like when disk 2 was attached, the web interface was slow to become available at boot and slow to respond during page to page clicks. The slow response may have been because of the bad cable. Fast forward to present day, I upgraded unRAID to 6.2.4 and upgraded all hardware, but am still using the same disks. Things seem to be running fine. I'm just not sure what to make of disk 2. I think I am reading the SMART results correctly. The values look good to me. I also executed both the short and extended SMART self tests and both passed without error. Thoughts? tower-smart-20170129-2233.zip

Thanks Frank. I appreciate your response and you have answered my question. I didn't necessarily want to go that route and will copy the files, but for the sake of educating myself to understand how unRAID works, assume my flash stick is dead or lost. What kind of issues would I expect to run into? Network settings and a server name seems easy enough, so I'm more curious about recreating disk.cfg and sharename.cfg's. If I was forced to do that, is it mission critical that the share settings be exactly as they were before? Or would I be free to change things like highwater vs fillup, or even the share name? Does a share name change require renaming the folders on each disk? These questions might be getting off topic, but thank you for your input.

I have been using the free 3-disk v5.0-beta13 version of unRAID. I'm upgrading to 6.2.4. The only hardware I'm keeping is the disk drives; everything else is new including the flash stick. My old server was barebones with 3 shares and no plugins. The new flash stick boots and I have registered for a 30-day trial. I know my previous device-to-serial assignments, but have not assigned them and started the array yet. http://lime-technology.com/wiki/index.php/Upgrading_to_UnRAID_v6 "There are a few configuration files that are safe to keep and restore, ident.cfg, network.cfg, share.cfg, and any .cfg files in the config/shares folder. These files hold your network settings and identification, and your share settings, and are safe to bring forward. They will help you get back on the network quicker!" All that's left to do is copy some .cfg files and start the array, right? Are there any negative effects if I don't copy them and re-create the shares manually? Also, I suspect data disk 2 might be failing, but, I don't know for sure. In the past, problems with this disk have been tied to the SATA cable. The SMART check seems to pass. Maybe the new mobo and cables will help. I do have a same-size replacement drive if needed. How should I handle disk 2 during the upgrade? Are there any drive health assessment tests I can do?

I re-seated the power and SATA data cables and although they were snug, doing this appears to have fixed my issue. The estimated finish time for the parity check is back down to 473 minutes. I guess I should have checked that first.

Hi, I'm using the Unraid free version 5.0-Beta14 with a three 2TB disks. My shares are using the fill-up allocation method. - Parity disk is sda - Data disk1 is sdb <-- 750gb free - Data disk2 is sdc <-- No data is on this disk About two weeks ago, I powered down the server using the web interface and moved it. When I booted it back up in the new location, I noticed the web interface took a noticeably longer to load the main/shares/users/settings/utils pages. When I brought the array online, those pages seemed to respond quicker. I shut the server down this earlier this week and when I booted up last night, the web interface reported that disk 2 had an error, but I could start the array without the disk. I did not start the array and rebooted instead. No errors reported after the reboot. I brought the array online and everything seemed normal except for the web interface now showing an error under disk2. I tried to stream a movie and could not without a pause every 3 minutes.. I thought this was a switch/router/cabling issue, but now I believe it to be a disk read issue on disk1. I “think” the integrity of the disk is okay and maybe this is a quirk with Unraid? I’m not positive though. I tried running a parity check and it reported 24 sync errors and 103,939 minutes (two months) estimated to finish the parity check. I don't wish to wait two months, so I canceled the parity check. I ran “smartctl –a –A /dev/sda” and also on sdb and sdc and attached the reports for those disks. Disk1 (sdb) looks like it has the issues, but, it reports 0 for Reallocated_Sector_Ct, Current_Pending_Sector, UDMA_CRC_Error_Count. System logs shows: (which is also attached). Jul 22 02:08:14 Tower kernel: ata4: lost interrupt (Status 0x50) Jul 22 02:08:14 Tower kernel: ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Jul 22 02:08:14 Tower kernel: ata4.00: failed command: READ DMA I will verify my HDD data cables did not come loose from moving the server, but other than that, I’m not sure what to do… Any suggestions? Thanks. syslog.txt smartsda.txt smartsdb.txt smartsdc.txt