VFRLuke

well the good news is that I found another board/cpu laying around and have my server back in order now, but I definitely do want to upgrade from in if nothing else just for power consumption purposes. It's not an emergency any longer though so I will read up on some things and pull the trigger on something soon. Not sure I'm wanting to make the plunge for server hardware just because my use case is pretty low. I'll read up on options. and I insulated the dryer vent pipe that caused the chaos.

Hello all and thanks in advance for any advice. I'll start my story and try and keep it short. I've been using Unraid for a long time, but only with basic functionality of a NAS. I'm on my 2nd system, but have always put old hardware to use except for hard drives. I currently have a retired gaming motherboard and processor that's a 2nd gen i5-2500k and asus motherboard. I don't have any onboard video and have been running headless for years. Last night it crashed while streaming a video file from the server, and I couldn't get a response or ping it, power cycled it and it came up. I thought it was weird as it's been pretty solid, but then this am before I left for work it was down again. fast forward to this evening I've been down there working on it when I believe I have figured out that there's hardware failure and why. I just moved and put a server rack in the basement and there's a dryer vent above it. I suppose with the heat and humidity I have condensation inside the dryer vent, leaked out of the seam and into my unraid machine. It's the back of the PC, not where the drives reside. I need to get some hardware ordered up pretty fast. I use it for NAS only but maybe would like to do some very small things in the future. I assume an up to date i3 would do the trick. I have 8 drives and 6 of them are in the array, 1 cache, 1 hot spare. all 8 sata ports are on the motherboard. I need a motherboard, cpu, memory, extra card for sata ports if the motherboard doesn't have 8 (more is always better), and I'm thinking I might get a new power supply for good measure. Any form factor mobo is ok as I have it in a mid tower fractal define case (with the vented top of course to allow for water intrusion). I'm going to devise a way to defect any condensation away from my bench. Also if I put all of my current drives in with the existing USB drive, is there anything I should do beforehand? Would it be beneficial to replace my old mechanical cache drive with an NVME drive? I'm not really worried about cost, but I don't want to just waste money. Looking to keep the power draw low. I was happy with a 2nd gen i5 so I'm sure I'll be really happy with whatever level of performance. Thanks for any advice or help! Luke

I pulled it out. I'll keep it at 8 ports for now. If I want to ever add another I'll get one of the LSI controllers I suppose.

I did not replace the power supply. the one I have is a quality unit with a 12v rail capable of 49A. so if I have 9 drives (8 now) and no GPU that gives me a ton of headroom. I thought about replacing it just to have a modular power supply and neaten up the wiring.

I replaced 4 cables and eliminated drive 9 as I was just using it as a second spot for preclearing. so far so good. I powered it up and down about 5 times and it booted every time. I might run a parity check and set it to not write corrections just to stress test it a bit.

