T1000

The ASUS M5A78L-M/USB3 looks like it should be a god replacement. I don't dont have a spare NIC to try.

It should but it doesn't: http://www.beardeddonkey.com/home/comments.php?y=12&m=10&entry=entry121007-042518 I can get it to sleep and all the settings are corect but nothing will wake it up. I have to shut it down and reboot.

I'm currently running two servers with ASRock 880GMLE ATX AMD 880G motherboards: http://www.asrock.com/mb/AMD/880GM-LE%20FX/index.us.asp?cat=Specifications In a bid to cut my electricty bill I'm sorting out all my computers for sleep and wake on LAN. After testing and google search I've come to find that WOL will not work on these motherboards. Can someone advise me on what I should replace them with to get at least the same features with proper WOL? I want to use my current CPU, fans ,RAM and PCI/PCIe cards if possible. I'm open to a new processor if need to. These are the attached cards: http://www.scan.co.uk/products/supermicro-aoc-saslp-mv8-8-port-sas-sata-300mb-s-pci-e-controller-card http://www.maplin.co.uk/p/serial-ata-raid-pci-card-a47bb

Thanks for that. Thats why I get Dynamix GUI but no plugins. Sorted now. I put the flash drive in a windows PC and it offered CheckDisk straight away. It's back in and running again now. Still had to install SSH before I could use it. Maybe a issue checkdisk might have fixed?? When I tried to shutdown it couldn't unmount all the drives. I ran this command on each drive: fuser -k /mnt/disk1 It was disk 7 that wasn't unmounting for some reason. At least using that command I didn't have to do a parity check after start up. I'll have to keep an eye on it next time.

