Tom2000

Found the problem is on the RAM. Upgrade from 1G to 2G solved the problem. Here is the error when upgrading to 6.5 tom@Hydra:/tmp$ cat unraid_error plugin: installing: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer.plg plugin: downloading https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer.plg plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer.plg ... done plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.5.1-x86_64.zip ... done plugin: downloading: https://s3.amazonaws.com/dnld.lime-technology.com/stable/unRAIDServer-6.5.1-x86_64.md5 ... done Archive: /tmp/unRAIDServer.zip creating: /tmp/unRAIDServer/EFI-/ creating: /tmp/unRAIDServer/EFI-/boot/ inflating: /tmp/unRAIDServer/EFI-/boot/bootx64.efi inflating: /tmp/unRAIDServer/EFI-/boot/ldlinux.e64 inflating: /tmp/unRAIDServer/EFI-/boot/libcom32.c32 inflating: /tmp/unRAIDServer/EFI-/boot/libutil.c32 inflating: /tmp/unRAIDServer/EFI-/boot/mboot.c32 inflating: /tmp/unRAIDServer/EFI-/boot/menu.c32 inflating: /tmp/unRAIDServer/EFI-/boot/syslinux.cfg inflating: /tmp/unRAIDServer/bzfirmware inflating: /tmp/unRAIDServer/bzimage inflating: /tmp/unRAIDServer/bzmodules inflating: /tmp/unRAIDServer/bzroot unzip error 0 plugin: run failed: /bin/bash retval: 1

I haven't kept up with the upgrade and realized that the version I am running is way behind. What is the best way to upgrade the system to the latest and stable version? Read the wiki and forum, but couldn't find a good answer yet. Thanks, --Tom

Hi Joe, The preclear_disk.sh script finally completed one cycle and below is the result. I suppose it is OK, right? Thanks, --Tom =========================================================================== = unRAID server Pre-Clear disk /dev/sdj = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Disk Post-Clear-Read completed DONE Elapsed Time: 14:36:38 ============================================================================ == == Disk /dev/sdj has been successfully precleared == ============================================================================ S.M.A.R.T. error count differences detected after pre-clear note, some 'raw' values may change, but not be an indication of a problem 71c71 < 190 Airflow_Temperature_Cel 0x0022 075 075 000 Old_age Always - 25 (Lifetime Min/Max 25/26) --- > 190 Airflow_Temperature_Cel 0x0022 072 072 000 Old_age Always - 28 (Lifetime Min/Max 25/28) 77c77 < 200 Multi_Zone_Error_Rate 0x000a 253 253 000 Old_age Always - 0 --- > 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 ============================================================================

Hi Joe, Thanks again for the explanations. Those are good notes that I will keep to maintain my unRAID server. I am still waiting for preclear_disk.sh script to finish and will update later on. --Tom

Hi Joe, Thanks for the analysis. Please see below for the smartctl command output and it seems to be fine to me. I did the hot-plug on the external SATA cable.Thanks for pointing out that to me since I did not know I am not supposed to do that. I am using putty to connect to unRAID server. Whenever I execute the command "preclear_disk.sh -t /dev/sdk", the session just terminated right away. I think I will go ahead stop the array and restart the server, and then run the preclear_disk.sh again. Thanks, --Tom ------------------------------------------------------------------------ root@Tower:~# smartctl -d ata -a /dev/sdk smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD154UI Serial Number: S1Y6J1KS744099 Firmware Version: 1AG01118 User Capacity: 1,500,301,910,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Fri Aug 21 12:44:04 2009 Local time zone must be set--see zic m ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (19393) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 34) minutes. SCT capabilities: (0x003f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 100 100 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 071 071 011 Pre-fail Always - 9640 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 4 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 10 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 4 13 Read_Soft_Error_Rate 0x000e 100 100 000 Old_age Always - 0 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 184 Unknown_Attribute 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 075 075 000 Old_age Always - 25 (Lifetime Min/Max 25/26) 194 Temperature_Celsius 0x0022 075 075 000 Old_age Always - 25 (Lifetime Min/Max 25/27) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 223195953 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 253 253 000 Old_age Always - 5 200 Multi_Zone_Error_Rate 0x000a 253 253 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 100 100 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