tower-diagnostics-20211118-0611.zip Hello, I had all of my hardware in an old cooler master case and I couldn't find any of the drive bays for it, so I decided to treat myself to a Fractal Define 7 that newegg had on sale. Long story short. I have 9 drives installed and after the install it only wants to boot up about half the time and my cpu load seems to be much higher than what it was before. This thing was rock solid before, and the only thing that could be different is maybe some sata cables and maybe the way that I utilized the power supply connections. I did add another drive in there to try and preclear it to see what kind of shape it was in, but I tried to unplug the connections from that particular drive and it still seems to only want to boot up about half the time. I only use this for storage, no docker containers. It's a retired gaming machine with a P8P67 motherboard, i5-2500k cpu. The motherboard has 8 sata ports on it and I have another little 2 port sata controller on it for the 9th drive (that's the one that I unplugged). I also have no GPU in this machine to even see what is happening during the boot. I can find something to install, but I wanted to post a thread with the diagnostics to see if anyone had any ideas of what I might check. I was thinking of just replacing a few of the SATA cables and checking to see if it's better, but I'm certainly up for suggestions. The sata cable theory might make sense because I disturbed all of them and may have even put in a couple of different ones to try and get the lengths closer to what I needed in the new case. The unassigned WD40EZRX is the disk that I tried unplugging. I see the error rate is really high on that disk as well and I suspected issues from that particular drive in the past. Thanks in advance, Luke

Did the parity swap and that went perfectly, thanks.

Thanks for the reply. I'll start that tomorrow.

Hello, I have recently started getting some smart errors on some of my old 2TB drives and I picked up a couple of 12TB drives to replace them. They are over 10 years old. Obviously I want to assign one new drive as the parity, Use the old parity 8TB drive and the other new 12TB drive to replace disks 3 and 4. I have the new drives in and precleared. I was thinking this order 1. Replace the parity drive and let it rebuild 2. Replace disk 3 with the other new drive 3. Preclear the old parity drive and replace disk 4 with it Would there be a better way of doing things? I wasn't sure if the parity swap procedure was appropriate since I have all drives currently installed. Thanks in advance for your help, Luke Disk 3 smart: Disk 4 smart:

It's been slow with multiple USB sticks except that one. When I transferred the license file is when it happened to this one. When it loads the page it happens fast, there's just a really big delay before the page loads.

So I recently upgraded my box to some of the hardware from my old gaming rig. It's up and running but the webgui is really slow. I thought for sure I had it narrowed down to the usb thumb drive. I built the new machine and got it up and running with a trial license long enough to transfer everything over. The thumb drive I had in there for that seemed to work well, the webgui was very snappy. I formatted my original USB key and put it in and I got the really slow webgui. Well it's 2017 now and I kind of wanted one of those low profile usb drives anyway so I ordered one of the san disk Cruiser Fit newer version, turns out it was really slow on that as well. I read through a couple of threads, plugged it into every USB port on the machine, disabled USB 3.0 in bios (Asus P8P67pro motherboard) and no matter what I couldn't get any speed out of the webgui with that thumb drive. I gave up and put the one that I had the trial key back in and my speed was back. I transferred the license from my old thumb drive guid to this one and now it's slow as well. That's really frustrating to me. The only things plugged into usb are the thumb drive and the cable to the UPS. Would one of you guys be able to look into the diagnostics and steer me in the right direction? Thanks in advance, Luke tower-diagnostics-20171226-1900.zip

OK, hopefully my last question. I'm almost finished copying stuff over to the new temporary build. Once that's finished I'm going to install all of the hardware in my existing case with all of the drives. My question is about the flash Drive. I will need to use the drive from the old server since it has the key on it I assume. Should I copy the entire contents of the "tower2" thumb drive over to the thumb drive for "tower 1"? Is there anything common mistakes that I need to look out for? I just want to make sure the part of it that remembers the data disk is in tact, the rest of it I can muddle through and play with settings if need be. Thanks in advance, Luke

I was being stupid. I didn't have a filesystem on the new disk yet so it wouldn't let me create the shares. I was hoping I got my question deleted before I exposed my ignorance Thanks for your help. I am in the process of copying the files over now

Hello guys, I wanted to bump this as I think I have my upgrade plan pretty well planned out in my mind. I just want someone to make sure I'm not overlooking anything. * I'm upgrading hardware, I have a cpu/mobo/memory that I will be using from my last gaming pc. * I'm planning on putting 2 precleared 8TB drives into my old gaming PC which will hold everything on my server. * I got a 30 day trial of another liscence and I have 2 boxes up now (no drives yet in the new box) Here's my plan 1. Get temporary install of unraid running on gaming machine with new hardware (done) 2. Install 2 8G hard drives in this machine 3. Transfer everything on my current server to that array (what's the best way to transfer a massive amount of data between 2 unraid machines?) 4. Take down original unraid machine and transfer the new motherboard into my current case and populate with drive I want to reuse 5. Reformat the additional drives with the newer file system and add into array I know that's pretty basic, but is there anything I should be careful of with the handling of the USB drives and or keys? Thanks in advance! Luke

thanks...this project just keeps getting bigger...

hello guys, I've had my unraid box running for quite some time and I ended up buying the budget build hardware way back when v4 was current. It's the AMD semperon and biostar Mobo in the old outdated recommended hardware wiki. I also have 2G of ram. Fast forward to present day, I've got my box out of the closet and I'm going to be doing some drive upgrades and I'm wondering now that since I've upgraded to v6, is this hardware adequate? I'm pretty much just using it as a NAS but I was maxing out the CPU doing a couple of preclears. I have my old gaming machine that can be canibalized for parts. Asus P8p67 pro board, I5-2500k cpu, 8G of ram. The board doesn't have on board video, so I might have an old junk video card I can put in there to set it up and get it to boot. Would it be worth the effort? any noticable performance gains on just using it as a NAS or should I just leave well enough alone until I have the need for more features? I don't have much interest in virtual machines or anything, but I'm sure there are some cool plugins. I have no problem buying the proper hardware if there's a reason for it, but I have this stuff collecting dust. Thanks in advance, Luke

Well, I've certainly suspected something going on with this particular disk, I don't mind getting it out of there, my current disk 1 also has a couple of reallocated sectors as well so that could be another one that gets replaced being that I have 2 8TB drives ready to go in. This leads me to my original post about what would be the best order of operations of doing this? I'm also thiking about doing some hardware upgrades also. My old gaming machine is collecting dust and I have a Asus p8p67pro board and an I5-2500k not being used. My current hardware is the old old recommended budget box with the semperon and 2g of memory. I don't plan on using any of the advanced features, but it seems like I have this stuff laying around, I could use it. If I was going to upgrade the hardware, should I just start from scratch with the 2 8tb hard drives on a new install and put the drives in one by one and copy the stuff to the new array. I think I saw a tutorial about how to install unassigned devices and copy over.

This is after the extended test. I assume this means this drive is ok? I can't replicate the issue now smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Green Device Model: WDC WD40EZRX-00SPEB0 Serial Number: WD-WCC4E6SDTPT3 LU WWN Device Id: 5 0014ee 2b651e2b1 Firmware Version: 80.00A80 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Tue Dec 12 06:26:40 2017 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: (0x85) Offline data collection activity was aborted 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: (51120) 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: ( 512) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x7035) 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 192 192 051 Pre-fail Always - 126204 3 Spin_Up_Time 0x0027 183 178 021 Pre-fail Always - 7841 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 514 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 069 069 000 Old_age Always - 23232 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 - 29 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 9 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 4195 194 Temperature_Celsius 0x0022 129 117 000 Old_age Always - 23 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 001 001 000 Old_age Offline - 91707 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 Extended offline Completed without error 00% 23228 - # 2 Extended offline Aborted by host 90% 23165 - # 3 Short offline Completed without error 00% 22998 - 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.

ok, I have that running now. You know that disk is on an external SATA card where the rest of the drives are plugged directly into the motherboard. Maybe the drive is good and I have another hardware problem. Thanks for your help

and here is the smart report, but honestly I have no idea what to look for in the smart results. smartctl 6.5 2016-05-07 r4318 [x86_64-linux-4.9.30-unRAID] (local build) Copyright (C) 2002-16, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Green Device Model: WDC WD40EZRX-00SPEB0 Serial Number: WD-WCC4E6SDTPT3 LU WWN Device Id: 5 0014ee 2b651e2b1 Firmware Version: 80.00A80 User Capacity: 4,000,787,030,016 bytes [4.00 TB] Sector Sizes: 512 bytes logical, 4096 bytes physical Rotation Rate: 5400 rpm Device is: In smartctl database [for details use: -P show] ATA Version is: ACS-2 (minor revision not indicated) SATA Version is: SATA 3.0, 6.0 Gb/s (current: 6.0 Gb/s) Local Time is: Sat Dec 9 10:49:01 2017 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: (51120) 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: ( 512) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x7035) 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 192 192 051 Pre-fail Always - 126204 3 Spin_Up_Time 0x0027 180 178 021 Pre-fail Always - 7958 4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 508 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 069 069 000 Old_age Always - 23164 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 - 28 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 9 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 4160 194 Temperature_Celsius 0x0022 129 117 000 Old_age Always - 23 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 182 182 000 Old_age Offline - 7344 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 without error 00% 22998 - 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.

Not sure if this helps. This is snipped from a log file before I did the upgrade to v6 Dec 5 03:15:30 Tower kernel: ata8.00: failed command: READ DMA EXT Dec 5 03:15:30 Tower kernel: ata8.00: cmd 25/00:00:60:53:3d/00:04:ca:01:00/e0 tag 0 dma 524288 in Dec 5 03:15:30 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 5 03:15:30 Tower kernel: ata8.00: status: { DRDY } Dec 5 03:15:30 Tower kernel: ata8: hard resetting link Dec 5 03:15:31 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Dec 5 03:15:31 Tower kernel: ata8.00: configured for UDMA/100 Dec 5 03:15:31 Tower kernel: ata8.00: device reported invalid CHS sector 0 Dec 5 03:15:31 Tower kernel: ata8: EH complete Dec 5 03:16:01 Tower kernel: ata8.00: limiting speed to UDMA/33:PIO4 Dec 5 03:16:01 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Dec 5 03:16:01 Tower kernel: ata8.00: failed command: READ DMA EXT Dec 5 03:16:01 Tower kernel: ata8.00: cmd 25/00:00:60:53:3d/00:04:ca:01:00/e0 tag 0 dma 524288 in Dec 5 03:16:01 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 5 03:16:01 Tower kernel: ata8.00: status: { DRDY } Dec 5 03:16:01 Tower kernel: ata8: hard resetting link Dec 5 03:16:02 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Dec 5 03:16:02 Tower kernel: ata8.00: configured for UDMA/33 Dec 5 03:16:02 Tower kernel: ata8.00: device reported invalid CHS sector 0 Dec 5 03:16:02 Tower kernel: sd 7:0:0:0: [sde] Dec 5 03:16:02 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08 Dec 5 03:16:02 Tower kernel: sd 7:0:0:0: [sde] Dec 5 03:16:02 Tower kernel: Sense Key : 0xb [current] [descriptor] Dec 5 03:16:02 Tower kernel: Descriptor sense data with sense descriptors (in hex): Dec 5 03:16:02 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Dec 5 03:16:02 Tower kernel: 00 00 00 00 Dec 5 03:16:02 Tower kernel: sd 7:0:0:0: [sde] Dec 5 03:16:02 Tower kernel: ASC=0x0 ASCQ=0x0 Dec 5 03:16:02 Tower kernel: sd 7:0:0:0: [sde] CDB: Dec 5 03:16:02 Tower kernel: cdb[0]=0x88: 88 00 00 00 00 01 ca 3d 53 60 00 00 04 00 00 00 Dec 5 03:16:02 Tower kernel: end_request: I/O error, dev sde, sector 7687983968 Dec 5 03:16:02 Tower kernel: ata8: EH complete Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687983904 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687983912 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687983920 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687983928 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687983936 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687983944 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687983952 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687983960 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687983968 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687983976 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687983984 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687983992 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984000 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984008 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984016 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984024 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984032 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984040 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984048 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984056 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984064 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984072 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984080 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984088 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984096 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984104 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984112 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984120 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984128 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984136 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984144 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984152 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984160 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984168 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984176 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984184 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984192 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984200 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984208 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984216 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984224 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984232 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984240 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984248 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984256 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984264 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984272 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984280 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984288 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984296 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984304 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984312 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984320 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984328 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984336 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984344 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984352 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984360 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984368 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984376 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984384 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984392 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984400 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984408 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984416 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984424 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984432 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984440 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984448 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984456 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984464 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984472 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984480 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984488 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984496 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984504 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984512 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984520 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984528 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984536 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984544 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984552 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984560 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984568 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984576 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984584 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984592 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984600 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984608 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984616 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984624 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984632 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984640 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984648 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984656 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984664 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984672 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984680 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984688 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984696 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984704 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984712 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984720 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984728 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984736 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984744 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984752 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984760 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984768 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984776 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984784 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984792 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984800 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984808 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984816 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984824 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984832 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984840 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984848 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984856 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984864 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984872 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984880 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984888 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984896 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984904 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984912 Dec 5 03:16:02 Tower kernel: md: disk5 read error, sector=7687984920 Dec 5 03:17:52 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Dec 5 03:17:52 Tower kernel: ata8.00: failed command: READ DMA EXT Dec 5 03:17:52 Tower kernel: ata8.00: cmd 25/00:00:60:67:3d/00:04:ca:01:00/e0 tag 0 dma 524288 in Dec 5 03:17:52 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 5 03:17:52 Tower kernel: ata8.00: status: { DRDY } Dec 5 03:17:52 Tower kernel: ata8: hard resetting link Dec 5 03:17:53 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Dec 5 03:17:53 Tower kernel: ata8.00: configured for UDMA/33 Dec 5 03:17:53 Tower kernel: ata8.00: device reported invalid CHS sector 0 Dec 5 03:17:53 Tower kernel: ata8: EH complete Dec 5 03:18:23 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Dec 5 03:18:23 Tower kernel: ata8.00: failed command: READ DMA EXT Dec 5 03:18:23 Tower kernel: ata8.00: cmd 25/00:00:60:67:3d/00:04:ca:01:00/e0 tag 0 dma 524288 in Dec 5 03:18:23 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 5 03:18:23 Tower kernel: ata8.00: status: { DRDY } Dec 5 03:18:23 Tower kernel: ata8: hard resetting link Dec 5 03:18:24 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Dec 5 03:18:24 Tower kernel: ata8.00: configured for UDMA/33 Dec 5 03:18:24 Tower kernel: ata8.00: device reported invalid CHS sector 0 Dec 5 03:18:24 Tower kernel: ata8: EH complete Dec 5 03:18:54 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Dec 5 03:18:54 Tower kernel: ata8.00: failed command: READ DMA EXT Dec 5 03:18:54 Tower kernel: ata8.00: cmd 25/00:00:60:67:3d/00:04:ca:01:00/e0 tag 0 dma 524288 in Dec 5 03:18:54 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 5 03:18:54 Tower kernel: ata8.00: status: { DRDY } Dec 5 03:18:54 Tower kernel: ata8: hard resetting link Dec 5 03:18:55 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Dec 5 03:18:55 Tower kernel: ata8.00: configured for UDMA/33 Dec 5 03:18:55 Tower kernel: ata8.00: device reported invalid CHS sector 0 Dec 5 03:18:55 Tower kernel: ata8: EH complete Dec 5 03:19:25 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Dec 5 03:19:25 Tower kernel: ata8.00: failed command: READ DMA EXT Dec 5 03:19:25 Tower kernel: ata8.00: cmd 25/00:00:60:67:3d/00:04:ca:01:00/e0 tag 0 dma 524288 in Dec 5 03:19:25 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 5 03:19:25 Tower kernel: ata8.00: status: { DRDY } Dec 5 03:19:25 Tower kernel: ata8: hard resetting link Dec 5 03:19:26 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Dec 5 03:19:26 Tower kernel: ata8.00: configured for UDMA/33 Dec 5 03:19:26 Tower kernel: ata8.00: device reported invalid CHS sector 0 Dec 5 03:19:26 Tower kernel: ata8: EH complete Dec 5 03:19:56 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Dec 5 03:19:56 Tower kernel: ata8.00: failed command: READ DMA EXT Dec 5 03:19:56 Tower kernel: ata8.00: cmd 25/00:00:60:67:3d/00:04:ca:01:00/e0 tag 0 dma 524288 in Dec 5 03:19:56 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 5 03:19:56 Tower kernel: ata8.00: status: { DRDY } Dec 5 03:19:56 Tower kernel: ata8: hard resetting link Dec 5 03:19:57 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Dec 5 03:19:57 Tower kernel: ata8.00: configured for UDMA/33 Dec 5 03:19:57 Tower kernel: ata8.00: device reported invalid CHS sector 0 Dec 5 03:19:57 Tower kernel: ata8: EH complete Dec 5 03:20:27 Tower kernel: ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen Dec 5 03:20:27 Tower kernel: ata8.00: failed command: READ DMA EXT Dec 5 03:20:27 Tower kernel: ata8.00: cmd 25/00:00:60:67:3d/00:04:ca:01:00/e0 tag 0 dma 524288 in Dec 5 03:20:27 Tower kernel: res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) Dec 5 03:20:27 Tower kernel: ata8.00: status: { DRDY } Dec 5 03:20:27 Tower kernel: ata8: hard resetting link Dec 5 03:20:28 Tower kernel: ata8: SATA link up 6.0 Gbps (SStatus 133 SControl 310) Dec 5 03:20:28 Tower kernel: ata8.00: configured for UDMA/33 Dec 5 03:20:28 Tower kernel: ata8.00: device reported invalid CHS sector 0 Dec 5 03:20:28 Tower kernel: sd 7:0:0:0: [sde] Dec 5 03:20:28 Tower kernel: Result: hostbyte=0x00 driverbyte=0x08 Dec 5 03:20:28 Tower kernel: sd 7:0:0:0: [sde] Dec 5 03:20:28 Tower kernel: Sense Key : 0xb [current] [descriptor] Dec 5 03:20:28 Tower kernel: Descriptor sense data with sense descriptors (in hex): Dec 5 03:20:28 Tower kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Dec 5 03:20:28 Tower kernel: 00 00 00 00 Dec 5 03:20:28 Tower kernel: sd 7:0:0:0: [sde] Dec 5 03:20:28 Tower kernel: ASC=0x0 ASCQ=0x0 Dec 5 03:20:28 Tower kernel: sd 7:0:0:0: [sde] CDB: Dec 5 03:20:28 Tower kernel: cdb[0]=0x88: 88 00 00 00 00 01 ca 3d 67 60 00 00 04 00 00 00 Dec 5 03:20:28 Tower kernel: end_request: I/O error, dev sde, sector 7687989088 Dec 5 03:20:28 Tower kernel: ata8: EH complete Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989024 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989032 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989040 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989048 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989056 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989064 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989072 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989080 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989088 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989096 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989104 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989112 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989120 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989128 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989136 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989144 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989152 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989160 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989168 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989176 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989184 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989192 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989200 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989208 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989216 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989224 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989232 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989240 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989248 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989256 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989264 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989272 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989280 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989288 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989296 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989304 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989312 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989320 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989328 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989336 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989344 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989352 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989360 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989368 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989376 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989384 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989392 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989400 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989408 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989416 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989424 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989432 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989440 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989448 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989456 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989464 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989472 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989480 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989488 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989496 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989504 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989512 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989520 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989528 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989536 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989544 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989552 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989560 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989568 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989576 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989584 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989592 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989600 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989608 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989616 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989624 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989632 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989640 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989648 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989656 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989664 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989672 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989680 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989688 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989696 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989704 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989712 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989720 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989728 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989736 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989744 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989752 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989760 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989768 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989776 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989784 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989792 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989800 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989808 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989816 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989824 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989832 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989840 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989848 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989856 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989864 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989872 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989880 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989888 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989896 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989904 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989912 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989920 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989928 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989936 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989944 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989952 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989960 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989968 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989976 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989984 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687989992 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687990000 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687990008 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687990016 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687990024 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687990032 Dec 5 03:20:28 Tower kernel: md: disk5 read error, sector=7687990040 Dec 5 03:40:01 Tower logger: mover started Dec 5 03:40:01 Tower logger: skipping */ Dec 5 03:40:01 Tower logger: mover finished Dec 5 03:47:07 Tower sSMTP[15972]: Sent mail for root@localhost (221 2.0.0 dnvrco-cmomta02 cmsmtp closing connection) uid=0 username=root outbytes=1555 Dec 5 04:50:27 Tower sSMTP[16118]: Sent mail for root@localhost (221 2.0.0 dnvrco-cmomta01 cmsmtp closing connection) uid=0 username=root outbytes=1555 Dec 5 05:47:05 Tower sSMTP[16242]: Sent mail for root@localhost (221 2.0.0 dnvrco-cmomta03 cmsmtp closing connection) uid=0 username=root outbytes=1555 Dec 5 06:27:10 Tower kernel: mdcmd (58): nocheck Dec 5 06:27:25 Tower kernel: md: md_do_sync: got signal, exit... Dec 5 06:27:48 Tower kernel: md: recovery thread sync completion status: -4 Dec 5 07:27:18 Tower kernel: mdcmd (59): spindown 0 Dec 5 07:27:19 Tower kernel: mdcmd (60): spindown 5

