August 14, 201015 yr Hi, Yesterday i bought my pro licence so i installed a fresh new system. Now i have some trouble with my new WD20EARS drives. What is did: - added the WD20EARS to the unRAID box with a jumper on pin 7-8. (one WD20EARS parity drive the other data drive). - added several other greenpower drives. - Started unRAID - added the drives onto the device list. - format all drives on the main page. - i canceled the parity-sync, because i first want to copy all data over. Later do the parity sync. When everything runs fine delete the data which i copy over to the unRAID box. Now the problem when i copy data to my WD20EARS drive, coping is very slow, stuttering. It begins with 28MB/sec for a few seconds then goes back to 720KB/sec (with a lot of stuttering, hanging). Not good.., did i do something wrong? Please some advice and help. I'm also checking the forum now... To be clear i have a backup of all my data. Losing data onto unRAID box is not a problem.
August 14, 201015 yr Not good.., did i do something wrong? Please some advice and help. I'm also checking the forum now... Only way to know what is happening is for you to post a copy of your syslog. Instructions under "troubleshooting" in the wiki.
August 14, 201015 yr Also worth looking at the output from smartctl for the dodgy drive. Maybe a dodgy cable? or reallocated sectors?
August 14, 201015 yr Now the problem when i copy data to my WD20EARS drive, coping is very slow, stuttering. It begins with 28MB/sec for a few seconds then goes back to 720KB/sec (with a lot of stuttering, hanging). Not good.., did i do something wrong? Please some advice and help. I'm also checking the forum now... To be clear i have a backup of all my data. Losing data onto unRAID box is not a problem. your syslog doesn't show any abnormal after you aborted parity sync, however now sure i follow you correctly because your syslog show you have only ONE 2TB in unRAID domain, so i assume this one should be the parity disk, how can you copy data to this WD20EARS? you copy data to data disk NOT parity disk. If what you want to do is saving time in copying over by skipping parity then (a) take parity disk offline (keep in mind, no protection from now on) (b) copy all data over to data disks. © Put parity disk back and let unRAID kick off parity rebuild. --------------------------- from your syslog ------------------------------------------------------------------------ Aug 14 13:26:49 Tower kernel: md1: running, size: 1953514552 blocks Aug 14 13:26:49 Tower kernel: md2: running, size: 976762552 blocks Aug 14 13:26:49 Tower kernel: md3: running, size: 976762552 blocks Aug 14 13:26:49 Tower kernel: md4: running, size: 976762552 blocks Aug 14 13:26:49 Tower kernel: md5: running, size: 976762552 blocks Aug 14 13:26:50 Tower emhttp: shcmd (22): udevadm settle Aug 14 13:26:50 Tower emhttp: shcmd (23): mkdir /mnt/disk2 Aug 14 13:26:50 Tower emhttp: shcmd (23): mkdir /mnt/disk1 Aug 14 13:26:50 Tower emhttp: shcmd (23): mkdir /mnt/disk3 Aug 14 13:26:50 Tower emhttp: shcmd (23): mkdir /mnt/disk4 Aug 14 13:26:50 Tower emhttp: shcmd (23): mkdir /mnt/disk5 Aug 14 13:26:50 Tower kernel: mdcmd (16): check Aug 14 13:26:50 Tower kernel: md: recovery thread woken up ... Aug 14 13:26:50 Tower kernel: md: recovery thread syncing parity disk ... Aug 14 13:26:50 Tower kernel: md: using 1152k window, over a total of 1953514552 blocks. Aug 14 13:29:33 Tower kernel: mdcmd (39): nocheck Aug 14 13:29:33 Tower kernel: md: md_do_sync: got signal, exit... Aug 14 13:29:33 Tower kernel: md: recovery thread sync completion status: -4
August 14, 201015 yr Aug 14 13:26:40 Tower kernel: md: import disk0: [8,0] (sda) WDC WD20EARS-00M WD-WMAZA0008941 offset: 63 size: 1953514552 Aug 14 13:26:40 Tower kernel: md: import disk1: [8,16] (sdb) WDC WD20EARS-00M WD-WMAZA0183850 offset: 63 size: 1953514552 looks ok to me(?)
August 14, 201015 yr Aug 14 13:26:40 Tower kernel: md: import disk0: [8,0] (sda) WDC WD20EARS-00M WD-WMAZA0008941 offset: 63 size: 1953514552 Aug 14 13:26:40 Tower kernel: md: import disk1: [8,16] (sdb) WDC WD20EARS-00M WD-WMAZA0183850 offset: 63 size: 1953514552 looks ok to me(?) Sigh.... I forget parity disk has no filesystem.
August 14, 201015 yr Author Also worth looking at the output from smartctl for the dodgy drive. Maybe a dodgy cable? or reallocated sectors? Hi Chris Pollard, The cables were fine yesterday. I experiment with unRAID for a couple of weeks, and had no issues. I used a couple of 1TB drives.
August 14, 201015 yr Author Aug 14 13:26:40 Tower kernel: md: import disk0: [8,0] (sda) WDC WD20EARS-00M WD-WMAZA0008941 offset: 63 size: 1953514552 Aug 14 13:26:40 Tower kernel: md: import disk1: [8,16] (sdb) WDC WD20EARS-00M WD-WMAZA0183850 offset: 63 size: 1953514552 looks ok to me(?) Sigh.... I forget parity disk has no filesystem. Hi GK20, Thanks for thinking along. Appreciated, but i do really have two WD20EARS!
August 14, 201015 yr Author I did some further investigation. I reinstalled unRAID and swapped data and parity drive (WD20EARS), and disconnected all other drives. Same problems lots of stuttering hanging during copying. I also removed the jumper from pin 7-8, and formated the drives again. Same problem. I decided to take the drives out of the unRAID box and test the drives onto a Windows 7 box. The drives are running fine with a jumper om pin 7-8, and without a jumper on pin 7-8.
August 14, 201015 yr Author If what you want to do is saving time in copying over by skipping parity then (a) take parity disk offline (keep in mind, no protection from now on) (b) copy all data over to data disks. © Put parity disk back and let unRAID kick off parity rebuild. What i did i unassigned the parity drive. I have now only one WD20EARS as data drive attached. Copying goes smoothly... If you first want to copy your data to the unRAID box (new installed system) you have to unassign the parity drive? Later one when you want to do the parity, assign the drive back again?
August 14, 201015 yr you dont have to but it makes for much faster file tranfers in most cases. If what you want to do is saving time in copying over by skipping parity then (a) take parity disk offline (keep in mind, no protection from now on) (b) copy all data over to data disks. © Put parity disk back and let unRAID kick off parity rebuild. What i did i unassigned the parity drive. I have now only one WD20EARS as data drive attached. Copying goes smoothly... If you first want to copy your data to the unRAID box (new installed system) you have to unassign the parity drive? Later one when you want to do the parity, assign the drive back again?
August 14, 201015 yr Author you dont have to but it makes for much faster file tranfers in most cases. If what you want to do is saving time in copying over by skipping parity then (a) take parity disk offline (keep in mind, no protection from now on) (b) copy all data over to data disks. © Put parity disk back and let unRAID kick off parity rebuild. What i did i unassigned the parity drive. I have now only one WD20EARS as data drive attached. Copying goes smoothly... If you first want to copy your data to the unRAID box (new installed system) you have to unassign the parity drive? Later one when you want to do the parity, assign the drive back again? Thanks dogmanky for your reply. Ok, i understand. Following question when i assign (new installed system) a data drive and parity drive. I cancel the parity sync, and copying everything to the newly installed unRAID box. What happens? Lots of stuttering, hanging during copying?
August 15, 201015 yr Author Morning to you all, I want you to no my unRAID server in running smoothly now. The array is sync. ?I don't have a clue what was wrong yesterday (maybe i had a bad day). To be sure a i have replaced the jumpers (WD20EARS). Not sure that was the reason for the odd behavior. I like the cache drive feature it really speeds up copying. Great! I'm very happy with my pro license. I converted my old WHS to unRAID server, and in the feature i want to replace and add extra hardware. I have now 6TB of storage, and 2TB of parity. So my drive bays and sata ports are full. I can now stream 1080P Blu-ray without any stuttering. You don't want to try this with Windows Home Server. Thanks for your time and help Joe L. , Chris Pollard , GK20 , dogmanky.
Archived
This topic is now archived and is closed to further replies.