I've been running two servers for a few years now. Server 1 and server 2. Server 2 has recently starting playing up. When it boots, it starts and runs. I can add content and remove content. Parity syncs fine. I've added unmenu and dynamix and some plugins on both servers. Both running 5.0.5 On server 2 it all installs fine but it doesn't keep dynamix after a reboot. It keeps the plugins working but doesn't show in the web GUI. I know this because it keeps sending me emails. SSH stops working after a while too. If it's left for a few weeks the web GUI either doesn't come up or it does and when I select take array offline it seems to freeze. Only way around is turn switch it off, start it again and let it sync parity. Attached is the current syslog. Is there anything else I need to provide to get help? I've got older syslogs which quite likely has valuable info regarding the shutdown but they are quite large. Here are some snippets taken from the end of them: Aug 1 19:29:52 Tower2 powerdown[28663]: Initiating Shutdown with '' Aug 1 19:29:52 Tower2 shutdown[28664]: shutting down for system halt Aug 1 19:29:53 Tower2 init: Switching to runlevel: 0 Aug 1 19:29:55 Tower2 rc.unRAID[28683][28684]: Powerdown V2.06 Aug 1 19:29:55 Tower2 rc.unRAID[28683][28685]: Stopping Plugins. Aug 1 19:29:55 Tower2 rc.unRAID[28683][28693]: Running: "/etc/rc.d/rc.cachedirs stop" Aug 1 19:29:55 Tower2 cache_dirs: killing cache_dirs process 11051 Aug 1 19:30:00 Tower2 rc.unRAID[28683][28696]: cache_dirs stopped Aug 1 19:30:00 Tower2 rc.unRAID[28683][28719]: Running: "/etc/rc.d/rc.sysstat stop" Aug 1 19:30:00 Tower2 rc.unRAID[28683][28723]: Stopping unRAID. Aug 1 19:30:01 Tower2 rc.unRAID[28683][28746]: Killing active pids on the array drives Aug 1 19:30:01 Tower2 rc.unRAID[28683][28749]: Cannot stat /mnt/cache: No such file or directory Aug 1 19:30:01 Tower2 rc.unRAID[28683][28749]: Cannot stat /mnt/cache: No such file or directory Aug 1 19:30:01 Tower2 rc.unRAID[28683][28750]: Sync filesystems Aug 1 19:30:02 Tower2 rc.unRAID[28683][28756]: Umounting the drives Aug 1 19:30:02 Tower2 rc.unRAID[28683][28760]: /dev/md1 umounted Aug 1 19:30:02 Tower2 rc.unRAID[28683][28760]: /dev/md2 umounted Aug 1 19:30:02 Tower2 rc.unRAID[28683][28760]: /dev/md3 umounted Aug 1 19:30:02 Tower2 rc.unRAID[28683][28760]: /dev/md4 umounted Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: /dev/md5 umounted Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: /dev/md6 umounted Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: umount2: Device or resource busy Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: umount: /mnt/disk7: device is busy. Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: (In some cases useful info about processes that use Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: the device is found by lsof( or fuser(1)) Aug 1 19:30:03 Tower2 rc.unRAID[28683][28760]: umount2: Device or resource busy Aug 1 19:30:03 Tower2 rc.unRAID[28683][28769]: Active pids left on the array drives Aug 1 19:30:03 Tower2 rc.unRAID[28683][28772]: Aug 1 19:30:03 Tower2 rc.unRAID[28683][28772]: USER PID ACCESS COMMAND Aug 1 19:30:03 Tower2 rc.unRAID[28683][28772]: /dev/md7: root 28629 ..c.. find Aug 1 19:30:03 Tower2 rc.unRAID[28683][28772]: Aug 1 19:30:03 Tower2 rc.unRAID[28683][28773]: Stopping the Array Aug 1 19:30:03 Tower2 rc.unRAID[28683][28779]: /root/mdcmd: line 11: echo: write error: Device or resource busy Aug 1 19:30:03 Tower2 kernel: mdcmd (161): stop Aug 1 19:30:03 Tower2 kernel: md: 2 devices still in use. Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: --- /tmp/mdcmd.28683.1^I2014-08-01 19:30:03.544252359 +0100 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: +++ /tmp/mdcmd.28683.2^I2014-08-01 19:30:08.553930818 +0100 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: @@ -124,7 +124,7 @@ Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: rdevSize.7=1465138552 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: rdevId.7=SAMSUNG_HD154UI_S1XWJ1KZ204639 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: rdevNumErrors.7=0 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: -rdevLastIO.7=1406917803 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: +rdevLastIO.7=1406917808 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: rdevSpinupGroup.7=0 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: diskNumber.8=8 Aug 1 19:30:08 Tower2 mdstatusdiff[28786]: diskName.8= Aug 19 16:39:49 Tower2 powerdown[9139]: Powerdown initiated Aug 19 16:39:49 Tower2 powerdown[9143]: Powerdown V2.06 Aug 19 16:39:49 Tower2 rc.unRAID[9145][9146]: Processing /etc/rc.d/rc.unRAID.d/ kill scripts. Aug 19 16:39:49 Tower2 powerdown[9151]: Initiating Shutdown with '' Aug 19 16:39:49 Tower2 shutdown[9152]: shutting down for system halt Aug 19 16:39:49 Tower2 init: Switching to runlevel: 0 Aug 19 16:39:53 Tower2 emhttp: Unmounting disks... Aug 19 16:39:53 Tower2 emhttp: shcmd (309): umount /mnt/disk7 |& logger Aug 19 16:39:53 Tower2 logger: umount: /mnt/disk7: device is busy. Aug 19 16:39:53 Tower2 logger: (In some cases useful info about processes that use Aug 19 16:39:53 Tower2 logger: the device is found by lsof( or fuser(1)) Aug 19 16:39:53 Tower2 emhttp: Retry unmounting disk share(s)... Aug 19 16:39:56 Tower2 rc.unRAID[9168][9169]: Powerdown V2.06 Aug 19 16:39:56 Tower2 rc.unRAID[9168][9170]: Stopping Plugins. Aug 19 16:39:56 Tower2 rc.unRAID[9168][9178]: Running: "/etc/rc.d/rc.cachedirs stop" Aug 19 16:39:58 Tower2 emhttp: Unmounting disks... Aug 19 16:39:58 Tower2 emhttp: shcmd (310): umount /mnt/disk7 |& logger Aug 19 16:39:58 Tower2 logger: umount: /mnt/disk7: device is busy. Aug 19 16:39:58 Tower2 logger: (In some cases useful info about processes that use Aug 19 16:39:58 Tower2 logger: the device is found by lsof( or fuser(1)) Aug 19 16:39:58 Tower2 emhttp: Retry unmounting disk share(s)... Aug 19 16:40:01 Tower2 rc.unRAID[9168][9181]: cache_dirs stopped Aug 19 16:40:01 Tower2 rc.unRAID[9168][9204]: Running: "/etc/rc.d/rc.sysstat stop" Aug 19 16:40:01 Tower2 rc.unRAID[9168][9208]: Stopping unRAID. Aug 19 16:40:02 Tower2 rc.unRAID[9168][9231]: Killing active pids on the array drives Aug 19 16:40:02 Tower2 rc.unRAID[9168][9234]: Cannot stat /mnt/user/*: No such file or directory Aug 19 16:40:02 Tower2 rc.unRAID[9168][9234]: Cannot stat /mnt/user/*: No such file or directory Aug 19 16:40:02 Tower2 rc.unRAID[9168][9234]: Cannot stat /mnt/cache: No such file or directory Aug 19 16:40:02 Tower2 rc.unRAID[9168][9234]: Cannot stat /mnt/cache: No such file or directory Aug 19 16:40:02 Tower2 rc.unRAID[9168][9235]: Sync filesystems Aug 19 16:40:03 Tower2 rc.unRAID[9168][9237]: Umounting the drives Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Invalid argument Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /dev/md1: not mounted Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: Could not find /dev/md1 in mtab Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Invalid argument Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /dev/md2: not mounted Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: Could not find /dev/md2 in mtab Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Invalid argument Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /dev/md3: not mounted Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: Could not find /dev/md3 in mtab Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Invalid argument Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /dev/md4: not mounted Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: Could not find /dev/md4 in mtab Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Invalid argument Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /dev/md5: not mounted Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: Could not find /dev/md5 in mtab Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Invalid argument Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /dev/md6: not mounted Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: Could not find /dev/md6 in mtab Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Device or resource busy Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount: /mnt/disk7: device is busy. Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: (In some cases useful info about processes that use Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: the device is found by lsof( or fuser(1)) Aug 19 16:40:03 Tower2 rc.unRAID[9168][9241]: umount2: Device or resource busy Aug 19 16:40:03 Tower2 rc.unRAID[9168][9249]: Active pids left on the array drives Aug 19 16:40:03 Tower2 rc.unRAID[9168][9252]: Aug 19 16:40:03 Tower2 rc.unRAID[9168][9252]: USER PID ACCESS COMMAND Aug 19 16:40:03 Tower2 rc.unRAID[9168][9252]: /dev/md7: root 8718 ..c.. find Aug 19 16:40:03 Tower2 rc.unRAID[9168][9252]: Aug 19 16:40:03 Tower2 rc.unRAID[9168][9253]: Stopping the Array Aug 19 16:40:03 Tower2 rc.unRAID[9168][9259]: /root/mdcmd: line 11: echo: write error: Device or resource busy Aug 19 16:40:03 Tower2 kernel: mdcmd (102): stop Aug 19 16:40:03 Tower2 kernel: md: 2 devices still in use. Aug 19 16:40:03 Tower2 emhttp: Unmounting disks... Aug 19 16:40:03 Tower2 emhttp: shcmd (311): umount /mnt/disk7 |& logger Aug 19 16:40:03 Tower2 logger: umount: /mnt/disk7: device is busy. Aug 19 16:40:03 Tower2 logger: (In some cases useful info about processes that use Aug 19 16:40:03 Tower2 logger: the device is found by lsof( or fuser(1)) Aug 19 16:40:03 Tower2 emhttp: Retry unmounting disk share(s)... Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: --- /tmp/mdcmd.9168.1^I2014-08-19 16:40:03.310623845 +0100 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: +++ /tmp/mdcmd.9168.2^I2014-08-19 16:40:08.320314003 +0100 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: @@ -124,7 +124,7 @@ Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: rdevSize.7=1465138552 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: rdevId.7=SAMSUNG_HD154UI_S1XWJ1KZ204639 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: rdevNumErrors.7=0 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: -rdevLastIO.7=1408462803 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: +rdevLastIO.7=1408462808 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: rdevSpinupGroup.7=0 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: diskNumber.8=8 Aug 19 16:40:08 Tower2 mdstatusdiff[9269]: diskName.8= tower2.txt

