goinsnoopin

For the Parity I get this: Smartctl open device: /dev/sda failed: No such device Disk 7 Smart Report: I get this (the /dev/sba: Smartctl open device: /dev/sdb failed: No such device I tried to browse disk7 and I can't get any files to open??? Disk 5 Smart Report: Statistics for /dev/sdc WDC_WD10EARS-00Y_WD-WCAV56190116 smartctl -a -d ata /dev/sdc smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD10EARS-00Y5B1 Serial Number: WD-WCAV56190116 Firmware Version: 80.00A80 User Capacity: 1,000,204,886,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Wed Sep 5 18:06:04 2012 EDT 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: FAILED! Drive failure expected in less than 24 hours. SAVE ALL DATA. See vendor-specific Attribute list for failed Attributes. General SMART Values: Offline data collection status: (0x82) Offline data collection activity was completed without error. Auto Offline Data Collection: Enabled. Self-test execution status: ( 73) The previous self-test completed having a test element that failed and the test element that failed is not known. Total time to complete Offline data collection: (18960) 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: ( 219) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x3031) 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 0x002f 197 197 051 Pre-fail Always - 64859 3 Spin_Up_Time 0x0027 126 121 021 Pre-fail Always - 6666 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2248 5 Reallocated_Sector_Ct 0x0033 097 097 140 Pre-fail Always FAILING_NOW 818 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 074 074 000 Old_age Always - 19348 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 66 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 26 193 Load_Cycle_Count 0x0032 151 151 000 Old_age Always - 148296 194 Temperature_Celsius 0x0022 117 114 000 Old_age Always - 30 196 Reallocated_Event_Count 0x0032 001 001 000 Old_age Always - 783 197 Current_Pending_Sector 0x0032 193 193 000 Old_age Always - 1235 198 Offline_Uncorrectable 0x0030 200 198 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 032 000 Old_age Offline - 19 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed: unknown failure 90% 19348 - 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.

I had a parity drive failure in mid August. I RMAed the drive, replaced it and then recalculated parity from my data drives. All of this happened without any issues. On 9/1/12 unmenu ran its scheduled monthly parity check. I was getting hourly email notifications and noticed it was taking a long time...at one point I noticed that the parity check was going at 20 kb/s when I normally see 40,000 kb/s. At the time I was getting 20kb/s I remotely connected to my unraid server and pulled up the main user interface. At that time all drives were green, however I noticed disk5 had errors listed. I was on vacation so I did not have direct access to the server. Utimately the parity check finished however when it finished the parity drive was disabled and has the red dot next to it. Attached is a screenshot. I have a syslog however it is too large to attach. However, here is a link to the zipped syslog in my public dropbox folder: https://dl.dropbox.com/u/10262611/syslog-2012-09-05.zip Thanks, Dan

I forgot about the powerdown script....it saved the log automatically! I have attached a shortened version...similiar errors continued on an on for 274mb! This should give an idea of what happened. Dan syslog_shortened.txt

Thanks Joe...attached is the syslog. I realize that I did something stupid that I did not list in my first email....I did a restart of unraid after I got the blue parity ball...and I did not save the syslog before I restarted...big mistake I now realize... The syslog below is obviously what resulted after my restart. I will contact Tom and point him to this thread. syslog-2012-05-22.txt

So I have an issue. Unraid 4.7 I had disk 8 fail. I contacted WD and RMAed the drive (2 TB EARS). I received the WDEARX drive today and replaced disk8. Reassigned the new drive and started the array. The data rebuild was in progress and I got an update 1 hour into the process. I did not preclear the drive (possible mistake??) I normally do, but some of the data I lost was important and I wanted to recover it ASAP. At hour 2 I did not get an email update which I thought was odd. When I got home the unraid box had a kernel panic and would not accept any input from the keyboard. I power cycled the machine and at the time I was thinking about the 6gb/s capacity of the WDEARX drive versus the existing drive so I decided to put a jumper on pins 5 and 6 to set the WDEARX drive to 3 gb/s thinking this might have something to do with the issue. I then fired the machine back up and immediately the unraid webgui indicated the rebuild was in progress, however I saw a large volume of writes being made to the parity disk so I immediately stopped the parity rebuild. When I did this the disk 8 went back to missing and the parity turned blue. Any suggestions??? Thanks! Dan Edit: Tom Helped me out...thanks Tom!

One of my drives failed and I have a question. My system has 8 drives and one of them failed (disk 6). It looks like I need to order a new drive from newegg, so it will take a couple of days to get a new drive, preclear it and then rebuild the data from parity. So here is my question...can I continue to add new data to my array? Will the parity drive still be able to reproduce the data on this disk 6 if I continue to add new files to my other disks? Thanks, Dan

Thanks everyone. I purchased a new drive, precleared it and rebuilt parity so I am up and running again. I pulled the driver and installed it in a windows machine as Stephen suggested. The WD lifeguard diagnostic indicated that there were errors in the extended test. I called WD and got an RMA for the drive. Thanks for your help and suggestions. Dan

I have a WDEARS20 drive as my parity drive. Back in February I got a disk failure. At that time Joe L. suggested smart report, check cables, etc. which I did and found that the drive was O.k. Joe suggested that I powercycle the drive and rebuild parity, which I successfully did and it has been working fine until a couple of days ago. The drive is now doing the same thing. Smart report is good, cables are good, I powercycled and rebuilt parity, the array comes back up and several hours later the drive fails again. I have rebuilt it two times now...does anyone have any suggestions? Syslog attached. Thanks, Dan Please see my old post that was marked as solved for background: http://lime-technology.com/forum/index.php?topic=10982.msg104600#msg104600 syslog-2011-05-04.zip

Joe, I replaced the cable (just to be sure) restarted the array and let it rebuild parity. Everything went fine... no errors. Can I expect this to keep happening since you mention buggy firmware? Thanks for your help! Dan

Joe, I rebooted the unraid server - the parity drive shows as a blue dot and says new parity disk installed??? I then ran the smart disk command see below. Do you have any suggestions on how to move forward? Thanks, Dan smartctl -d ata -a /dev/sdi smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WMAZA3388631 Firmware Version: 51.0AB51 User Capacity: 2,000,398,934,016 bytes Device is: Not in smartctl database [for details use: -P showall] ATA Version is: 8 ATA Standard is: Exact ATA specification draft version not indicated Local Time is: Sun Feb 13 08:31:59 2011 EST 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: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. 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: (36480) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off supp ort. 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: ( 5) minutes. SCT capabilities: (0x3035) 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 0x002f 200 200 051 Pre-fail Always - 0 3 Spin_Up_Time 0x0027 220 162 021 Pre-fail Always - 4000 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 59 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 200 200 000 Old_age Always - 0 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 253 10 Spin_Retry_Count 0x0032 100 253 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 14 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 11 193 Load_Cycle_Count 0x0032 200 200 000 Old_age Always - 481 194 Temperature_Celsius 0x0022 129 120 000 Old_age Always - 21 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 200 000 Old_age Offline - 0 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 No self-tests have been logged. [To run self-tests, use: smartctl -t] SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay.

Joe, I will check/replace the cable. Here is the results from the SMART report: root@Tower:~# smartctl -d ata -a /dev/sdi smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright © 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T perm issive' options.

I completed my upgrade to 4.7 on 2/8/11. As part of the upgrade I replaced my old WD black 1Tb parity drive with a new 2.0TB WD Ears drive. I ran preclear.sh with the -A switch before installing and rebuilding. The new drive rebuilt parity and a successful parity check was completed after the data rebuild. Today at 11:09am in the syslog that is attached you will see the start of the errors. Can someone view my syslog and let me know what they think is wrong and how I should proceed? Thanks, Dan syslog-2011-02-12.zip

I just successfully replaced my parity drive, rebuilt parity and performed a parity check with no errors. How long should I wait before I preclear the old parity drive and use it to replace one of my other data drives? Or is there anything else I should do or test before preclearing the old parity drive? Thanks, Dan

Joe, Thanks for the help! I made the changes you suggested, rebuilt the data, ran a parity check afterwards, upgraded to 4.7...no issues this time and ran another successful parity check. I checked the syslog and I no longer see any reference to hpa so I think I am all set and am off to replace my parity drive with a 2TB WD EARS. Thanks again! Dan

Joe, I am using the unofficial supermicro C2SEE motherboard...I didn't think that had the HPA issues like the gigabyte boards have. The only gigabyte board I have ever owned is in my current desktop... I can not remember it this drive was ever installed on it. I just did a parity check before the attempted 4.7 upgrade and I had no errors. Please confirm that the HPA issue can not come from the supermicro board...if this is the case can I just run the hdparm command? Thanks, Dan

I just upgraded to 4.7 and have a problem. Disk 6 shows up with a red dot, says replacement disk is too small and therefore the array does not start. The odd think is the size is off by 4. Please note this is a regular sata drive and not an advanced format drive. I have attached the syslog and screenshot. I reverted to 4.6 and disk 6 has a green dot, the array starts and everything works fine. Does anyone have any ideas on how to proceed? I want to get to 4.7 to install a new 2TB parity drive. Thanks, Dan syslog-2011-01-28.txt

Rajahal and Joe, Thanks for the additional information, I will leave the jumper on! Dan

Rajahal, Thanks for the response. The reason I am tempted to remove the jumper on my 1 TB drive is that it is the only other advanced format drive in my box. My thought is that as I continue to replace drives they will in all likely hood be advanced format drives, and who knows what the future will hold for performance or some other benefit. Dan

I just bought a WD EARS 2TB drive, this is my first 2TB drive and as such was planning to use it as my parity drive. Since 4.7 is final I have a quick question, since it is an advanced format drive is there any problem using this as my parity drive since it will be the only one in my system? I am also out of sata ports so my plan is to give up/unassign my cache drive, install the new drive and attach it to the cache drive sata port, run the new preclear script with the –A option, then remove the old parity drive (1 TB WD Black) and replace it with the new WDEARS 2TB, rebuild parity, parity check???, then use the old parity drive to replace my 1 TB WD EARS (should I preclear it first?), then rebuild the data for this drive, then remove the jumper from my 1 TB WD EARS and preclear it with the –A option and replace my smallest drive (300GB). Then when I am all done I will hook the cache drive back up and have a 300GB drive as a spare until I purchase the supermicro AV8. Am I on the right track?

Starcat, I updated and have everything running, thanks for the help! One quick question about the links...will they survive a reboot of the unraid server or will I need to make these links each time I reboot? I did not have a smb-extra.conf file so I added one to the root of my flash drive with just the text you had in your message. I am not sure it is working as the album was not picked up by a scan. After changing directory and file permissions manually they scanned. So I must not have something correct with the smb-extra.conf file. I'm going to research this some more. Thanks again! Dan

Starcat, Thanks for all the great information, I can't wait to try this this weekend. I have been running the 7.5 version of slimserver for a year now and it has worked well. I am going to update to 7.52 this weekend. One of the issues that has plagued me is the addition of new songs. When I rip a cd and add music to my music folder the new music does not get picked up by an automatic or manual scan of slimserver. I assume this is a permissions /ownership issue. To pickup the new music I have to run the commands I found on page 8 of this thread: find . -type d -exec chmod 755 {} \; find . -type f -exec chmod 644 {} \; Are you able to get slimserver to automatically scan for new music? What permissions do you use for each folder that you recommended in your last reply to me. Thanks - all of you information has been very valuable to this linux newbie. Dan

Starcat, Thanks for the information. I have slimserver running on disk1 and I have all my music in a directory called Music on this disk. In your response you said: "Library is a link to the user share containing your audio". I would love to move my music to a user share. Can you explain what you mean by a link and how you would do this? Is there anything special about permissions and setting this up. Thanks, Dan

Matt or foo_fighter, I have two questions about the update process: Can you clarify what slimserver:1000 is? Is it the username you defined or is it the root folder of the original install? This part is confusing me. Also in step 7 you say to run: perl /slimserver/slimserver.pl --daemon --user slimserver >/dev/null 2>&1 & what does the: >/dev/null 2>&1 & at the end do? I previously only typed everything up to this point. Also one last question. Where have you kept your playlists - I assume in a directory and what permissions did you use for this directory? Thanks, Dan

I have had slimserver working for several months now and am considering updating to the 7.5 stable release. Has anyone performed an upgrade? Can I just install it on top of the current version? Are there any special steps I need to take other than killing the current install. Any input would be greatly appreciated! Thanks, Dan

Its been a while since I have had to purchase a new drive and was wondering if anyone could recommend a good parity drive. I currently have a 1 TB WD Black Caviar Drive set as my parity. Back when I purchased this drive - people were recommending this drive over seagate which was having the firmware issues at the time and the WD Green drives as they were 5400 rpm. At this point I think it makes sense to purchase a 1.5TB or even a 2TB drive for parity and then migrate my existing parity into the rotation after rebuilding and checking parity. In looking online it doesn't look like WD makes a black caviar 1.5TB and the 2TB verision is very expensive. Any recommendations would be greatly appreciated! Thanks, Dan