Hi, I think this should be the right thread to post my question. I just purchased two 1.5 TB Samsung SATA drives and tried to use the preclear.sh script to prepare the HD. What I normally do is to connect the HD to the external SATA port on the system and ran though the preclear.sh scripts one disk at a time. Unfortunately Both of them returned the same unsuccessful results, which shows below. =========================================================================== = unRAID server Pre-Clear disk /dev/sdk = cycle 1 of 1 = Disk Pre-Clear-Read completed DONE = Step 1 of 10 - Copying zeros to first 2048k bytes DONE = Step 2 of 10 - Copying zeros to remainder of disk to clear it DONE = Step 3 of 10 - Disk is now cleared from MBR onward. DONE = Step 4 of 10 - Clearing MBR bytes for partition 2,3 & 4 DONE = Step 5 of 10 - Clearing MBR code area DONE = Step 6 of 10 - Setting MBR signature bytes DONE = Step 7 of 10 - Setting partition 1 to precleared state DONE = Step 8 of 10 - Notifying kernel we changed the partitioning DONE = Step 9 of 10 - Creating the /dev/disk/by* entries DONE = Step 10 of 10 - Testing if the clear has been successful. DONE = Elapsed Time: 7:56:59 ============================================================================ == == SORRY: Disk /dev/sdk MBR could NOT be precleared == ============================================================================ 0+0 records in 0+0 records out 0 bytes (0 B) copied, 2.8617e-05 s, 0.0 kB/s 0000000 The only difference is that when I ran the first HD, the syslog was filled up with the following message like 600MB. I then deleted the syslog and do a touch command to created a new syslog. I then ran the preclear.sh on my second drives and the syslog remains size of 0. Aug 20 03:37:23 Tower kernel: end_request: I/O error, dev sdk, sector 32563752 Aug 20 03:37:23 Tower kernel: sd 9:0:0:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00 Aug 20 03:37:23 Tower kernel: end_request: I/O error, dev sdk, sector 32579816 Aug 20 03:37:23 Tower kernel: sd 9:0:0:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00 Aug 20 03:37:23 Tower kernel: end_request: I/O error, dev sdk, sector 32595880 Aug 20 03:37:23 Tower kernel: sd 9:0:0:0: [sdk] Result: hostbyte=0x04 driverbyte=0x00 Aug 20 03:37:23 Tower kernel: end_request: I/O error, dev sdk, sector 32611944 With the message such as "SORRY: Disk /dev/sdk MBR could NOT be precleared", does it imply that both of my HD are defect? I appreciate if anyone can chime-in what I should do next? --Tom

Hi Joe, Thanks for your reply. I have re-installed the drive in the enclosure, but it seems to be behave the same. Since I have only one SATA enclosure and cable, I might just installed the drive in the system and run the preclear_disk.sh again. I ran a smartctl -H against it and failed: -------------------- root@Tower:/boot/packages# smartctl -H /dev/sdg smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ Short INQUIRY response, skip product id A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. ------------------ I ran another "smartctl -al"l command and here is the result: ---------------- root@Tower:/boot/packages# smartctl --all /dev/sdg smartctl version 5.38 [i486-slackware-linux-gnu] Copyright © 2002-8 Bruce Allen Home page is http://smartmontools.sourceforge.net/ === START OF INFORMATION SECTION === Device Model: SAMSUNG HD103UJ Serial Number: S13PJ9DS302065 Firmware Version: 1AA01113 User Capacity: 1,000,204,886,016 bytes Device is: In smartctl database [for details use: -P show] ATA Version is: 8 ATA Standard is: ATA-8-ACS revision 3b Local Time is: Thu Mar 26 12:26:15 2009 Local time zone must be set--see zic m ==> WARNING: May need -F samsung or -F samsung2 enabled; see manual for details. SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x00) Offline data collection activity was never started. Auto Offline Data Collection: Disabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (11788) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 197) minutes. Conveyance self-test routine recommended polling time: ( 21) minutes. SCT capabilities: (0x003f) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0007 078 078 011 Pre-fail Always - 7590 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 11 5 Reallocated_Sector_Ct 0x0033 100 100 010 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 253 253 051 Pre-fail Always - 0 8 Seek_Time_Performance 0x0025 100 100 015 Pre-fail Offline - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 0 10 Spin_Retry_Count 0x0033 100 100 051 Pre-fail Always - 0 11 Calibration_Retry_Count 0x0012 100 100 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 11 13 Read_Soft_Error_Rate 0x000e 253 253 000 Old_age Always - 0 183 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 184 Unknown_Attribute 0x0033 100 100 000 Pre-fail Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Unknown_Attribute 0x0032 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 078 077 000 Old_age Always - 22 (Lifetime Min/Max 22/22) 194 Temperature_Celsius 0x0022 078 077 000 Old_age Always - 22 (Lifetime Min/Max 22/22) 195 Hardware_ECC_Recovered 0x001a 100 100 000 Old_age Always - 405 196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 099 099 000 Old_age Always - 3 200 Multi_Zone_Error_Rate 0x000a 100 100 000 Old_age Always - 0 201 Soft_Read_Error_Rate 0x000a 253 253 000 Old_age Always - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. root@Tower:/boot/packages# ------------------------------- Thanks, --Tom

