Polopollo Posted January 7, 2018 Share Posted January 7, 2018 Hello, I created a post on Reddit, but I realized that here might be a better place for getting help! I made my own tower. I installed unRaid (trial version for 30days, I plan to buy the license later, I wasn't in a hurry for now) on a 16Gb USB key. I'm pretty noob so far. I bought 4 WD 8Tb HDDs. I first plugged them with the USB cables to run the pre-clear for 2.5days. Worked perfectly. I was able to access the http://tower.local the whole time without any problems. Didn't change anything in the meanwhile, was just looking into the "main" tab to follow the pre-clear progress. (Docker and VM deactivated.) Then I shucked the HDDs and put them into my tower. I read that I need to redo a pre-clear to be sure there is no problem with the sata cables. So I started the process again. Before installing them into the tower, I never had any trouble accessing my http://tower.local (from my mac) or http://tower (from my windows). After installing them into the tower, I restarted unRaid, and the menu appeared with no content under it, no matter what I click on for the menus. No errors either. As I am new with unRaid, I didn't know if it was a problem or not. I restarted the tower properly (quickly pressed the tower power button and it took 30-40 seconds to turn off. I restarted and then was able to properly access my http://tower UI. I thought it was a simple browser error at the time.) I started the pre-clear and had an email sent to me every 25%. So far in the previous preclear I had done, it was one email every 3-4 hours. It's been now 7 hours since the last email (pre-read done, and started the zeroing). I am pretty confident that I won't receive any emails anymore, as I have compared the previous one I did with USB and it was 3.5 hours for each 25%. Here I created an imgur album to show screens I am scared to restart anything, especially that I see that the chrome developer console keeps doing xhr calls to a "http://tower.local/plugins/preclear.disk/Preclear.php" The response is: { "disks": "<tr class='odd'>\n <td><img src='/webGui/images/green-on.png'><a href='/Tools/New?name=sdd'> sdd</a></td>\n <td><span class='toggle-reports' hdd='sdd' style='margin-left:0px;'><i class='glyphicon glyphicon-hdd hdd'></i><span style='margin:8px;'></span>WDC_WD80EFAX-68LHPN0_7SGLAUSC</td>\n <td>30 C</td>\n <td><span>8 TB</span></td>\n <td><span style='color:#478406;'>Zeroing: 46% @ 181 MB/s (5:43:26)</span><a id='preclear_open_sdd' class='exec tooltip' style='margin-left:5px;' onclick='openPreclear(\"7SGLAUSC\");' title='Preview'><i class='glyphicon glyphicon-eye-open hdd'></i></a><a id='preclear_rm_sdd' class='exec tooltip' style='color:#CC0000;font-weight:bold;margin-left:5px;' title='Stop Preclear' onclick='stopPreclear(\"7SGLAUSC\",\"ask\");'><i class='glyphicon glyphicon-remove hdd'></i></a></td>\n </tr><tr class='even'>\n <td><img src='/webGui/images/green-on.png'><a href='/Tools/New?name=sdb'> sdb</a></td>\n <td><span class='toggle-reports' hdd='sdb' style='margin-left:0px;'><i class='glyphicon glyphicon-hdd hdd'></i><span style='margin:8px;'></span>WDC_WD80EFAX-68LHPN0_7SGA7MRC</td>\n <td>30 C</td>\n <td><span>8 TB</span></td>\n <td><span style='color:#478406;'>Zeroing: 47% @ 181 MB/s (5:47:17)</span><a id='preclear_open_sdb' class='exec tooltip' style='margin-left:5px;' onclick='openPreclear(\"7SGA7MRC\");' title='Preview'><i class='glyphicon glyphicon-eye-open hdd'></i></a><a id='preclear_rm_sdb' class='exec tooltip' style='color:#CC0000;font-weight:bold;margin-left:5px;' title='Stop Preclear' onclick='stopPreclear(\"7SGA7MRC\",\"ask\");'><i class='glyphicon glyphicon-remove hdd'></i></a></td>\n </tr><tr class='odd'>\n <td><img src='/webGui/images/green-on.png'><a href='/Tools/New?name=sde'> sde</a></td>\n <td><span class='toggle-reports' hdd='sde' style='margin-left:0px;'><i class='glyphicon glyphicon-hdd hdd'></i><span style='margin:8px;'></span>WDC_WD80EMAZ-00WJTA0_7SGLSPNC</td>\n <td>29 C</td>\n <td><span>8 TB</span></td>\n <td><span style='color:#478406;'>Zeroing: 47% @ 181 MB/s (5:46:47)</span><a id='preclear_open_sde' class='exec tooltip' style='margin-left:5px;' onclick='openPreclear(\"7SGLSPNC\");' title='Preview'><i class='glyphicon glyphicon-eye-open hdd'></i></a><a id='preclear_rm_sde' class='exec tooltip' style='color:#CC0000;font-weight:bold;margin-left:5px;' title='Stop Preclear' onclick='stopPreclear(\"7SGLSPNC\",\"ask\");'><i class='glyphicon glyphicon-remove hdd'></i></a></td>\n </tr><tr class='even'>\n <td><img src='/webGui/images/green-on.png'><a href='/Tools/New?name=sdc'> sdc</a></td>\n <td><span class='toggle-reports' hdd='sdc' style='margin-left:0px;'><i class='glyphicon glyphicon-hdd hdd'></i><span style='margin:8px;'></span>WDC_WD80EFAX-68LHPN0_7SGGTN0C</td>\n <td>31 C</td>\n <td><span>8 TB</span></td>\n <td><span style='color:#478406;'>Zeroing: 47% @ 181 MB/s (5:49:06)</span><a id='preclear_open_sdc' class='exec tooltip' style='margin-left:5px;' onclick='openPreclear(\"7SGGTN0C\");' title='Preview'><i class='glyphicon glyphicon-eye-open hdd'></i></a><a id='preclear_rm_sdc' class='exec tooltip' style='color:#CC0000;font-weight:bold;margin-left:5px;' title='Stop Preclear' onclick='stopPreclear(\"7SGGTN0C\",\"ask\");'><i class='glyphicon glyphicon-remove hdd'></i></a></td>\n </tr>", "info": "{\"sdd\":{\"ID_MODEL\":\"WDC_WD80EFAX-68LHPN0\",\"ID_SERIAL_SHORT\":\"7SGLAUSC\",\"SERIAL_SHORT\":\"7SGLAUSC\",\"SERIAL\":\"WDC_WD80EFAX-68LHPN0_7SGLAUSC\",\"BUS\":\"usb\",\"SMART\":\"-d auto\",\"FAMILY\":\"n\\/a\",\"MODEL\":\"WDC WD80EFAX-68LHPN0\",\"FIRMWARE\":\"83.H0A83\",\"SIZE\":\"8001563222016\",\"SIZE_H\":\"8 TB\",\"DEVICE\":\"\\/dev\\/sdd\",\"PARTS\":[],\"MOUNTED\":false,\"RUNNING\":true,\"TIMESTAMP\":1515355878,\"TEMP\":\"30\",\"NAME\":\"sdd\",\"PRECLEAR\":false},\"sdb\":{\"ID_MODEL\":\"WDC_WD80EFAX-68LHPN0\",\"ID_SERIAL_SHORT\":\"7SGA7MRC\",\"SERIAL_SHORT\":\"7SGA7MRC\",\"SERIAL\":\"WDC_WD80EFAX-68LHPN0_7SGA7MRC\",\"BUS\":\"usb\",\"SMART\":\"-d auto\",\"FAMILY\":\"n\\/a\",\"MODEL\":\"WDC WD80EFAX-68LHPN0\",\"FIRMWARE\":\"83.H0A83\",\"SIZE\":\"8001563222016\",\"SIZE_H\":\"8 TB\",\"DEVICE\":\"\\/dev\\/sdb\",\"PARTS\":[],\"MOUNTED\":false,\"RUNNING\":true,\"TIMESTAMP\":1515355881,\"TEMP\":\"30\",\"NAME\":\"sdb\",\"PRECLEAR\":false},\"sde\":{\"ID_MODEL\":\"WDC_WD80EMAZ-00WJTA0\",\"ID_SERIAL_SHORT\":\"7SGLSPNC\",\"SERIAL_SHORT\":\"7SGLSPNC\",\"SERIAL\":\"WDC_WD80EMAZ-00WJTA0_7SGLSPNC\",\"BUS\":\"usb\",\"SMART\":\"-d auto\",\"FAMILY\":\"n\\/a\",\"MODEL\":\"WDC WD80EMAZ-00WJTA0\",\"FIRMWARE\":\"83.H0A83\",\"SIZE\":\"8001563222016\",\"SIZE_H\":\"8 TB\",\"DEVICE\":\"\\/dev\\/sde\",\"PARTS\":[],\"MOUNTED\":false,\"RUNNING\":true,\"TIMESTAMP\":1515355888,\"TEMP\":\"29\",\"NAME\":\"sde\",\"PRECLEAR\":false},\"sdc\":{\"ID_MODEL\":\"WDC_WD80EFAX-68LHPN0\",\"ID_SERIAL_SHORT\":\"7SGGTN0C\",\"SERIAL_SHORT\":\"7SGGTN0C\",\"SERIAL\":\"WDC_WD80EFAX-68LHPN0_7SGGTN0C\",\"BUS\":\"usb\",\"SMART\":\"-d auto\",\"FAMILY\":\"n\\/a\",\"MODEL\":\"WDC WD80EFAX-68LHPN0\",\"FIRMWARE\":\"83.H0A83\",\"SIZE\":\"8001563222016\",\"SIZE_H\":\"8 TB\",\"DEVICE\":\"\\/dev\\/sdc\",\"PARTS\":[],\"MOUNTED\":false,\"RUNNING\":true,\"TIMESTAMP\":1515355895,\"TEMP\":\"31\",\"NAME\":\"sdc\",\"PRECLEAR\":false}}", "status": { "7SGLAUSC": { "footer": "<span>WDC_WD80EFAX-68LHPN0_7SGLAUSC - 8 TB (sdd)</span><br><span style='float:right;'><span style='color:#478406;'>Zeroing: 46% @ 181 MB/s (5:43:26)</span><a id='preclear_open_sdd' class='exec tooltip' style='margin-left:5px;' onclick='openPreclear(\"7SGLAUSC\");' title='Preview'><i class='glyphicon glyphicon-eye-open hdd'></i></a><a id='preclear_rm_sdd' class='exec tooltip' style='color:#CC0000;font-weight:bold;margin-left:5px;' title='Stop Preclear' onclick='stopPreclear(\"7SGLAUSC\",\"ask\");'><i class='glyphicon glyphicon-remove hdd'></i></a></span>", "status": "<span style='color:#478406;'>Zeroing: 46% @ 181 MB/s (5:43:26)</span><a id='preclear_open_sdd' class='exec tooltip' style='margin-left:5px;' onclick='openPreclear(\"7SGLAUSC\");' title='Preview'><i class='glyphicon glyphicon-eye-open hdd'></i></a><a id='preclear_rm_sdd' class='exec tooltip' style='color:#CC0000;font-weight:bold;margin-left:5px;' title='Stop Preclear' onclick='stopPreclear(\"7SGLAUSC\",\"ask\");'><i class='glyphicon glyphicon-remove hdd'></i></a>" }, "7SGA7MRC": { "footer": "<span>WDC_WD80EFAX-68LHPN0_7SGA7MRC - 8 TB (sdb)</span><br><span style='float:right;'><span style='color:#478406;'>Zeroing: 47% @ 181 MB/s (5:47:17)</span><a id='preclear_open_sdb' class='exec tooltip' style='margin-left:5px;' onclick='openPreclear(\"7SGA7MRC\");' title='Preview'><i class='glyphicon glyphicon-eye-open hdd'></i></a><a id='preclear_rm_sdb' class='exec tooltip' style='color:#CC0000;font-weight:bold;margin-left:5px;' title='Stop Preclear' onclick='stopPreclear(\"7SGA7MRC\",\"ask\");'><i class='glyphicon glyphicon-remove hdd'></i></a></span>", "status": "<span style='color:#478406;'>Zeroing: 47% @ 181 MB/s (5:47:17)</span><a id='preclear_open_sdb' class='exec tooltip' style='margin-left:5px;' onclick='openPreclear(\"7SGA7MRC\");' title='Preview'><i class='glyphicon glyphicon-eye-open hdd'></i></a><a id='preclear_rm_sdb' class='exec tooltip' style='color:#CC0000;font-weight:bold;margin-left:5px;' title='Stop Preclear' onclick='stopPreclear(\"7SGA7MRC\",\"ask\");'><i class='glyphicon glyphicon-remove hdd'></i></a>" }, "7SGLSPNC": { "footer": "<span>WDC_WD80EMAZ-00WJTA0_7SGLSPNC - 8 TB (sde)</span><br><span style='float:right;'><span style='color:#478406;'>Zeroing: 47% @ 181 MB/s (5:46:47)</span><a id='preclear_open_sde' class='exec tooltip' style='margin-left:5px;' onclick='openPreclear(\"7SGLSPNC\");' title='Preview'><i class='glyphicon glyphicon-eye-open hdd'></i></a><a id='preclear_rm_sde' class='exec tooltip' style='color:#CC0000;font-weight:bold;margin-left:5px;' title='Stop Preclear' onclick='stopPreclear(\"7SGLSPNC\",\"ask\");'><i class='glyphicon glyphicon-remove hdd'></i></a></span>", "status": "<span style='color:#478406;'>Zeroing: 47% @ 181 MB/s (5:46:47)</span><a id='preclear_open_sde' class='exec tooltip' style='margin-left:5px;' onclick='openPreclear(\"7SGLSPNC\");' title='Preview'><i class='glyphicon glyphicon-eye-open hdd'></i></a><a id='preclear_rm_sde' class='exec tooltip' style='color:#CC0000;font-weight:bold;margin-left:5px;' title='Stop Preclear' onclick='stopPreclear(\"7SGLSPNC\",\"ask\");'><i class='glyphicon glyphicon-remove hdd'></i></a>" }, "7SGGTN0C": { "footer": "<span>WDC_WD80EFAX-68LHPN0_7SGGTN0C - 8 TB (sdc)</span><br><span style='float:right;'><span style='color:#478406;'>Zeroing: 47% @ 181 MB/s (5:49:06)</span><a id='preclear_open_sdc' class='exec tooltip' style='margin-left:5px;' onclick='openPreclear(\"7SGGTN0C\");' title='Preview'><i class='glyphicon glyphicon-eye-open hdd'></i></a><a id='preclear_rm_sdc' class='exec tooltip' style='color:#CC0000;font-weight:bold;margin-left:5px;' title='Stop Preclear' onclick='stopPreclear(\"7SGGTN0C\",\"ask\");'><i class='glyphicon glyphicon-remove hdd'></i></a></span>", "status": "<span style='color:#478406;'>Zeroing: 47% @ 181 MB/s (5:49:06)</span><a id='preclear_open_sdc' class='exec tooltip' style='margin-left:5px;' onclick='openPreclear(\"7SGGTN0C\");' title='Preview'><i class='glyphicon glyphicon-eye-open hdd'></i></a><a id='preclear_rm_sdc' class='exec tooltip' style='color:#CC0000;font-weight:bold;margin-left:5px;' title='Stop Preclear' onclick='stopPreclear(\"7SGGTN0C\",\"ask\");'><i class='glyphicon glyphicon-remove hdd'></i></a>" } } } I can see that it still doing the Zeroing for now. I think this GUI bug happened when I tried to access my http://tower this morning (after a whole night without any trouble and still receiving the emails). But my questions are: 1) What is happening? I cannot even find the right keywords in Google to find similar cases. 2) What can I do to fix this? Like can I ssh to my tower and restart the PHP/webserver process? Or something else? 3) How can I prevent that from happening? I want to have things done well! Thanks! Paul Quote Link to comment
Squid Posted January 7, 2018 Share Posted January 7, 2018 48 minutes ago, Polopollo said: I created a post on Reddit, but I realized that here might be a better place for getting help! by far I'm curious if you can log in to the console (login: root, password whatever you set it to) And type in ls /boot and post the output. It appears from the one screen shot (can't find key file) that your flash drive became dislodged or dropped (generally always use a USB2 port) If there's no errors, type in diagnostics And then if you're able to access the flash drive over the network, upload the resulting file. It also wouldn't hurt to ensure that you have no ad-blockers running on your client PC's (or whitelist your server) Quote Link to comment
Polopollo Posted January 7, 2018 Author Share Posted January 7, 2018 (edited) Ok I am able to ssh with ssh [email protected] Then here are the results of the commands you asked me: root@Tower:~# ls /boot root@Tower:~# diagnostics Starting diagnostics collection... mkdir: cannot create directory ‘/boot/logs’: Input/output error done. ZIP file '/boot/logs/tower-diagnostics-20180107-1558.zip' created. root@Tower:~# ls /boot/logs/tower-diagnostics-20180107-1558.zip /bin/ls: cannot access '/boot/logs/tower-diagnostics-20180107-1558.zip': No such file or directory root@Tower:~# ls /boot root@Tower:~# ls / bin/ boot/ dev/ etc/ home/ init@ lib/ lib64/ mnt/ proc/ root/ run/ sbin/ sys/ tmp/ tower-diagnostics-20180107-1558/ usr/ var/ root@Tower:~# ls /boot/ root@Tower:~# ls -l /boot/ total 0 root@Tower:~# ls -l /tower-diagnostics-20180107-1558/ total 4 drwxrwxrwx 2 root root 40 Jan 7 15:58 config/ drwxrwxrwx 2 root root 80 Jan 7 15:58 logs/ drwxrwxrwx 2 root root 60 Jan 7 15:58 qemu/ drwxrwxrwx 2 root root 40 Jan 7 15:58 shares/ drwxrwxrwx 2 root root 140 Jan 7 15:58 smart/ drwxrwxrwx 2 root root 340 Jan 7 15:58 system/ -rw-rw-rw- 1 root root 5 Jan 7 15:58 unRAID-6.3.5.txt root@Tower:~# pwd /root root@Tower:~# cd /tmp/ root@Tower:/tmp# ls community.applications/ emhttp/ notifications/ plugins/ preclear_stat_sdb preclear_stat_sdc preclear_stat_sdd preclear_stat_sde tmux-0/ unassigned.devices/ root@Tower:/tmp# tar -czvf diagnostics.tar.gz /tower-diagnostics-20180107-1558 tar: Removing leading `/' from member names /tower-diagnostics-20180107-1558/ /tower-diagnostics-20180107-1558/unRAID-6.3.5.txt /tower-diagnostics-20180107-1558/qemu/ /tower-diagnostics-20180107-1558/qemu/no qemu log files /tower-diagnostics-20180107-1558/smart/ /tower-diagnostics-20180107-1558/smart/SanDisk_Ultra_Fit_4C531001461121120035-0-0-20180107-1558.txt /tower-diagnostics-20180107-1558/smart/WDC_WD80EMAZ-00WJTA0_7SGLSPNC-20180107-1558.txt /tower-diagnostics-20180107-1558/smart/WDC_WD80EFAX-68LHPN0_7SGLAUSC-20180107-1558.txt /tower-diagnostics-20180107-1558/smart/WDC_WD80EFAX-68LHPN0_7SGGTN0C-20180107-1558.txt /tower-diagnostics-20180107-1558/smart/WDC_WD80EFAX-68LHPN0_7SGA7MRC-20180107-1558.txt /tower-diagnostics-20180107-1558/shares/ /tower-diagnostics-20180107-1558/logs/ /tower-diagnostics-20180107-1558/logs/syslog.last200.txt /tower-diagnostics-20180107-1558/logs/syslog.txt /tower-diagnostics-20180107-1558/config/ /tower-diagnostics-20180107-1558/system/ /tower-diagnostics-20180107-1558/system/folders.txt /tower-diagnostics-20180107-1558/system/cmdline.txt /tower-diagnostics-20180107-1558/system/iommu_groups.txt /tower-diagnostics-20180107-1558/system/ifconfig.txt /tower-diagnostics-20180107-1558/system/ethtool.txt /tower-diagnostics-20180107-1558/system/df.txt /tower-diagnostics-20180107-1558/system/lsmod.txt /tower-diagnostics-20180107-1558/system/lsof.txt /tower-diagnostics-20180107-1558/system/ps.txt /tower-diagnostics-20180107-1558/system/memory.txt /tower-diagnostics-20180107-1558/system/lsusb.txt /tower-diagnostics-20180107-1558/system/lspci.txt /tower-diagnostics-20180107-1558/system/lsscsi.txt /tower-diagnostics-20180107-1558/system/lscpu.txt /tower-diagnostics-20180107-1558/system/vars.txt root@Tower:/tmp# ll -bash: ll: command not found root@Tower:/tmp# ls -l total 148 drwxrwxrwx 3 root root 60 Jan 6 17:28 community.applications/ -rw-rw-rw- 1 root root 132888 Jan 7 16:03 diagnostics.tar.gz drwxrwxrwx 2 root root 60 Jan 6 17:28 emhttp/ drwxr-xr-x 4 root root 80 Jan 6 17:28 notifications/ drwxr-xr-x 2 root root 40 May 26 2017 plugins/ -rw-rw-rw- 1 root root 47 Jan 7 16:03 preclear_stat_sdb -rw-rw-rw- 1 root root 47 Jan 7 16:04 preclear_stat_sdc -rw-rw-rw- 1 root root 47 Jan 7 16:03 preclear_stat_sdd -rw-rw-rw- 1 root root 47 Jan 7 16:04 preclear_stat_sde drwx------ 2 root root 60 Jan 6 17:30 tmux-0/ drwxrwxrwx 2 root root 60 Jan 6 17:28 unassigned.devices/ root@Tower:/tmp# Then I ran scp from a new terminal to copy it to my computer,I just attached it (I named it "diagnostics.tar.gz") 56 minutes ago, Squid said: (generally always use a USB2 port) Ok I did not know that, it is currently into a "USB 3.1 Gen1" port (directly on the mobo). I will change it later to a one of the usb 2.9 port under the "2 x USB 2.0 & PS/2 Combo Port" then... (here in overview, number 1 instead of number 4) 56 minutes ago, Squid said: It also wouldn't hurt to ensure that you have no ad-blockers running on your client PC's (or whitelist your server) I tried in a chrome without any extension activated in private mode, still didn't work But the fact that it says "unRAID Server - missing key file" in the GUI headers in the imgur make me think there is a problem to read the conf files in the USB key... I just wonder why so suddenly. Thanks for the help! diagnostics.tar.gz Edited January 7, 2018 by Polopollo Quote Link to comment
Squid Posted January 7, 2018 Share Posted January 7, 2018 100% the flash dropped offline. Explains a lot of the gui problems. Unfortunately, I have no idea of the ramifications for the preclear plugin. kernel: usb 2-4: USB disconnect, device number 2 6 minutes ago, Polopollo said: it is currently into a "USB 3.1 Gen1" Your mileage varies with USB 3. Generally recommended to use the absolute stablest ports / sticks available. And that is usually USB2. Speed-wise it only affects boot up time. Quote Link to comment
Polopollo Posted January 7, 2018 Author Share Posted January 7, 2018 Ok. Well in the http://tower.local I am still able to see the pre-clear progress in the chrome dev console by looking at the xhr tab. Hopefully once it is done I just reboot the tower and will be able to read the logs. Thanks for the help, I'd love to fix that ^^ Quote Link to comment
Polopollo Posted January 8, 2018 Author Share Posted January 8, 2018 Well, after a little bit more debugging on the chrome console side. I am able to see the status with this command: openPreclear("7SGLAUSC") openPreclear("7SGA7MRC") openPreclear("7SGLSPNC") openPreclear("7SGGTN0C") It has the exact same effect than if I clicked on the little "eye" icon that should have been here on the page. It is really annoying for the USB flash that disconnected. I will definitely try another port when the whole pre-clear is done. It is so weird that the pre-clear is able to continue but the emails are not sent anymore. Quote Link to comment
Polopollo Posted January 8, 2018 Author Share Posted January 8, 2018 Ok the preclear will be done in less than 30mins. Should I do something else before rebooting? Run another diagnosis? Is there a way to "test the usb boot key"? Quote Link to comment
cybrnook Posted January 8, 2018 Share Posted January 8, 2018 I did something similar when I first started unraid years ago, and made a rookie mistake. I execute the preclear script from the USB drive, and not from ram disk. Ended up killing my USB drive within a matter of hours due to the millions of writes I shot to it all at once. Quote Link to comment
Polopollo Posted January 8, 2018 Author Share Posted January 8, 2018 4 minutes ago, cybrnook said: the USB drive, and not from ram disk What does it mean? I don't remember having the choice... ------------------------- My preclear are done, here are the results: ############################################################################################################################ # # # unRAID Server Preclear of disk 7SGLAUSC # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [14:59:03 @ 148 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [14:50:24 @ 149 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: [14:58:40 @ 148 MB/s] SUCCESS # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 44:48:10 | Total elapsed time: 44:48:10 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status default # # # # # # ATTRIBUTE INITIAL CYCLE 1 STATUS # # 5-Reallocated_Sector_Ct 0 0 - # # 9-Power_On_Hours 78 123 Up 45 # # 194-Temperature_Celsius 28 30 Up 2 # # 196-Reallocated_Event_Count 0 0 - # # 197-Current_Pending_Sector 0 0 - # # 198-Offline_Uncorrectable 0 0 - # # 199-UDMA_CRC_Error_Count 0 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear Finished Successfully!. rm: cannot remove '/boot/config/plugins/preclear.disk/7SGLAUSC.resume': No such file or directory mkdir: cannot create directory '/boot/preclear_reports/': Input/output error /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh: line 2133: /boot/preclear_reports/preclear_report_7SGLAUSC_2018.01.08_14.18 .39.txt: No such file or directory /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh: line 1375: /boot/config/plugins/preclear.disk/1660150748240.sreport: No suc h file or directory root@Tower:/usr/local/emhttp# (2 others similar to it, then, for the 4th one: ############################################################################################################################ # # # unRAID Server Preclear of disk 7SGLSPNC # # Cycle 1 of 1, partition start on sector 64. # # # # # # Step 1 of 5 - Pre-read verification: [14:55:34 @ 148 MB/s] SUCCESS # # Step 2 of 5 - Zeroing the disk: [14:46:49 @ 150 MB/s] SUCCESS # # Step 3 of 5 - Writing unRAID's Preclear signature: SUCCESS # # Step 4 of 5 - Verifying unRAID's Preclear signature: SUCCESS # # Step 5 of 5 - Post-Read verification: [14:55:08 @ 148 MB/s] SUCCESS # # # # # # # # # # # # # # # ############################################################################################################################ # Cycle elapsed time: 44:37:34 | Total elapsed time: 44:37:34 # ############################################################################################################################ ############################################################################################################################ # # # S.M.A.R.T. Status default # # # # # # ATTRIBUTE INITIAL CYCLE 1 STATUS # # 5-Reallocated_Sector_Ct 0 0 - # # 9-Power_On_Hours 90 135 Up 45 # # 194-Temperature_Celsius 28 29 Up 1 # # 196-Reallocated_Event_Count 0 0 - # # 197-Current_Pending_Sector 0 8 Up 8 # # 198-Offline_Uncorrectable 0 0 - # # 199-UDMA_CRC_Error_Count 0 0 - # # # # # # # # # # # ############################################################################################################################ # SMART overall-health self-assessment test result: PASSED # ############################################################################################################################ --> ATTENTION: Please take a look into the SMART report above for drive health issues. --> RESULT: Preclear Finished Successfully!. rm: cannot remove '/boot/config/plugins/preclear.disk/7SGLSPNC.resume': No such file or directory mkdir: cannot create directory '/boot/preclear_reports/': Input/output error /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh: line 2133: /boot/preclear_reports/preclear_report_7SGLSPNC_2018.01.08_14.08 .12.txt: No such file or directory /usr/local/emhttp/plugins/preclear.disk/script/preclear_disk.sh: line 1375: /boot/config/plugins/preclear.disk/9826422508980.sreport: No suc h file or directory root@Tower:/usr/local/emhttp# I re-sshed to the tower and ran the diagnosis again, I attached the file I do not know what to do know, reboot the tower with the power button? What about the "# 197-Current_Pending_Sector 0 8 Up 8"? I guess it is ok as the end says success? What about all these errors? It is scary. diagnostics-after-preclear.tar.gz Quote Link to comment
itimpi Posted January 8, 2018 Share Posted January 8, 2018 You do not want any disk in the array which has a non-zero value for Pending sectors. It means that there are sectors on the drive that potentially cannot be read reliably. Such sectors can sometimes be cleared by successfully writing to them later but it is always a worrying sign to have them. Quote Link to comment
Polopollo Posted January 8, 2018 Author Share Posted January 8, 2018 Hmmm I wonder if it is the white label one (got 3 red labels and one white label). I put some electrical tape to hide the 3 pins that prevents that to starts, maybe it caused some interference.. Ok I am gonna reboot the tower I guess. Quote Link to comment
trurl Posted January 8, 2018 Share Posted January 8, 2018 1 hour ago, cybrnook said: I did something similar when I first started unraid years ago, and made a rookie mistake. I execute the preclear script from the USB drive, and not from ram disk. Ended up killing my USB drive within a matter of hours due to the millions of writes I shot to it all at once. 1 hour ago, Polopollo said: What does it mean? I don't remember having the choice... Ignore what cybrnook said above. Years ago there wasn't a preclear plugin, only a preclear script. And whether script or plugin, what he said about his mistake doesn't really make any sense. There is no point in speculating what might have happened unless he has an old thread we can reference about it. It's probably safe to assume it isn't relevant to this thread. Quote Link to comment
Polopollo Posted January 8, 2018 Author Share Posted January 8, 2018 Ok yes I confirm the disk that shows 197-Current_Pending_Sector 0 8 Up 8 is the white label WD one I shucked. It could be because of the electrical tape I used instead of Kapton tape. Quote Link to comment
trurl Posted January 8, 2018 Share Posted January 8, 2018 14 minutes ago, Polopollo said: Ok yes I confirm the disk that shows 197-Current_Pending_Sector 0 8 Up 8 is the white label WD one I shucked. It could be because of the electrical tape I used instead of Kapton tape. Pending sectors are internal to the disk and extremely unlikely to be affected by anything you did with tape. The usual course for pending sectors while preclearing is to preclear again so the pending sectors will be reallocated when rewritten. If you can't get them to zero using this method then the disk shouldn't be trusted. Quote Link to comment
Polopollo Posted January 8, 2018 Author Share Posted January 8, 2018 I think I have 4 more days to exchange them at best buy. As it is a white label, I think I won't bother more and just change it! Quote Link to comment
pwm Posted January 9, 2018 Share Posted January 9, 2018 7 hours ago, cybrnook said: I did something similar when I first started unraid years ago, and made a rookie mistake. I execute the preclear script from the USB drive, and not from ram disk. Ended up killing my USB drive within a matter of hours due to the millions of writes I shot to it all at once. The preclear is a sequential operation. So it should be perfectly safe for a USB drive unless the USB enclosure has bad ventilation in which case it wouldn't be fit for normal file transfers either. But more than one manufacturer of USB drives have released models with bad ventilation (and so getting lots of warranty returns). Quote Link to comment
trurl Posted January 9, 2018 Share Posted January 9, 2018 5 minutes ago, pwm said: The preclear is a sequential operation. So it should be perfectly safe for a USB drive unless the USB enclosure has bad ventilation in which case it wouldn't be fit for normal file transfers either. But more than one manufacturer of USB drives have released models with bad ventilation (and so getting lots of warranty returns). That might make some sense, but not sure it really fits with this sentence: 7 hours ago, cybrnook said: I execute the preclear script from the USB drive, and not from ram disk. Don't know what that means, or how it could be the mistake that caused the death of the drive. Quote Link to comment
pwm Posted January 9, 2018 Share Posted January 9, 2018 1 minute ago, trurl said: That might make some sense, but not sure it really fits with this sentence: Don't know what that means, or how it could be the mistake that caused the death of the drive. I have always run my own "curation" of new drives - but if the script writes down the current clear position at a very high frequency, then it can matter if that state information is written to a RAM file system or to a USB drive. At least if the state file is closed between each update, since that forces meta information updates on the disk and that would trig journal writes etc in the disk file system. So with a frequently update state file on the USB drive, there could be a rather high number of disk seeks. And that makes the drive hotter. 1 Quote Link to comment
Polopollo Posted January 9, 2018 Author Share Posted January 9, 2018 Hijacking my thread quickly: I put in a usb 2 port, it works fine...for now. Now I decided to start the array with the 3 disks that are fine, while the 4th one I exchanged yesterday is pre-clearing. Here is the imgur album result, including some errors. I guess I have to wait the end of the parity sync before doing anything? Despite that they were all empty (pre-clear put everything to 0 right?) My big question is: Isn't it a problem that it tries to format the disk WHILE parity-sync? Quote Link to comment
JorgeB Posted January 9, 2018 Share Posted January 9, 2018 12 minutes ago, Polopollo said: including some errors Those warnings are normal, FCP plugin is probably complaining of the same. 12 minutes ago, Polopollo said: My big question is: Isn't it a problem that it tries to format the disk WHILE parity-sync? It doesn't try, you can format it, it's not a problem, it will just take much longer. Quote Link to comment
Polopollo Posted January 9, 2018 Author Share Posted January 9, 2018 Thanks for calming me ^^ Here is what the FCP plugin is saying: https://imgur.com/KK9OVk1 And here is what the main page looks like https://imgur.com/Lx6uud1 So I guess everything is ok for now and I just ignore the FCP plugin warning, and wait the parity sync to be completely done before doing anything else anymore (setting up shares etc) Thanks! Quote Link to comment
Squid Posted January 10, 2018 Share Posted January 10, 2018 If the error / notification from FCP came before you formatted the disk, then the error is valid. A rescan within FCP should clear the error, since the Main tab shows that there's no problems with disk 1. But, if a rescan still shows the same error, can you post another diagnostics so I can see why FCP is failing Quote Link to comment
Polopollo Posted January 10, 2018 Author Share Posted January 10, 2018 Ok I did not click on the "ignore" on this error on the FCP plugin page. I clicked re-scan got: No errors found I will sleep better tonight Thanks!! Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.