Hello guys and thanks in advance for anyone willing to share some custom advice. Backstory is that I had my server running on version 5 for a long time with no issues. about a week ago I starting noticing weird behavior out anything reading off of disk 5 and in the log there were lots of read errors on disk 5. I couldn't even stream a movie. as a test I deleted those files from disk 5 and excluded it in the share and it read fine off of the cache drive and then the next day off of another disk. So there's still a green ball on disk 5, but it's causing me problems and I do not trust it. I ordered a pair of 8TB WD red's and I ended up upgrading to unraid 6 so that my plus key would support more drives. I have them preclearing now, they should finish some time late tonight. My request for help is the order of operations for doing this upgrade and really what are my best options for the utilization of the new drives. I have 8 physical slots in my box for drives. I know one of the new 8TB drives will be the new Parity, the rest is kind of up in the air. The simplest would seem to be 1. replace parity drive and let it rebuild 2. replace disk 5 with the new 8tb data drive and let it rebuild 3. preclear the old parity drive, and replace one of the older 2TB drives with it or just add it in as a new data drive. I have some free space on some of these other drives though. Please see the screenshot below. It seems as if I could move everything from disk 5 to disk 4 and remove it from the array, then add in the new 8 as a new drive with the newer file system. would there be any benefit to that? I'm curious what some of you experienced guys would do in my situation? Thanks! Luke

good idea. I suppose I could just try any old usb stick and leave my current thumb drive the way it is and try it.

the term beta usually scares me, so when I decided it was time to upgrade from 4.7 I went with 5.0.6. I'm not a power user or anything, just mainly want a nice NAS. We I bought a couple of hard drives and wasn't aware that 5 limits me to 7 drives with a plus key where v6 lets me have 8. I have 8 drives right now and one of them I would like to keep as a hot spare (for now). I have fairly low end hardware in my system. an amd semperon processor: http://www.newegg.com/Product/Product.aspx?Item=N82E16819103698 and 2G of memory. I don't use much other than unmenu now...should I just stick with the tried and true and unplug my 8th drive, or switch to 6? thanks in advance, Luke

Thanks for the help guys, I may go ahead and order one of those cards that you linked and a 4TB drive or two. If I order 2 4TB drives, it should net me 6 more TB of storage because I'll reuse the old parity drive. Any drives that are the hot ticket right now, or should I stick with the tried and true WD greens? performance is not as important as cost and reliability.