The old parity drive won't be in the unRAID server while I get the new parity up and running. I get overly concerned with drive assignment letters and stuff because I don't want to mix anything up. Hell I might even get it taken on a road trip so I can't get them mixed up in anyway. When the new parity is synced and checked then I will allow the old one back in the house.

Thanks So rather than this: cd /boot ./preclear_disk.sh -A /dev/sda It would be this?: cd /boot ./preclear_disk.sh -n /dev/sda

Okay thanks! I don't mind running a full pre-clear on it. I've been messing about with data rebuilds and parity syncs for the last 4 days now with 3 more days of pre-clearing the new parity drive before it gets swapped, 1 more day won't hurt.

I'm going to be replacing my parity disk with a 4TB in the next few days after some pre-clearing. When I remove the old parity 2TB disk and use again it shouldn't need pre-clearing because it's already proved itself for the last 3 years. When I want to expand the array with the old parity disk as a data drive do I just select it in the GUI, format and then start using the larger array? Am I missing something, after all the disk did have the parity info on it, does the re-format take care of all that?

Thanks. It worked fine. I'm always very cautious with unRAID. Theres a lot of content to mess up if I get it wrong.

I should probably add that when I moved the drive to another bay in the 3-5 case the drive stayed red.

Hello, I got home last night with my first ever 4TB drive, to do my first ever parity swap and there was a nasty red ball sitting by the last drive I fitted to the server a month ago with 22 errors on it. I can't find anything wrong cable wise. I'm running 5.0.4 I tried to put a movie on the server at the weekend and it failed due to being full. All the drives are full. The SMART report on the disk is attached. If I'm reading the SMART report correctly the drive is fine. The syslog is pastebin as it was too big to attach: http://pastebin.com/vjJcBZiS What should I do next? Thanks smart.txt

