JorgeB Posted June 8, 2018 Share Posted June 8, 2018 11 hours ago, Imba said: Sigh, well it looks like I don't have that option. Sorry, yeah you need to use the command line, didn't notice you're still on v5. Link to comment
Imba Posted June 12, 2018 Author Share Posted June 12, 2018 Ok so I ran a long test on one of the drives, but I accidentally ran a test on a different drive so I started the test on the correct drive now and will post the result as soon as it's done. This is the smart report for Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA5742681 smartsdglong.txt Link to comment
JorgeB Posted June 12, 2018 Share Posted June 12, 2018 6 minutes ago, Imba said: This is the smart report for Device Model: WDC WD20EARS-00MVWB0 Serial Number: WD-WCAZA5742681 That one is fine for now. Link to comment
Imba Posted June 12, 2018 Author Share Posted June 12, 2018 Oh good, should I still consider replacing it in the near future or do I have more time than that? Link to comment
JorgeB Posted June 12, 2018 Share Posted June 12, 2018 29 minutes ago, Imba said: Oh good, should I still consider replacing it in the near future or do I have more time than that? It would be best to replace it when possible, though it can last for months or years without issues, very difficult to predict. Link to comment
Imba Posted June 13, 2018 Author Share Posted June 13, 2018 Finally here's the report for the other WD drive. smarthddlong.txt Link to comment
JorgeB Posted June 13, 2018 Share Posted June 13, 2018 4 minutes ago, Imba said: Finally here's the report for the other WD drive. smarthddlong.txt This one has failed and needs to be replaced now. Link to comment
Imba Posted June 13, 2018 Author Share Posted June 13, 2018 Sigh, so I'm not sure what I need to do now. I know there are something that I don't have backups of, and would need to try to retrieve and I know the drives need to be replaced but I'm how I should go about things now. I'm worried that everything is gonna be lost. Link to comment
JorgeB Posted June 13, 2018 Share Posted June 13, 2018 IMO your best bet it to create a new array with the known good disks (adding more new ones if needed for space) and then mount the failing disks with the UD plugin and copy everything you can to the array, you should be able to copy most data, alternatively you can use ddrescue to clone the disks and recover as much data as possible, then create a new array with all the good disks. Link to comment
JorgeB Posted June 13, 2018 Share Posted June 13, 2018 You'll need to update to v6 first though. Link to comment
trurl Posted June 13, 2018 Share Posted June 13, 2018 11 minutes ago, johnnie.black said: mount the failing disks with the UD plugin He's on 4.7 so no Unassigned Devices. You'd have to go to the command line to mount the disks. Or update to V6 if possible. Might have to add RAM to get a stable system though. V6 would be so very much easier to work with. Link to comment
Imba Posted June 13, 2018 Author Share Posted June 13, 2018 Would it be easier to upgrade to v6 or use the command line like trurl suggested? Link to comment
trurl Posted June 13, 2018 Share Posted June 13, 2018 Unless you already know enough linux to mount disks, there's going to be a learning curve either way. Did you look at the upgrade wiki I linked earlier? You could use your old version to set a New Config with only the good disks, sync parity, then worry about how to get the data from the other disks after that. I think an upgrade is really called for eventually in any case. Link to comment
Imba Posted June 13, 2018 Author Share Posted June 13, 2018 Yeah I'm not that linux savvy. Alright so how do I go about setting up the new config with the good disks and all that jazz? Link to comment
JorgeB Posted June 13, 2018 Share Posted June 13, 2018 IIRC on v4 it's on Utils -> New config You'll need to re-assign all your disks, make sure old parity is assigned to the parity slot, data disk order it's not important, unless you're including/excluding disks for any shares. Link to comment
Imba Posted June 13, 2018 Author Share Posted June 13, 2018 So I remove the failing drives and start the server back up? Or do I have to reformat the flash? I'm sorry I really have no idea how to go about this. Link to comment
Imba Posted June 13, 2018 Author Share Posted June 13, 2018 OH, would I Shut down the server Remove the Drives Start the server and do something like new config or assign drives then new config :3 Link to comment
JorgeB Posted June 13, 2018 Share Posted June 13, 2018 You only need to power down if you need to replace or add disks, if not just new config and assign the disks, then start the array to begin the parity sync. Link to comment
Imba Posted June 13, 2018 Author Share Posted June 13, 2018 Ok so power down > remove failing drives > new config, > assign drives > start array Should I plan on how to get the data on the failing drives or just focus on this part? Link to comment
Imba Posted June 13, 2018 Author Share Posted June 13, 2018 I'm not sure if this is something but I read about but should I do a parity check after the sync? Link to comment
JorgeB Posted June 13, 2018 Share Posted June 13, 2018 First let the sync finish so the array is protected then go about recovering the data on the failing disks, parity check after is optional but good practice. Link to comment
Imba Posted June 13, 2018 Author Share Posted June 13, 2018 So....here's an interesting development. I'm guessing it's like the hitachi so should I just remove that along with the other two failing drives? Link to comment
JorgeB Posted June 14, 2018 Share Posted June 14, 2018 If the disk is really failing yes, it could be a cable/connection issue, SMART report might help figure out which. Link to comment
Imba Posted June 14, 2018 Author Share Posted June 14, 2018 Is there a way to get the smart report without having to power down and plug the flash drive into another computer? NVM Figured it out. They array won't stop so I can shut it down. After waking up the monitor to do the smart report this is flashing on the screen: REISERFS error (device md5): -vs13070 reiserfs_read_locked_inode: i/o failure occured trying to find stat data of {30 172 0x0 SD] Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.