August 10, 201312 yr 5.0 rc16c share using excluded drive 1, data on drive 1 super slow to access I have disk 1 for my data and disk 2 thru disk 10 for 3 shares, disk 11 for parity and disk 12 for cache. One of the 3 shares shows the free space from disk 1 added to it. How can I fix this? My disk 1 is SUPER SLOW now and my drive light stays on all the time. Thinking about downgrading back to 5.0 rc8, didn't have any issues until I upgraded. Array is Valid. NOTE: I think 1 of my drives is going bad, but I haven't gotten any ERRORS on unRAID GUI or any SMART errors, backing up data now, but it's taking hours to do 1 gig of data. It's ridiculously slow! Anybody know how to speed it up, maybe disconnect it and use the parity? Thanks!
August 11, 201312 yr Author BTW I started to backup all the files over to a new share but it's taking forever! It took the whole day to recover my music (35 gigs) I wanted to know if it will be faster to take the drive out and use the parity drive? The drive is AWFUL slow to access right now. It seems like what the MBR on a Windows system is but on ReiserFS got messed up and accessing any folder takes like 15 to 20 seconds to show up for that drive. Which makes me wonder, can we change the location of that sector or whatever it's called?
August 11, 201312 yr Author Huh, didn't notice I had so many read errors on disk1! syslog is over 192k can't upload it. But here is a clip of the errors I am getting all over the syslog file while backing up the data off of that drive: Aug 11 00:16:48 MMPC kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 11 00:16:48 MMPC kernel: ata1.00: irq_stat 0x40000001 Aug 11 00:16:48 MMPC kernel: ata1.00: failed command: READ DMA EXT Aug 11 00:16:48 MMPC kernel: ata1.00: cmd 25/00:00:68:26:34/00:04:10:00:00/e0 tag 0 dma 524288 in Aug 11 00:16:48 MMPC kernel: res 51/40:3f:28:27:34/00:03:10:00:00/e0 Emask 0x9 (media error) Aug 11 00:16:48 MMPC kernel: ata1.00: status: { DRDY ERR } Aug 11 00:16:48 MMPC kernel: ata1.00: error: { UNC } Aug 11 00:16:49 MMPC kernel: ata1.00: configured for UDMA/133 Aug 11 00:16:49 MMPC kernel: ata1: EH complete Aug 11 00:16:53 MMPC kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 11 00:16:53 MMPC kernel: ata1.00: irq_stat 0x40000001 Aug 11 00:16:53 MMPC kernel: ata1.00: failed command: READ DMA EXT Aug 11 00:16:53 MMPC kernel: ata1.00: cmd 25/00:00:68:26:34/00:04:10:00:00/e0 tag 0 dma 524288 in Aug 11 00:16:53 MMPC kernel: res 51/40:3f:28:27:34/00:03:10:00:00/e0 Emask 0x9 (media error) Aug 11 00:16:53 MMPC kernel: ata1.00: status: { DRDY ERR } Aug 11 00:16:53 MMPC kernel: ata1.00: error: { UNC } Aug 11 00:16:54 MMPC kernel: ata1.00: configured for UDMA/133 Aug 11 00:16:54 MMPC kernel: ata1: EH complete Aug 11 00:16:56 MMPC kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 11 00:16:56 MMPC kernel: ata1.00: irq_stat 0x40000001 Aug 11 00:16:56 MMPC kernel: ata1.00: failed command: READ DMA EXT Aug 11 00:16:56 MMPC kernel: ata1.00: cmd 25/00:00:68:26:34/00:04:10:00:00/e0 tag 0 dma 524288 in Aug 11 00:16:56 MMPC kernel: res 51/40:3f:28:27:34/00:03:10:00:00/e0 Emask 0x9 (media error) Aug 11 00:16:56 MMPC kernel: ata1.00: status: { DRDY ERR } Aug 11 00:16:56 MMPC kernel: ata1.00: error: { UNC } Aug 11 00:16:58 MMPC kernel: ata1.00: configured for UDMA/133 Aug 11 00:16:58 MMPC kernel: ata1: EH complete Aug 11 00:17:01 MMPC kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 11 00:17:01 MMPC kernel: ata1.00: irq_stat 0x40000001 Aug 11 00:17:01 MMPC kernel: ata1.00: failed command: READ DMA EXT Aug 11 00:17:01 MMPC kernel: ata1.00: cmd 25/00:00:68:26:34/00:04:10:00:00/e0 tag 0 dma 524288 in Aug 11 00:17:01 MMPC kernel: res 51/40:3f:28:27:34/00:03:10:00:00/e0 Emask 0x9 (media error) Aug 11 00:17:01 MMPC kernel: ata1.00: status: { DRDY ERR } Aug 11 00:17:01 MMPC kernel: ata1.00: error: { UNC } Aug 11 00:17:02 MMPC kernel: ata1.00: configured for UDMA/133 Aug 11 00:17:02 MMPC kernel: ata1: EH complete Aug 11 00:17:05 MMPC kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 11 00:17:05 MMPC kernel: ata1.00: irq_stat 0x40000001 Aug 11 00:17:05 MMPC kernel: ata1.00: failed command: READ DMA EXT Aug 11 00:17:05 MMPC kernel: ata1.00: cmd 25/00:00:68:26:34/00:04:10:00:00/e0 tag 0 dma 524288 in Aug 11 00:17:05 MMPC kernel: res 51/40:3f:28:27:34/00:03:10:00:00/e0 Emask 0x9 (media error) Aug 11 00:17:05 MMPC kernel: ata1.00: status: { DRDY ERR } Aug 11 00:17:05 MMPC kernel: ata1.00: error: { UNC } Aug 11 00:17:07 MMPC kernel: ata1.00: configured for UDMA/133 Aug 11 00:17:07 MMPC kernel: ata1: EH complete Aug 11 00:17:10 MMPC kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Aug 11 00:17:10 MMPC kernel: ata1.00: irq_stat 0x40000001 Aug 11 00:17:10 MMPC kernel: ata1.00: failed command: READ DMA EXT Aug 11 00:17:10 MMPC kernel: ata1.00: cmd 25/00:00:68:26:34/00:04:10:00:00/e0 tag 0 dma 524288 in Aug 11 00:17:10 MMPC kernel: res 51/40:3f:28:27:34/00:03:10:00:00/e0 Emask 0x9 (media error) Aug 11 00:17:10 MMPC kernel: ata1.00: status: { DRDY ERR } Aug 11 00:17:10 MMPC kernel: ata1.00: error: { UNC } Aug 11 00:17:10 MMPC kernel: ata1.00: configured for UDMA/133 Aug 11 00:17:10 MMPC kernel: sd 0:0:0:0: [sda] Unhandled sense code Aug 11 00:17:10 MMPC kernel: sd 0:0:0:0: [sda] Result: hostbyte=0x00 driverbyte=0x08 Aug 11 00:17:10 MMPC kernel: sd 0:0:0:0: [sda] Sense Key : 0x3 [current] [descriptor] Aug 11 00:17:10 MMPC kernel: Descriptor sense data with sense descriptors (in hex): Aug 11 00:17:10 MMPC kernel: 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 Aug 11 00:17:10 MMPC kernel: 10 34 27 28 Aug 11 00:17:10 MMPC kernel: sd 0:0:0:0: [sda] ASC=0x11 ASCQ=0x4 Aug 11 00:17:10 MMPC kernel: sd 0:0:0:0: [sda] CDB: cdb[0]=0x28: 28 00 10 34 26 68 00 04 00 00 Aug 11 00:17:10 MMPC kernel: end_request: I/O error, dev sda, sector 271853352 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853288 Aug 11 00:17:10 MMPC kernel: ata1: EH complete Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853296 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853304 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853312 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853320 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853328 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853336 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853344 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853352 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853360 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853368 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853376 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853384 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853392 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853400 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853408 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853416 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853424 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853432 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853440 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853448 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853456 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853464 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853472 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853480 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853488 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853496 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853504 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853512 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853520 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853528 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853536 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853544 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853552 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853560 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853568 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853576 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853584 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853592 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853600 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853608 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853616 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853624 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853632 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853640 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853648 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853656 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853664 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853672 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853680 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853688 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853696 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853704 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853712 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853720 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853728 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853736 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853744 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853752 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853760 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853768 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853776 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853784 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853792 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853800 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853808 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853816 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853824 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853832 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853840 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853848 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853856 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853864 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853872 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853880 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853888 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853896 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853904 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853912 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853920 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853928 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853936 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853944 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853952 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853960 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853968 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853976 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853984 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271853992 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854000 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854008 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854016 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854024 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854032 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854040 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854048 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854056 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854064 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854072 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854080 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854088 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854096 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854104 Aug 11 00:17:10 MMPC kernel: md: disk1 read error, sector=271854112 And this is over and over...! Time to change the drive! (BTW, I changed the cable already with no luck) EDIT: I still have a valid parity. I had downgraded to 5.0-rc12a going to install 5.0-rc16c since it's not the version what's causing this. Thread can be closed I guess?
August 11, 201312 yr Un-assign the drive and start the array. You should be able to copy the data faster. But simply replacing the drive should not result in any data lose.
August 12, 201312 yr It is not necessarily the drive. I would check carefully that the SATA and Power cables are correctly seated as if they are loose you would get the symptoms shown. A smartctl report is likely to show if the drive itself is having problems.
August 12, 201312 yr Huh, didn't notice I had so many read errors on disk1! Aug 11 00:16:48 MMPC kernel: ata1.00: Just for future reference, ata1.00 in no way indicates disk1. The disk1 read errors indicate that disk 1 is having issues, but the ata line by itself could be any of the disks. Further troubleshooting and a full syslog is necessary to determine if ata1 is indeed disk 1. In this case it probably is, but I didn't want thread searchers to see that and think "aha! ata1 must equal disk 1".
August 14, 201312 yr Author Per unRAID GUI, disk 1 is /dev/sdb, here is the smart report for /dev/sdb. EDIT: I had posted a smart report already a few posts back, looks similar I think. smart.txt
August 14, 201312 yr Author I ordered another drive anyways even if this one is good which I doubt to have a spare drive.
August 14, 201312 yr The disk has a lot of pending sectors. it needs to be rebuilt. Use the spare and then run pre-clear on the current drive. You will be able to access the contents of the disk much faster if you un-assign the disk.
August 14, 201312 yr Author The disk has a lot of pending sectors. it needs to be rebuilt. Use the spare and then run pre-clear on the current drive. You will be able to access the contents of the disk much faster if you un-assign the disk. I moved everything out of the drive, it's empty now. Waiting on replacement to rebuild and make it part of my other shares (include it, it's excluded from all the shares at the moment.) Parity has always been Valid. Never had parity issues, thank God. It was part of the array but it was it's own single drive share, used the most (Data drive) but it's not even 2 years old and it's got errors already, I have a Seagate 7200.11 1.5TB that's 5 yrs old, with a heat peak of 63 deg on the smart report (when my A/C went out) and it has 0 errors! The Seagate is my cache drive.
August 14, 201312 yr I don't understand why the disk is empty. Replacing the disk or rebuilding the disk onto itself would have resulted in the rebuilt disk containing all of the data that the disk previously contained. This is the point of unRAIDs parity protection system. If the disk is empty then set a new config and exclude the empty disk. When the new disk arrives add it as a new disk.
August 14, 201312 yr Author It was a share on that drive only and I moved it to all the drives, and making all the shares use all the drives, that's why it's empty now. I moved my data out of the drive 1 (which was DATA share, excluding the other 9 drives) Now my DATA is part of the other 9 drives and when I put this new drive in, im going to include all drives on all the shares.
August 16, 201312 yr Author Got new drive, pre-cleared it (took 28 hrs. 12 min. for 2.0 TB EARX) Got 0 errors on new drive. Rebuilding un-array (LOL) now, 4 hrs. left, 0 errors. RMA'd the drive with WD, advanced (they charged me $150 + 9.75 tax??? <--(they get u somewhere, eh?) They send me new drive while they wait for mine and after they receive my old drive they refund (not sure if I get tax back.) Sending old drive tomorrow and used their mailing label ($6~ via UPS) Thank you all for your help!!! EDIT: 2 hrs. 28 min. with 0 errors! (forgot I had to click on the MAIN tab to refresh)
August 16, 201312 yr Author A bit Off-Topic...but... Why running 5.0 rc16c there is no /dev/sda? My /dev/sda became /dev/sdb and so on... ? EDIT: Never mind, I just noticed on unmenu that /dev/sda1 is my flash drive now, it used to be /dev/sdf1...
August 17, 201312 yr Author After the rebuild, does it run a parity check automatically? Should I let it run? It rebuild with 0 errors.... Thanks.
August 18, 201312 yr Author I let it run, took a while but everything was ok. It was an empty drive so not sure what it was trying to read.. LOL Thanks for your help!
August 18, 201312 yr It was an empty drive so not sure what it was trying to read.. LOLIt was verifying that all the empty space was readable and correctly accounted for on the parity drive. Unraid uses all remaining array disks in full to reconstruct a missing disk, so it's imperative that all the space on all the drives is readable and correct. That is why a periodic (monthly for most) parity check is so important.
August 18, 201312 yr Author It was an empty drive so not sure what it was trying to read.. LOLIt was verifying that all the empty space was readable and correctly accounted for on the parity drive. Unraid uses all remaining array disks in full to reconstruct a missing disk, so it's imperative that all the space on all the drives is readable and correct. That is why a periodic (monthly for most) parity check is so important. Yeah, the Verify does make sense after a rebuild (after giving it some more thought, it's not verifying the new drive, it's verifying the parity consistency)
Archived
This topic is now archived and is closed to further replies.