docspectre Posted January 20, 2018 Share Posted January 20, 2018 I have been using unRaid for a few weeks. Pretty happy so need to add some more disks - upgrading parity and data. Thought I bought 2x7200rpm disks, but the WD Red isn't Pro so it's 5900rpm. The other drive is 7200rpm. Both passed preclear. Rebuilding my parity now on my HP Gen 8 without write cache enabled (because I haven't got a UPS ). Using the WD Red gives ~37mpbs speed. Not great. So, would I benefit from stopping the rebuild and changing to the 7200rpm as parity and 5900 for data? Main data is media storage and PC backups. For future I intend to get another 7200rpm, which means that my options will be: 6tb 5900 parity 6tb 7200 data 6tb 7200 data or 6tb 7200 parity 6tb 5900 data 6tb 7200 data Or should I find another use for the WD Red? Link to comment
JorgeB Posted January 20, 2018 Share Posted January 20, 2018 14 minutes ago, docspectre said: Rebuilding my parity now on my HP Gen 8 without write cache enabled (because I haven't got a UPS ). Using the WD Red gives ~37mpbs speed. Not great. That's normal with write cache disable, no point in getting different disks, it will be the same. Link to comment
docspectre Posted January 20, 2018 Author Share Posted January 20, 2018 1 minute ago, johnnie.black said: That's normal with write cache disable, no point in getting different disks, it will be the same. Thought so. I will have to look at UPS option and then enable write cache. After the parity is built, do the different disk speeds between parity and data matter too much? Link to comment
JorgeB Posted January 20, 2018 Share Posted January 20, 2018 It will matter for all writes, especially if you enable turbo write, and any disk rebuild. Also note that most boards, including server boards like Supermicro, come with no such setting and write cache is always on, but it recommended to have an UPS for a file server. Link to comment
docspectre Posted January 20, 2018 Author Share Posted January 20, 2018 Hmm, I think I will wait it out and see how it goes. Only 1 day, 22 hours, 26 minutes until the parity sync is finished .. Link to comment
tdallen Posted January 20, 2018 Share Posted January 20, 2018 Your parity drive has to be at least as large as a your largest data drive, and as a best practice it should be at least as fast as your fastest data drive. That said, I'd probably wait until you get the new 7200rpm drive and then add it as parity when you do. You won't notice much difference in the meantime. Link to comment
docspectre Posted January 21, 2018 Author Share Posted January 21, 2018 13 hours ago, tdallen said: Your parity drive has to be at least as large as a your largest data drive, and as a best practice it should be at least as fast as your fastest data drive. That said, I'd probably wait until you get the new 7200rpm drive and then add it as parity when you do. You won't notice much difference in the meantime. Yeah, I will have to wait until then - thanks. I'll probably get a UPS at the same time. Link to comment
SSD Posted January 21, 2018 Share Posted January 21, 2018 I don't have a ups and run unRaid with default write cache settings. Power cuts are very rare, but they do happen once or twice a year. I used to get occasional sync errors when it happened, but have not seen one in ages. Even when I got the occasional sync error, I never had corruption on the data disk. I'm not sure exactly what you disabled, but I'd go back to default settings. My disk contains a mix of drives including slower WD REDS and parity build runs at about 140 MB/sec. 37 way too slow! Link to comment
witalit Posted January 21, 2018 Share Posted January 21, 2018 Sorry to piggy back off this thread but its pretty relevant. I had a power cut the other night as a bulb blew, I don't have a UPS so my server had unexpected shutdown. Parity disk was disabled so I started a parity sync again. Sync completed but drive is still disabled, any ideas what I can do? I need to get a UPS I know and I have write cache and turboboost enabled. Had power cuts before its been fine but this times something has gone wrong. Do I need to completely wipe the parity drive before re-sync? Diags attached. unraid-diagnostics-20180121-1121.zip Link to comment
Squid Posted January 21, 2018 Share Posted January 21, 2018 I would reseat the cabling to your parity disk, as it dropped, then reconnected, but a write error ensued causing it to be disabled Also, disable debugging on the Auto Turbo Write plugin. Link to comment
JorgeB Posted January 21, 2018 Share Posted January 21, 2018 26 minutes ago, SSD said: I'm not sure exactly what you disabled, but I'd go back to default settings. That is the default settings for Microservers, at least gens 7 and 8, but I would enable it even without an UPS, though IMO one should be used. Link to comment
witalit Posted January 21, 2018 Share Posted January 21, 2018 6 minutes ago, Squid said: I would reseat the cabling to your parity disk, as it dropped, then reconnected, but a write error ensued causing it to be disabled Also, disable debugging on the Auto Turbo Write plugin. Thanks let me try that and report back! Link to comment
JorgeB Posted January 21, 2018 Share Posted January 21, 2018 3 minutes ago, witalit said: Thanks let me try that and report back! Since it's a MIcroserver and no cables to re-seat I would swap slots with a different disk and try again, in case it happens again see if it follows the disk or stays with the slot. Link to comment
witalit Posted January 21, 2018 Share Posted January 21, 2018 6 minutes ago, johnnie.black said: Since it's a MIcroserver and no cables to re-seat I would swap slots with a different disk and try again, in case it happens again see if it follows the disk or stays with the slot. I am actually just in the process of building a new build so I could just take all the disks out and see if its fine in the new box? extended self-test currently running should I wait for this to complete or can I cancel it? Link to comment
JorgeB Posted January 21, 2018 Share Posted January 21, 2018 1 minute ago, witalit said: I am actually just in the process of building a new build so I could just take all the disks out and see if its fine in the new box? yes 1 minute ago, witalit said: extended self-test currently running should I wait for this to complete or can I cancel it? as you prefer, since it doesn't take that long on a 2TB disk might as well let it finish Link to comment
witalit Posted January 21, 2018 Share Posted January 21, 2018 1 minute ago, johnnie.black said: yes as you prefer, since it doesn't take that long on a 2TB disk might as well let it finish Thanks man. Here is a link to my new build just for reference! Machine is built will be updating build log today, just waiting for the disks to be swapped. Link to comment
witalit Posted January 21, 2018 Share Posted January 21, 2018 OK server built, SMART test seemed to complete not errors. Parity drive still disabled. I'm trying to re-sync parity again, only thing I can think of. Link to comment
JorgeB Posted January 21, 2018 Share Posted January 21, 2018 You need to re-enable the drive and re-sync parity Link to comment
witalit Posted January 22, 2018 Share Posted January 22, 2018 23 hours ago, johnnie.black said: You need to re-enable the drive and re-sync parity Seems the 2nd re-sync in new build has fixed my issues. Thanks Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.