Replacing the motherboard has brought it all back to life. I will try Reiserfsck later.

I'm running 10.6 Snow Leopard. I think the mobo is on it's way out. Tried to do Reiserfsck but the USB keyboard isn't working. I tried the flash drive from another server and all the writing is purple on the screen. I can't access the web GUI anymore either. A mobo died (ASRock 880GMLE) on this server about two years ago and I had to change it. I think I got an extra spare one at the time.

I found info about rolling back. I rolled back to 5.0.4 and so far so good.

I'm currently running 5.0.5 Pro on my movie server and I'm having issues loading files via OSX. I get the following error with 5 seconds left before completion: The operation can’t be completed because an item with the name “Thunderbolt and Lightfoot 1974” already exists I can't tell if the file does complete but it does play okay. How do I work out whats happening? My other server is running 5.0.4 and doesn't seem to have the same issues. Could I rollback to 5.0.4 and try it? Is there anything special I have to do to roll back other than copy the three 5.0.4 files over?

Hmm, it works from one laptop but not the other. I guess it's not an unRAID issue. Thanks.

Yes I did that.

Thanks guys got it working fine in the end. I had to reformat the drive, make bootable and copy my pro key from a back up from nearly a year ago because it wouldn't work but now it's fine. Just one outstanding problem. On 4.7 when I "Connect to server..." on OSX I could type in smb://192.168.0.200 and it would bring up all the drives on the unraid server. Now it says I don't have permission to access the server. I can access it under Network computers but not by that path. What could it be?

I'm looking to upgrade to 5.0 from 4.7. It says "Disable or un-install all non-stock unRAID add-ons" are the addons I have installed using unMenu (like apcupsd) non-stock? If they are what is easiest way to disable them all and then get them running on the 5.0 release? Thanks

Swapped the 2TB Seagate drive that kept failing on it's 2nd preclear to the other card and it's precleared twice and on it's 3rd preclear now. The spare 1.5TB Samsung drive I had I have attached to the Supermicro card and it's also precleared twice and on it's 3rd preclear. So the 2TB Seagate only fails on it's 2nd preclear via the Supermicro card. Is it because it's 2TB and not 1.5TB? After the 3rd preclear I'm gonna move it back to the supermicro card and do some preclears. I just wish it didn't take so long! If any one has any idea's on how I can find the casue of the problem would be great, thanks.

The preclear failed on it's 2nd preclear (it's always on the second preclear) and here is the image which is exactly the same as the one I posted the other day: Should try and get the Supermicro card exchanged? RAM looks fine (as far as I can tell). Same error on different disks. That preclear fail screen is the same now as it was 2 months ago. Is there another test I can do to rule it out?

