Albin
-
Posts
120 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Albin
-
-
I recently noticed after running diagnostics at the command line, that my libvirt log file is reporting bunch of missing iso, img, and dev/disk/ (physical disks). I intentionally moved some VM images off the cache pool to save on room. (I move them back to the cache pool when I want to use that particular VM.
It appears to me that when you browse to the VM tab, this executes some type of search or query to see if all the iso's, images, and dev devices are in their rightfully place, which may also explain why in my case it takes a little bit of time for the VM page to load, (it is not finding what it is looking for).
here are 2 lines from the libvirt.txt file (see attached full log)
2022-06-08 14:55:32.602+0000: 14124: error : virQEMUFileOpenAs:11519 : Failed to open file '/dev/disk/by-id/ata-MKNSSDRE500GB_MK17052310036411A': No such file or directory 2022-06-08 14:55:35.245+0000: 14125: error : virFileIsSharedFixFUSE:3337 : unable to canonicalize /mnt/user/domains/sagerrecoveryuae/vdisk1.img: No such file or directoryThis may not be possible, but I will through it out there any way. Why not do the search for the files when you go to start or edit one particular vm instead of search for all the images and isos when you browse to the VM tab. (I typically do not have the disk drives section view for each vm expanded) (I like the compact view and expand the view as needed)
I may be a "one off case" for this, meaning everyone else has room to spare on their cache pool, and they do not need to get rid of or move less frequently used items off the cache pool.
There may also be a better way to handle this particular situation.
I am guessing there is no "VM Mover app". (an app that would invoke moving a VM to the cache pool along with all the iso, images, xml, nvram, and any other items for the VM), then once you are done with the VM you invoke a move to return it to the desired share on the array.
I am guessing this could be done with "user scripts". I will need to learn some more about user scripts before I can pound out anything like that in script format, and I am surely not ready to make an app for this.
In the meantime I am remapping the isos or images to a share on the array that I have set up for this, but this does not eliminate the errors I get in the libvirt log for missing physical drives. I have some VMs that are currently physical drives and only get connected and mounted to the server when I want to spin up that vm. I need to convert the physical disks to images.
Just wondering if anybody else is moving VM images off their cache pool (but leaving their VM settings and in place) and moving it back when needed. For now I am remapping the images stored on the array, to see if this speeds up load time for my VM tab.
Maybe this will help someone else out.
-
5 hours ago, bonienl said:
This is related to the text editor ACE.
I recently updated ACE to the latest available version, if you have not updated the File Manager yet, I recommend you install the latest version.
The file "mod-log.js" is indeed not existing in the ACE package, I don't know if this an error or not.
What kind of file (extension) are you opening when this error message occurs?
Ps. I can reproduce this error when I open a *.log file.
The syntax file is not present and its content is displayed as regular text.
I keep an eye on ACE to see if it gets corrected / included.
You can simply ignore the error, it has no impact.
Dynamix File Manager version is 2022.06.07
ACE version is showing under DFM release notes as version 1.5.3
The error time stamp is at the exact same time I browse to view the syslog server log at the following extension/link:
http://192.168.2.209/Shares/Browse?dir=/mnt/user/SysLogs
So every time I check the syslog file, a new error entry appears with the current time stamp.
I will ignore the error as you recommended, but I can't help but wonder what else is needing to get to
/usr/local/emhttp/ or /usr/local/emhttp/plugins
I can't find the directory emhttp. Is there a way to browse to this to see if it exists and what is actually there.
I am guessing this path exists, but I don't know enough to get to it.
I do see the go script calls for
# Start the Management Utility /usr/local/sbin/emhttp &which is not the same path as usr/local/emhttp
This may be completely unrelated but I opened terminal and ran
php /usr/local/emhttp/plugins/dynamix/include/UpdateDNS.php -vvwhich had a server response of
✅ Signed in to Unraid.net as usernamehere Use SSL is no ⚠️ Rebind protection is enabled for myunraid.net Local Access url: http://Tower.local ⚠️ hash.myunraid.net does not resolve to an IP address, it should resolve to 192.168.2.209then I ran
ping www.hash.unraid.netnote for others: actual hash value not shown
The response was:
ping: hash.myunraid.net: Name or service not knownnot sure if this has anything to do with emhttp
That's all I got for now.
Thanks again for your reply and help
-
I am really liking this integrated feature. Thanks!
I recently started using syslog because I am having some weird behaviors going on. After getting syslog server up and running I am seeing the following error
Jun 9 07:22:33 Tower2
nginx: 2022/06/09 07:22:33 [error] 9167#9167: *895418 open() "/usr/local/emhttp/plugins/dynamix.file.manager/javascript/ace/mode-log.js" failed (2: No such file or directory) while sending to client, client: 192.168.2.104, server: , request: "GET /plugins/dynamix.file.manager/javascript/ace/mode-log.js HTTP/1.1", host: "192.168.2.209", referrer: "http://192.168.2.209/Shares/Browse?dir=/mnt/user/SysLogs"
I am not sure if /usr/local/ is the same as root/usr/local but when looking around for emhttp, I do not see it. I am guessing it is there, I just don't know enough to know where to look for it.
I am not sure if how I set up sys log is part of the problem or not.
here are the settings for syslog server:
Local syslog server: Enabled UDP 514
Local syslog folder: SysLogsLocal syslog rotation: Disabled
Remote syslog server: 192.168.2.209 UDP 514
Mirror syslog to flash: NoI have several errors showing up in various location in the diagnostics. I am trying to knock them out one at a time.
Thanks for any push you can give me in the correct direction.
-
This may or may not help. I recently upgraded from 6.8.3 to 6.9.1 and windows was extremely slow. I did the following:
Opened Control Panel > Programs and Features > Turn Windows features on or off (upper left corner) (or just open windows and search for Features and it should show)
Unchecked everything under "Hyper-V" (I Run Unraid with VMs, but I do not Run Unaid with VMs that Run VMs (nested VMs) so I do not need this feature)
Checked the box "Windows Subsystem for Linux" I think this is referred to as WSL I also hear people refer to WSL2 but I currently do not see that as an option
I do have other boxes that I have checked when creating the VM a long time ago, but I do not think they are related to this issue.
I then rebooted and The slowness that I was having and CPU usage issues went away (very snappy now). Hope this helps.
Be sure to back up your VM image before attempting this.
-
1
-
-
Ability to assign Alias Names to USB Devices, to allow for easier mapping or allocating of devices in VMS.
If you have 2 or 3 keyboards, 2 or 3 mice, CD rive, USB security dongles, USB card readers, it can get a little confusing when you are trying to assign devices to VMS especially if some of them are made by the same manufacture. With the ability to assign aliases, this process would be a lot easier. If this already exists, I am not aware of it.
-
I just checked the File Activity log and it appears to be working.
-
I uninstalled and reinstalled the file activity plugin.
I also made sure that flash\config\plugins\file.activity did not exist at the time of reinstall.
After re-installation, I started file activity, but I do not see any logs or results, even after hitting refresh.
Status shows as running.
I did adjust my inotify value (from 524288 to 2524288) with tips and tweaks (thanks for the tips and tweaks plugin!)
I can't figure out why do not get results with file activity.
I attached the diagnostics. Thanks for any insight into this.
-
Thanks for the plugin
-
I am having the same issue.
I have a share called "Main" that I created years ago and have had no problems accessing it until today.
I attempted a reboot of my windows 10 machine, then the server and the win10 machine, and neither helped.
I thought it was a SMB issue, but after some trouble shooting I realized that I could access some child folders and but not all child folders but I could not drill down from parent to child:
I could access Main\Downloads\folder1 (I had to type it out or use an existing shortcut to the location)
I could access Main\Downloads\folder2 (I had to type it out or use an existing shortcut to the location)
I could not access Main\Downloads\folder3
(this folder has files on the cache drive folder1 and folder2 do not have files on cache drive)
I cannot access Main\Downloads (I am guess it is because of folder3 having files on the cache drive)
I can Main\ (which I would have thought I would not be able to because of folder3 having files on the cache drive)
I invoked mover to see what this would do, but it did not seem to help.
I installed the "Tips and Tweaks" Plugin and changed my "Max Watches 'fs.inotify.max_user_watches'" from 524288 to 2524288
(just added a 2 to the front of the default value, and will play around with this value over time, if need be.)
see Still not enough inotify watches?
As soon as I adjusted the inotify value, I could access folder1, folder2 and any other problem folder I had.
Not sure if these will help but I attached the diagnostics file before and after the inotify changes.
Unfortunately I invoked mover and also adjusted the inotify value with in minutes of each other, so I am not certain which of the changes allowed access to the offending folders.
Thanks dlandon for the plugin Tips and Tweaks !
tower2-diagnostics-20190717-1617.zip tower2-diagnostics-20190717-1454.zip
-
Attempting to dig some more on this and get this working, I noticed in an error log something about certificate/s. Could my issue be related to SSL Certificates. It looks like there are a cert.crt, with cert.key file but it is under apache keys.
-
Hey,
I am struggling to get this going.
Here is what I have:
- Unraid 6.3.5
- Apache Web Server to serve up the VirtualBox GUI interface instead of using commandline
- phpVirtualBox GUI for virtualbox
- Virtualbox
Unraid
- go script edited to change unraid GUI to port 81
- /usr/local/sbin/emhttp -p 81 &
- Rebooted
Apache is installed to /mnt/user/appdata/apache with
- Host port 1 set to 80
- Host port 2 set to 443
phpVirtuabox
- phpvirtualbox-5.0-5
- dwonloaded and unzipped to /mnt/cache/appdata/apache/www/phpvb
- changed config.php-example to config.php
- removed # commenting out line: var $noAuth = true; (not really needed)
Virtualbox
- Virtualbox v5.1.22 local version and installed version
- virtualbox extension v5.1.22 local version and installed version
- virtualbox guest additions local version and NOT showing an installed version
- virtualbox plugin v2017.05.19e
- VirtualbBox symbolic link set to: /boot/custom/vbox (Two things I do not see this folder on unraid and do I need to change this location so it is not on the flash drive?) (I created the folder "custom" and then added the folder "vbox" to get /boot/custom/vbox .... not sure if this is needed)
- vboxwebsrv host IP: 127.0.0.1
- vboxwebsrv Port 18083
- Vboxwebserver log file location /boot/config/plugins/virtualbox/vbox (verbose mode YES) (just checked this location on the flash drive and there is no folder "vbox" under /boot/config/plugins/virtualbox) (I added the folder "vbox" ..... not sure if this is needed) (after doing the below and watching the folder, nothing appeared in vbox....)
Starting VirtualBox plugin:
- Went to Dockers and Started Apache
- Went to Plugins and Clicked "Start vboxwebsrv"
- Opened a New Chrome Tab and went to http:\\tower/phpvb/ or IP Address/phpvb
- By the way I have no VM's running plenty of Ram and space, and once I start the above process, I have to use terminal to do a "PowerDown" this process locks up the gui screen and I can not gain access to any part of gui from any computer or from the screen connected to the tower.
At the very bottom of the Virtualbox plugin tab it says: "/opt/VirtualBox/VBoxManage setproperty websrvauthlibrary null vboxwebsrv service started"
I saw the phpVirtualbox GUI but it was light (still loading) after waiting five minutes or so I refreshed and then the light outline of the GUI shows for a second and then goes away and does not come back and I get the message:
"An error occurred communicating with your vboxwebsrv. No more requests will be sent by phpVirtualBox until the error is corrected and this page is refreshed. The details of this connection error should be displayed in a subsequent dialog box."
and the message:
"Could not connect to host (http://127.0.0.1:18083/)[code]
Exception Object ( [message:protected] => Could not connect to host (http://127.0.0.1:18083/) [string:Exception:private] => [code:protected] => 64 [file:protected] => /config/www/phpvb/endpoints/lib/vboxconnector.php [line:protected] => 220 [trace:Exception:private] => Array ( [0] => Array ( [file] => /config/www/phpvb/endpoints/lib/vboxconnector.php [line] => 5763 [function] => connect [class] => vboxconnector [type] => -> [args] => Array ( ) ) [1] => Array ( [file] => /config/www/phpvb/endpoints/lib/vboxconnector.php [line] => 951 [function] => remote_vboxGroupDefinitionsGet [class] => vboxconnector [type] => -> [args] => Array ( [0] => ) ) [2] => Array ( [file] => /config/www/phpvb/endpoints/api.php [line] => 316 [function] => __call [class] => vboxconnector [type] => -> [args] => Array ( [0] => vboxGroupDefinitionsGet [1] => Array ( [0] => [1] => Array ( [0] => Array ( [data] => Array ( [responseData] => Array ( ) ) [errors] => Array ( ) [persist] => Array ( ) [messages] => Array ( ) ) ) ) ) ) [3] => Array ( [file] => /config/www/phpvb/endpoints/api.php [line] => 316 [function] => vboxGroupDefinitionsGet [class] => vboxconnector [type] => -> [args] => Array ( [0] => [1] => Array ( [0] => Array ( [data] => Array ( [responseData] => Array ( ) ) [errors] => Array ( ) [persist] => Array ( ) [messages] => Array ( ) ) ) ) ) ) [previous:Exception:private] => ) Location:http://127.0.0.1:18083/[/code]
Here is the first several lines of my vboxwebsrv.log file:
VirtualBox web service 5.1.22 r115126 linux.amd64 (Apr 28 2017 16:59:05) release log
00:00:00.001416 main Log opened 2017-08-27T11:56:00.979746000Z
00:00:00.001419 main Build Type: release
00:00:00.001422 main OS Product: Linux
00:00:00.001423 main OS Release: 4.9.30-unRAID
00:00:00.001424 main OS Version: #1 SMP PREEMPT Fri May 26 13:56:36 PDT 2017
00:00:00.001467 main DMI Product Name: CYPRESS11
00:00:00.001477 main DMI Product Version: 1.0
00:00:00.001551 main Host RAM: 128913MB (125.8GB) total, 107021MB (104.5GB) available
00:00:00.001556 main Executable: /opt/VirtualBox/vboxwebsrv
00:00:00.001557 main Process ID: 83003
00:00:00.001558 main Package type: LINUX_64BITS_GENERIC
00:00:00.006024 main IPC socket path: /tmp/.vbox-root-ipc/ipcd
00:00:00.014135 main Pumping COM event queue
00:00:00.014159 main Pumping COM event queue
00:00:00.014250 Watchdog Watchdog thread started
00:00:00.014262 Watchdog Watchdog: sleeping 5 seconds
00:00:00.014963 SQPmp Socket connection successful: host = 127.0.0.1, port = 18083, master socket = 12
00:00:05.014420 Watchdog Watchdog: checking 0 websessions
00:00:05.014458 Watchdog Statistics: 0 websessions, 0 references
00:00:05.014474 Watchdog Watchdog: sleeping 5 seconds
00:00:10.014603 Watchdog Watchdog: checking 0 websessions
00:00:10.014656 Watchdog Watchdog: sleeping 5 seconds
00:00:15.014332 main Pumping COM event queue
00:00:15.014747 Watchdog Watchdog: checking 0 websessions
00:00:15.014772 Watchdog Watchdog: sleeping 5 secondsIt just repeats from here on out (checking and sleeping)
I feel I am close, but I just can't get it working. Any pointers would be greatly appreciated.
I am looking forward to using this!
EDIT: The VirtualBox Plugin page finally gave me the option (buttons) to Restart or shutdown virtualbox (but it took forever)
Thanks,
Albin
-
I cannot seem to get CrashPlan-Desktop to install.
When I first added the container I was thinking that I needed to do volume mapping. Then I saw ljm42 post
I don't think there is a one-size-fits-all configuration for CrashPlan server or desktop. I guess that is what makes troubleshooting the problem a bit different for everyone. Some combination of the solutions mentioned is this thread will likely help most, but, there does not seem to be one config to rule them all.
My config is working fine without the disks mapping but needed the .ui_info fix:
Remove the volume mapping for /config -> /mnt/cache/appdata/crashplan-desktop. that conflicts with --volumes-from CrashPlan
After removing the container and the image I tried again.
This time I I did not change anything after hitting add. I left the volume mapping empty I left the port mapping the way it was (Container 3389 > host 3389) and I had left the --volumes-from CrashPlan in the Extra Parameters section.
After hitting add I get the following:
Command:
root@localhost:# /usr/bin/docker run -d --name="CrashPlan-Desktop" --net="bridge" -e TZ="America/New_York" -p 3389:3389/tcp --volumes-from CrashPlan gfjardim/crashplan-desktop
time="2015-07-30T17:01:23-04:00" level=fatal msg="Error response from daemon: Could not apply volumes of non-existent container "CrashPlan"."
The command failed.
I am not sure what I am doing wrong. Are there unRaid settings that I need to change.
I am running 6.0.1
This is a fresh install of 6.0.1
My docker image is at the root of my cache drive mnt/cache/docker.img
I have my appdata on the cache drive as a cache only share mnt/usr/appdata
I deleted any share that I created specifically for crash plan during my first attempts.
Thanks for any advice.
Albin
Have you installed the CrashPlan docker (Not the Desktop version) You need both, CrashPlan is the service and the Desktop is just a conduit to configuring the CrashPlan docker.
Thanks for pointing me in the correct direction. I installed the crashplan service. Looks like things are working now. Thanks for your help!
-
I cannot seem to get CrashPlan-Desktop to install.
When I first added the container I was thinking that I needed to do volume mapping. Then I saw ljm42 post
I don't think there is a one-size-fits-all configuration for CrashPlan server or desktop. I guess that is what makes troubleshooting the problem a bit different for everyone. Some combination of the solutions mentioned is this thread will likely help most, but, there does not seem to be one config to rule them all.
My config is working fine without the disks mapping but needed the .ui_info fix:
Remove the volume mapping for /config -> /mnt/cache/appdata/crashplan-desktop. that conflicts with --volumes-from CrashPlan
After removing the container and the image I tried again.
This time I I did not change anything after hitting add. I left the volume mapping empty I left the port mapping the way it was (Container 3389 > host 3389) and I had left the --volumes-from CrashPlan in the Extra Parameters section.
After hitting add I get the following:
Command:
root@localhost:# /usr/bin/docker run -d --name="CrashPlan-Desktop" --net="bridge" -e TZ="America/New_York" -p 3389:3389/tcp --volumes-from CrashPlan gfjardim/crashplan-desktop
time="2015-07-30T17:01:23-04:00" level=fatal msg="Error response from daemon: Could not apply volumes of non-existent container "CrashPlan"."
The command failed.
I am not sure what I am doing wrong. Are there unRaid settings that I need to change.
I am running 6.0.1
This is a fresh install of 6.0.1
My docker image is at the root of my cache drive mnt/cache/docker.img
I have my appdata on the cache drive as a cache only share mnt/usr/appdata
I deleted any share that I created specifically for crash plan during my first attempts.
Thanks for any advice.
Albin
-
I decided to do a fresh install of unRAID. I figured I would move my data off the server and preclear all the drives. I was hoping for some input as to which drives I should consider retiring. I did preclear most of these at the same time. Any input wold be greatly appreciated.
Thanks,
Albin
I took at look at your smart reports and you can see my comments below.
The drive sizes of the drives included are as follows:
sda - 750G
sdb - 500G
sdd - 500G
sde - 750G
sdf - 1T
sdh - 500G
Honestly, expect the 1T drive, I'd recommend retiring the lot of them and replacing with a new 3T that can be had for less than $100. These are all getting rather old, and with so much larger drives available economically, it may be something to consider.
But that is me. If these drive sizes are working for you, I do believe at least some of them have some life left.
Many of the values of smart reports are not terribly useful, but the three I look at very closely are reallocated sectors, pending sectors, and temperature.
reallocated sectors are small parts of the disk surface that the drive has decided are incapable of reliably storing data. Once reallocated, it will never be un-reallocated. Drives should have 0 of these. Occasionally a small number can develop and not increase in number. This is fine. But if the value is trickling upward, this is a sign the drive is failing.
pending sectors are similar, except the jury is not out yet. They may get reallocated, or the drive may decide they are ok after all. Pending sectors are dangerous in that they can cause problems if rebuilding a failed disk. You didn't have any, but if you had, the recommendation would be to run more preclear cycles in an effort to get them to either reallocate or be marked good. Limbo is a bad place to be.
temperature is the only one you have control of. I don't like to see temps go above 42 or 43, but preclearing is a pretty stressful activity, and you might expect that this will be the max temp the drive will see in your array. Your temps on some drives are approaching but just under temps that I would highlight, but I am not marking that as an issue. If we were seeing temps over 45, and certainly if they got to 50, I'd be much more concerned.
The other attributes you are really looking at the "VALUE" column (on the preclear output you see it as "NEW_VAL") and comparing it to the "FAILURE_THRESHOLD" column. If the value is lower than the threshold, the drive will report "FAILING NOW" in the "STATUS" column. You don't have any of these, but they are bad. If the drive manufacturer, that is warrantying the drives, says it is failing, I never question it and get my data off it as fast as possible.
If you seen "near_thresh" in the status column, that is worth looking at. Means the attribute is getting close to the threshold. But there are some attributes that a certain value is normal, and dropping even one lower is failure. So if you see a value of 100 (which is a typical normal good "value" for an attribute), and a threshold of 99, I interpret that to mean it should always be 100, and not to be concerned unless it drops to 99. But if I see a value of 22, and a threshold of 21, or a value of 1 and a threshold of 0, I would be much more concerned.
Let me know if any questions on the information below:
1 sda
== ST3750330NS 9QK0D9WY == Disk /dev/sda has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 119 6 ok 120090706 Spin_Retry_Count = 100 100 97 near_thresh 8 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 60 64 45 near_thresh 40 Temperature_Celsius = 40 36 0 ok 40 Hardware_ECC_Recovered = 45 34 0 ok 120090706 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 1 sector had been re-allocated before the start of the preclear. 4 sectors are re-allocated at the end of the preclear, a change of 3 in the number of sectors re-allocated. =======================================================================
This drive has picked up 3 reallocated sectors during the preclear. Although 4 reallocated sectors is not itself a problem, often INCREASES in the reallocated sectors is a sign the drive is failing. I'd recommend doing a couple more preclear cycles. If the numbers hold steady for three preclears in a row, you are probably fine. But if the numbers trickle up every preclear or two, and you can't get to three in a row with the same value even after 5 or 6 preclears, I'd retire the drive or use it for non-critical purposes (like storing backup data you already store on your array).
2 sdb
== ST3500630NS 5QG1HKD0 == Disk /dev/sdb has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 66 68 45 near_thresh 34 Temperature_Celsius = 34 32 0 ok 34 Hardware_ECC_Recovered = 57 71 0 ok 8218259 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 1 sector had been re-allocated before the start of the preclear. 1 sector is re-allocated at the end of the preclear, the number of sectors re-allocated did not change. =======================================================================
This drive has 1 reallocated sector. This might have been like this for a very long time, or the 1 reallocation may have happened shortly before the preclear. Similar to sda above, I'd run a couple more preclears. If the 1 doesn't increase or you can get 3 preclears in a row where the number holds steady, keep it. Otherwise backup duty.
3 sdd
== ST3500630AS 9QG0GA2R == Disk /dev/sdd has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 56 62 45 near_thresh 44 Temperature_Celsius = 44 38 0 ok 44 Hardware_ECC_Recovered = 53 65 0 ok 7699123 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 114 sectors had been re-allocated before the start of the preclear. 114 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. =======================================================================
Same as sdb. 114, although a bit large, its not a big deal if the reallocations don't increase. It is surprising (but good) that it went a whole preclear cycle with no new ones.
4 sde
== ST3750640NS 5QD0ELXR == Disk /dev/sde has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 55 58 45 near_thresh 45 Temperature_Celsius = 45 42 0 ok 45 Hardware_ECC_Recovered = 62 65 0 ok 64838030 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. =======================================================================
No signs of failure.
5 sdf
== ST31000340AS 9QJ1VHF6 == Disk /dev/sdf has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 110 6 ok 183656712 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 61 62 45 near_thresh 39 Temperature_Celsius = 39 38 0 ok 39 Hardware_ECC_Recovered = 50 36 0 ok 183656712 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. =======================================================================
No signs of failure.
6 sdh
== SAMSUNGHD502IJ S1PZJDWQ669795 == Disk /dev/sdh has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 74 77 0 ok 26 Temperature_Celsius = 74 76 0 ok 26 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. =======================================================================
No signs of failure.
I ran 3 more cycles on sda sdb and sdd. There were no changes to the sectors re-allocated for these drives. (the numbers held steady)! I attached results for cycle 3 and 4.
1_sda_ST3750330NS___9QK0D9WY_Pass_3_and_4_no_new.txt
-
Thanks Bjp999
I appreciate you taking the time to reply. The information you provided was very helpful.
I am going to run more preclears on the drives you suggested. I will let you know what happens.
Thanks,
Albin
I took at look at your smart reports and you can see my comments below.
The drive sizes of the drives included are as follows:
sda - 750G
sdb - 500G
sdd - 500G
sde - 750G
sdf - 1T
sdh - 500G
Honestly, expect the 1T drive, I'd recommend retiring the lot of them and replacing with a new 3T that can be had for less than $100. These are all getting rather old, and with so much larger drives available economically, it may be something to consider.
But that is me. If these drive sizes are working for you, I do believe at least some of them have some life left.
Many of the values of smart reports are not terribly useful, but the three I look at very closely are reallocated sectors, pending sectors, and temperature.
reallocated sectors are small parts of the disk surface that the drive has decided are incapable of reliably storing data. Once reallocated, it will never be un-reallocated. Drives should have 0 of these. Occasionally a small number can develop and not increase in number. This is fine. But if the value is trickling upward, this is a sign the drive is failing.
pending sectors are similar, except the jury is not out yet. They may get reallocated, or the drive may decide they are ok after all. Pending sectors are dangerous in that they can cause problems if rebuilding a failed disk. You didn't have any, but if you had, the recommendation would be to run more preclear cycles in an effort to get them to either reallocate or be marked good. Limbo is a bad place to be.
temperature is the only one you have control of. I don't like to see temps go above 42 or 43, but preclearing is a pretty stressful activity, and you might expect that this will be the max temp the drive will see in your array. Your temps on some drives are approaching but just under temps that I would highlight, but I am not marking that as an issue. If we were seeing temps over 45, and certainly if they got to 50, I'd be much more concerned.
The other attributes you are really looking at the "VALUE" column (on the preclear output you see it as "NEW_VAL") and comparing it to the "FAILURE_THRESHOLD" column. If the value is lower than the threshold, the drive will report "FAILING NOW" in the "STATUS" column. You don't have any of these, but they are bad. If the drive manufacturer, that is warrantying the drives, says it is failing, I never question it and get my data off it as fast as possible.
If you seen "near_thresh" in the status column, that is worth looking at. Means the attribute is getting close to the threshold. But there are some attributes that a certain value is normal, and dropping even one lower is failure. So if you see a value of 100 (which is a typical normal good "value" for an attribute), and a threshold of 99, I interpret that to mean it should always be 100, and not to be concerned unless it drops to 99. But if I see a value of 22, and a threshold of 21, or a value of 1 and a threshold of 0, I would be much more concerned.
Let me know if any questions on the information below:
1 sda
== ST3750330NS 9QK0D9WY == Disk /dev/sda has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 119 6 ok 120090706 Spin_Retry_Count = 100 100 97 near_thresh 8 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 60 64 45 near_thresh 40 Temperature_Celsius = 40 36 0 ok 40 Hardware_ECC_Recovered = 45 34 0 ok 120090706 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 1 sector had been re-allocated before the start of the preclear. 4 sectors are re-allocated at the end of the preclear, a change of 3 in the number of sectors re-allocated. =======================================================================
This drive has picked up 3 reallocated sectors during the preclear. Although 4 reallocated sectors is not itself a problem, often INCREASES in the reallocated sectors is a sign the drive is failing. I'd recommend doing a couple more preclear cycles. If the numbers hold steady for three preclears in a row, you are probably fine. But if the numbers trickle up every preclear or two, and you can't get to three in a row with the same value even after 5 or 6 preclears, I'd retire the drive or use it for non-critical purposes (like storing backup data you already store on your array).
2 sdb
== ST3500630NS 5QG1HKD0 == Disk /dev/sdb has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 66 68 45 near_thresh 34 Temperature_Celsius = 34 32 0 ok 34 Hardware_ECC_Recovered = 57 71 0 ok 8218259 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 1 sector had been re-allocated before the start of the preclear. 1 sector is re-allocated at the end of the preclear, the number of sectors re-allocated did not change. =======================================================================
This drive has 1 reallocated sector. This might have been like this for a very long time, or the 1 reallocation may have happened shortly before the preclear. Similar to sda above, I'd run a couple more preclears. If the 1 doesn't increase or you can get 3 preclears in a row where the number holds steady, keep it. Otherwise backup duty.
3 sdd
== ST3500630AS 9QG0GA2R == Disk /dev/sdd has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 56 62 45 near_thresh 44 Temperature_Celsius = 44 38 0 ok 44 Hardware_ECC_Recovered = 53 65 0 ok 7699123 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 114 sectors had been re-allocated before the start of the preclear. 114 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. =======================================================================
Same as sdb. 114, although a bit large, its not a big deal if the reallocations don't increase. It is surprising (but good) that it went a whole preclear cycle with no new ones.
4 sde
== ST3750640NS 5QD0ELXR == Disk /dev/sde has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 55 58 45 near_thresh 45 Temperature_Celsius = 45 42 0 ok 45 Hardware_ECC_Recovered = 62 65 0 ok 64838030 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. =======================================================================
No signs of failure.
5 sdf
== ST31000340AS 9QJ1VHF6 == Disk /dev/sdf has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 110 6 ok 183656712 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 61 62 45 near_thresh 39 Temperature_Celsius = 39 38 0 ok 39 Hardware_ECC_Recovered = 50 36 0 ok 183656712 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. =======================================================================
No signs of failure.
6 sdh
== SAMSUNGHD502IJ S1PZJDWQ669795 == Disk /dev/sdh has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 74 77 0 ok 26 Temperature_Celsius = 74 76 0 ok 26 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. =======================================================================
No signs of failure.
-
I decided to do a fresh install of unRAID. I figured I would move my data off the server and preclear all the drives. I was hoping for some input as to which drives I should consider retiring. I did preclear most of these at the same time. Any input wold be greatly appreciated.
Thanks,
Albin
1 sda ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sda = cycle 1 of 1, partition start on sector 63 = 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 = Disk Post-Clear-Read completed DONE Disk Temperature: 40C, Elapsed Time: 19:01:52 ========================================================================1.15 == ST3750330NS 9QK0D9WY == Disk /dev/sda has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sda /tmp/smart_finish_sda ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 117 119 6 ok 120090706 Spin_Retry_Count = 100 100 97 near_thresh 8 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 60 64 45 near_thresh 40 Temperature_Celsius = 40 36 0 ok 40 Hardware_ECC_Recovered = 45 34 0 ok 120090706 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 1 sector had been re-allocated before the start of the preclear. 4 sectors are re-allocated at the end of the preclear, a change of 3 in the number of sectors re-allocated. =======================================================================END sda 2 sdb ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdb = cycle 1 of 1, partition start on sector 63 = 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 = Disk Post-Clear-Read completed DONE Disk Temperature: 34C, Elapsed Time: 14:16:15 ========================================================================1.15 == ST3500630NS 5QG1HKD0 == Disk /dev/sdb has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdb /tmp/smart_finish_sdb ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 66 68 45 near_thresh 34 Temperature_Celsius = 34 32 0 ok 34 Hardware_ECC_Recovered = 57 71 0 ok 8218259 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 1 sector had been re-allocated before the start of the preclear. 1 sector is re-allocated at the end of the preclear, the number of sectors re-allocated did not change. =======================================================================END sdb 3 sdd ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdd = cycle 1 of 1, partition start on sector 63 = 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 = Disk Post-Clear-Read completed DONE Disk Temperature: 44C, Elapsed Time: 14:09:42 ========================================================================1.15 == ST3500630AS 9QG0GA2R == Disk /dev/sdd has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdd /tmp/smart_finish_sdd ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 56 62 45 near_thresh 44 Temperature_Celsius = 44 38 0 ok 44 Hardware_ECC_Recovered = 53 65 0 ok 7699123 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 0 sectors are pending re-allocation at the end of the preclear, the number of sectors pending re-allocation did not change. 114 sectors had been re-allocated before the start of the preclear. 114 sectors are re-allocated at the end of the preclear, the number of sectors re-allocated did not change. =======================================================================END sdd 4 sde ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sde = cycle 1 of 1, partition start on sector 63 = 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 = Disk Post-Clear-Read completed DONE Disk Temperature: 45C, Elapsed Time: 18:32:23 ========================================================================1.15 == ST3750640NS 5QD0ELXR == Disk /dev/sde has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sde /tmp/smart_finish_sde ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Spin_Retry_Count = 100 100 97 near_thresh 0 Airflow_Temperature_Cel = 55 58 45 near_thresh 45 Temperature_Celsius = 45 42 0 ok 45 Hardware_ECC_Recovered = 62 65 0 ok 64838030 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. =======================================================================END sde 5 sdf ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdf = cycle 1 of 1, partition start on sector 63 = 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 = Disk Post-Clear-Read completed DONE Disk Temperature: 39C, Elapsed Time: 22:37:55 ========================================================================1.15 == ST31000340AS 9QJ1VHF6 == Disk /dev/sdf has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdf /tmp/smart_finish_sdf ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE Raw_Read_Error_Rate = 118 110 6 ok 183656712 Spin_Retry_Count = 100 100 97 near_thresh 0 End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 61 62 45 near_thresh 39 Temperature_Celsius = 39 38 0 ok 39 Hardware_ECC_Recovered = 50 36 0 ok 183656712 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. =======================================================================END sdf 6 sdh ================================================================== 1.15 = unRAID server Pre-Clear disk /dev/sdh = cycle 1 of 1, partition start on sector 63 = 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 = Disk Post-Clear-Read completed DONE Disk Temperature: 26C, Elapsed Time: 16:30:41 ========================================================================1.15 == SAMSUNGHD502IJ S1PZJDWQ669795 == Disk /dev/sdh has been successfully precleared == with a starting sector of 63 ============================================================================ ** Changed attributes in files: /tmp/smart_start_sdh /tmp/smart_finish_sdh ATTRIBUTE NEW_VAL OLD_VAL FAILURE_THRESHOLD STATUS RAW_VALUE End-to-End_Error = 100 100 99 near_thresh 0 Airflow_Temperature_Cel = 74 77 0 ok 26 Temperature_Celsius = 74 76 0 ok 26 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 1. 0 sectors were pending re-allocation after zero of disk in cycle 1 of 1. 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. =======================================================================END sdh
-
I can't remember if I discovered that I had a bad memory stick before or after I ran the preclear. Could this would have caused bad results (if the bad stick was still in the machine)? Regardless, I am waiting for the new memory sticks to arrive, and then I am going to run the test again. Should I run the test with all the drives connected to the same slots, and review the results (maybe there is a chance the results would be different.... I am not sure how memory is allocated during the testing prior.... maybe sdd got allocated bad sections of memory? I am Totally guessing on this). Then if I get similar results to those posted, I could switch the drives around (different slots), and see what type of results I get.
I don't see any connection with memory here. I'll just add though that if I have any suspicions at all about the memory of a computer, then I consider that computer to be completely unusable! Period. When you get the new memory sticks, test them with memtest overnight, until you are completely confident in them.
By the way all the drives are connected to on board SATA slots. My first thought is that they should all have similar band widths, but maybe certain slots are designed, or are designated for higher bandwidth.
That pretty well rules out bandwidth differences, unless there was an issue with that specific port or cable. You might try preclearing the slow drive one more time connected to the cable and port used by one of the faster drives. And if you have the syslog during the slow drives preclear, check it for any drive-related errors/exceptions.
Rob,
I got the new memory in and then ran memtest for over night. I then ran a preclear on the same drives in the same slot. I got the same results as the reports I previously provided. I then switched moved the drive in sdd (the slowest drive) to sda and moved the drive in sda (the fastest drive) to sdd. I then ran the preclear again and I got similar results (the slowest drive was still finished 2 hours later) So it seems it is not a cable or slot issue.
I attached all three runs of the slow drive (Z2F0KS4Z) and one report of the fast drive (Z1E2EQXS) when it was on slot sdd.
I am not sure that I will use a speed test tool a 2 hour difference over a 24 hour preclear is not much, and I am guessing that the difference will not be that noticeable. I will put the fastest drive in the parity slot.
Albin
Z2F0KS4Z_sdd_new_mem_2013-01-15.txt
-
I can't remember if I discovered that I had a bad memory stick before or after I ran the preclear. Could this would have caused bad results (if the bad stick was still in the machine)? Regardless, I am waiting for the new memory sticks to arrive, and then I am going to run the test again. Should I run the test with all the drives connected to the same slots, and review the results (maybe there is a chance the results would be different.... I am not sure how memory is allocated during the testing prior.... maybe sdd got allocated bad sections of memory? I am Totally guessing on this). Then if I get similar results to those posted, I could switch the drives around (different slots), and see what type of results I get.
I don't see any connection with memory here. I'll just add though that if I have any suspicions at all about the memory of a computer, then I consider that computer to be completely unusable! Period. When you get the new memory sticks, test them with memtest overnight, until you are completely confident in them.
By the way all the drives are connected to on board SATA slots. My first thought is that they should all have similar band widths, but maybe certain slots are designed, or are designated for higher bandwidth.
That pretty well rules out bandwidth differences, unless there was an issue with that specific port or cable. You might try preclearing the slow drive one more time connected to the cable and port used by one of the faster drives. And if you have the syslog during the slow drives preclear, check it for any drive-related errors/exceptions.
Rob,
Very helpful information... thanks. I will test the Memory sticks with memtest and when comfortable I will move forward with test as yoiu recommended for the drives.
Albin
-
I just did a preclear on (3) Seagate ST2000DM001-1CH164.
I ran the preclear on each drive at the same time (start time was only seconds apart)
2 of the drives sda and sdc were neck and neck the whole time (about 10 min total difference in run time)
sdd was over 2 hours of difference.
I got these drives from newegg and I was not impressed with the way they were packed so I may be over concerned about difference between the reports but sdd has a very big difference in the Seek_Error_Rate 8590654534 compared to the other drives at 745946 and 751820. I am not sure if this value is critical or not.
I also was not sure if this type reading may be do to a data or power cable.
I'll start by saying that all 3 drives look fine, no issues at all.
For the following, ignore the temperature SMART attributes (190 and 194), they have their own interpretation rules. For the rest, you should not look at the Raw numbers for most SMART attributes, just the VALUE column (and perhaps the WORST column), which are an attempt by the manufacturer to indicate its own valuation of the numbers. Generally the VALUE's will be from 1 to 100, but often they may be from 1 to 200, or even for a few Maxtors 1 to 253 (the 200's can be halved and considered as 100's). That means you can generally think of them as percentages of perfect, as in 100 is considered factory perfect and 1 is bottomed-out bad and 50 is probably not very good. So even though a Raw_Read_Error_Rate may have a very high raw number, if its VALUE is 100, then the drive manufacturer considers its read error rate to be perfectly normal. I think we look too fast at the raw numbers, most of them should be ignored. We should look first at all the 100's and/or 200's in the VALUE and WORST columns.
As to a possible cable issue, I see no evidence of that. Would need the corresponding syslog to know for sure.
From here on, I'm moving from factual to speculative, trying to come up with ideas why one drive performed somewhat slower, even though all 3 drives were identical, and had the same firmware version. The most likely reason is that different controller chipsets or busses were involved, and the slow drive was stuck with the slower hardware, was bullied out of a fair share of the I/O bandwidth available. You could verify this by swapping its connection with one of the fast drives, and retesting.
But since we're already speculating ... we'll drift a little farther out in left field. All 3 SMART reports were essentially identical, as would be expected by identical drives. But there were 2 odd differences, one was that the slow drive had a far higher SEEK_ERROR_RATE raw number (which we should normally ignore!), and the other was that the slow drive reported a much longer time needed for offline data collection, a fact that is really strange for identical drives! The fast drives sda and sdc reported they only need 80 seconds for offline data collection. The slow drive sdd reports it needs 139 seconds! I don't want to put too much importance on that, since the manufacturers do not provide any info on properly interpreting these numbers, but it does seem very odd, and perhaps indicative of a slower drive. And while I really don't want to draw any conclusions from the SEEK_ERROR_RATE raw number, it plausibly *may* represent the need for many more seeks than the other drives, and seeks are relatively slow actions. You might want to run a drive speed testing tool (HDTune?) on both the slow drive and a fast drive, and compare.
Now for some crazy speculation... Manufacturers like to cut corners. What if, to make 1TB, 2TB, 3TB, and 4TB drives, they just set up production lines for 4TB platter sets, and then when factory testing them, sell the partially defective ones as smaller drives. So if one cannot support 4TB, determine how much it CAN support and sell it accordingly. Now, what if a platter set had a bad region only in the faster tracks, but had 3TB available in the slower tracks? You would create a good 3TB drive, but it would be significantly slower than the average 3TB drive. No easy way to know for sure...
Rob,
Thanks for your reply / post.
I can't remember if I discovered that I had a bad memory stick before or after I ran the preclear. Could this would have caused bad results (if the bad stick was still in the machine)? Regardless, I am waiting for the new memory sticks to arrive, and then I am going to run the test again. Should I run the test with all the drives connected to the same slots, and review the results (maybe there is a chance the results would be different.... I am not sure how memory is allocated during the testing prior.... maybe sdd got allocated bad sections of memory? I am Totally guessing on this). Then if I get similar results to those posted, I could switch the drives around (different slots), and see what type of results I get.
By the way all the drives are connected to on board SATA slots. My first thought is that they should all have similar band widths, but maybe certain slots are designed, or are designated for higher bandwidth.
Albin
-
both look fine
Just checking to see if you were replying to both of usurpator's reports, all three of my reports, or both usurpator and I at the same time.
Thanks
Albin
-
Joe thanks for the up to date preclear.sh tool!
I just did a preclear on (3) Seagate ST2000DM001-1CH164.
I ran the preclear on each drive at the same time (start time was only seconds apart)
2 of the drives sda and sdc were neck and neck the whole time (about 10 min total difference in run time)
sdd was over 2 hours of difference.
This is my first time using the preclear method (I should have done this on all my previous drives, but I just learned about this).
I got these drives from newegg and I was not impressed with the way they were packed so I may be over concerned about difference between the reports but sdd has a very big difference in the Seek_Error_Rate 8590654534 compared to the other drives at 745946 and 751820. I am not sure if this value is critical or not.
I also was not sure if this type reading may be do to a data or power cable.
Thanks for any input on these reports.
Albin
sdd_preclear_rpt__Z2F0KS4Z_2013-01-05.txt
[SOLVED] - VM Mover - Storing VM off cache drive
in General Support
Posted
Perfectly explained. I really appreciate it. I was over thinking this. Now I need to get the dev devices converted over to images so the VM tab loads faster, and I can get rid of all those error showing in the libvirt log.
Thanks again.