Hi, I am running unRAID pro version 4.4 and ran into problem tonight. I just purchased two 1TG hard disk. One is Western Digital WD10EADS and the other one is Samsung Spinpoint F1 HD103UJ. I use the preclear_disk.sh script to clear WD hard drive yesterday and it was running smoothly and finished today for two rounds. Then today before I ran the preclear_disk.sh script on Samsung, I have the problem of two disks showing unformatted. I searched the forum and installed the powerdown scripts. After rebooting the server, I started to run the preclear_disk.sh script on Samsung and encounter the following problems: 1. The preclear_disk.sh script complain that some libraries from smartctl can not be found, so I re-install the cxxlibs-6.0.8-i486-4.tgz package again. It seems to me that I need to re-install the package if I reboot the server. Is it right? 2. There are tons of error showing in the syslog and actually make the unRaid system not functional. I am no longer able to copy or delete files in the system. I think that is due to the continuous error on the system. Here are the messages which repeat like crazy in the syslog. Mar 26 03:20:56 Tower kernel: sd 7:0:0:0: [sdg] Result: hostbyte=0x04 driverbyte=0x00 Mar 26 03:20:56 Tower kernel: end_request: I/O error, dev sdg, sector 1953520064 Mar 26 03:20:56 Tower kernel: sd 7:0:0:0: [sdg] Result: hostbyte=0x04 driverbyte=0x00 Mar 26 03:20:56 Tower kernel: end_request: I/O error, dev sdg, sector 1953520064 I put the new disk in an enclosure and run the disk to the external SATA port on the machine. I want to clear the disk first before actually installing in the system. I thought it might be a problem on the physical drive, so I connect the hard drive to my Window XP laptop via the USB port. Then I partition and format the drive. It runs oK and I also copied a few files in the disk. I deleted a lot of error message on the syslog to make it smaller size. The syslog is attached in this post. Please take a look at the log and let me know how I can fix the problem. Your help is very much appreciated. --Tom

Hi Joe, Those few commands are exactly what I needed. Thanks so much for the clear and prompt reply. Now my pre-clear process is about a few percentage into the process. Once it is done and hopefully no error (may be more than 10 hours), I will replace the current parity drive with this drive. Happy New Year! --Tom

Hi Joe, Thanks for your prompt reply. How do I know the correct device name? --Tom

Hi Joel, Is there any procedure to run the script with a brand new drive? As to mount the drive first or any other thing I need to do from the unRAID management WEB interface? I have just receive my new 1TB drive and want to use your script to break-in the drive before I put it into my system as the parity drive. Currently I have one 1 TB drive and a few 500 G drives in my system. Since it is supposed to be a faster drive, I want it to be my parity drive. Now I put the hard drive in an enclosure and connect to e-SATA port on my unRAID server. Here is my current drive status: root@Tower:/boot/download# mount fusectl on /sys/fs/fuse/connections type fusectl (rw) usbfs on /proc/bus/usb type usbfs (rw) /dev/sdg1 on /boot type vfat (rw,umask=066,shortname=mixed) /dev/md3 on /mnt/disk3 type reiserfs (rw,noatime,nodiratime) /dev/md1 on /mnt/disk1 type reiserfs (rw,noatime,nodiratime) /dev/md5 on /mnt/disk5 type reiserfs (rw,noatime,nodiratime) /dev/md6 on /mnt/disk6 type reiserfs (rw,noatime,nodiratime) /dev/md4 on /mnt/disk4 type reiserfs (rw,noatime,nodiratime) /dev/md2 on /mnt/disk2 type reiserfs (rw,noatime,nodiratime) shfs on /mnt/user type fuse.shfs (rw,nosuid,nodev) Thanks, --Tom