I ran a ramtest the other night: Looks OK to me. Not sure how long it's supposed to run for. When you say disk controller does that mean the Supermicro 8 port card? Could it be the SAS-SATA cable? Either way it's gonna take days to figure out the cause particularly with it not failing every preclear. The preclear is just about to finish with no errors by the looks of it so I will have to start the preclear again to try and get it to fail. If it is the card would the turn around on testing for failure be quicker on a smaller drive? It would also save me from running 20-30 preclears on my new drive.

The image I posted was from a while ago on a different disk and I posted it because it looked very similar. I will do more preclears until it fails again and take a picture.

Added a new replacement drive (to the last port on the first SAS-sata on my Supermicro AOC-SASLP-MV8, 8-Port SAS/SATA Card) where the last one was. Tried a preclear and got an image similar to this one (this isn't the actual image): Which I believe to be a preclear fail. I powered down, connected the drive to another sata card I had in the enclosure and did a preclear fine, no errors. Then powered down again, connected the drive to the port it failed on last time and did the 2nd preclear, no problems, no errors, finished fine. Tried the 3rd and last preclear and it looked like the image above. Why would it fail then work, then fail etc? Should I be asking in the preclear thread or is it more likely to be a hardware issue? Here is the SMART report for the disk: root@Tower:~# smartctl -a /dev/sde smartctl 5.39.1 2010-01-28 r3054 [i486-slackware-linux-gnu] (local build) Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net === START OF INFORMATION SECTION === Device Model: ST2000DL003-9VT166 Serial Number: 5YD6C2PB Firmware Version: CC3C 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: ATA-8-ACS revision 4 Local Time is: Fri Oct 28 09:45:10 2011 UTC 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: (0x82) Offline data collection activity was completed without error. 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: ( 623) 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: ( 1) minutes. Extended self-test routine recommended polling time: ( 255) minutes. Conveyance self-test routine recommended polling time: ( 2) minutes. SCT capabilities: (0x30b7) SCT Status supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 10 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 112 100 006 Pre-fail Always - 43795672 3 Spin_Up_Time 0x0003 092 092 000 Pre-fail Always - 0 4 Start_Stop_Count 0x0032 100 100 020 Old_age Always - 10 5 Reallocated_Sector_Ct 0x0033 100 100 036 Pre-fail Always - 0 7 Seek_Error_Rate 0x000f 060 060 030 Pre-fail Always - 1197262 9 Power_On_Hours 0x0032 100 100 000 Old_age Always - 98 10 Spin_Retry_Count 0x0013 100 100 097 Pre-fail Always - 0 12 Power_Cycle_Count 0x0032 100 100 020 Old_age Always - 10 183 Runtime_Bad_Block 0x0032 100 100 000 Old_age Always - 0 184 End-to-End_Error 0x0032 100 100 099 Old_age Always - 0 187 Reported_Uncorrect 0x0032 100 100 000 Old_age Always - 0 188 Command_Timeout 0x0032 100 099 000 Old_age Always - 1 189 High_Fly_Writes 0x003a 100 100 000 Old_age Always - 0 190 Airflow_Temperature_Cel 0x0022 073 069 045 Old_age Always - 27 (Lifetime Min/Max 23/27) 191 G-Sense_Error_Rate 0x0032 100 100 000 Old_age Always - 0 192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 6 193 Load_Cycle_Count 0x0032 100 100 000 Old_age Always - 10 194 Temperature_Celsius 0x0022 027 040 000 Old_age Always - 27 (0 20 0 0) 195 Hardware_ECC_Recovered 0x001a 037 019 000 Old_age Always - 43795672 197 Current_Pending_Sector 0x0012 100 100 000 Old_age Always - 0 198 Offline_Uncorrectable 0x0010 100 100 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x003e 200 200 000 Old_age Always - 0 240 Head_Flying_Hours 0x0000 100 253 000 Old_age Offline - 63801739182178 241 Total_LBAs_Written 0x0000 100 253 000 Old_age Offline - 2313682740 242 Total_LBAs_Read 0x0000 100 253 000 Old_age Offline - 4159336131 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:~#