dave Posted February 16, 2012 Share Posted February 16, 2012 If the current_pending_sector count increases after a parity check, does that indicate it's dying? I assume so.... based on that, I plan to copy all of the data (lucky only ~200gb) off of it onto a good disk. Will parity recognize this change right away and then when I pull the dying disk out no problems will occur? I assume so on this as well, but want to make sure before I send it off to WD for RMA while it's under warranty. Thanks!!! PS: Yes, I realize my unmounted disk is probably dying too. Luckily it's under warranty still as well. Link to comment
marcusone Posted February 16, 2012 Share Posted February 16, 2012 You can move the data off no issue and parity will update. But if you remove the drive unraid will complain but still run. If you lose another disk your sol as you cant recover from multi disk failures. You dont have a backup? Before RMA id run a preclear and see what happens. Or do advanced RMA and wait for new drive then send failed one Sent from my SGH-I727R using Tapatalk Link to comment
dave Posted February 17, 2012 Author Share Posted February 17, 2012 You can move the data off no issue and parity will update. But if you remove the drive unraid will complain but still run. If you lose another disk your sol as you cant recover from multi disk failures. You dont have a backup? Before RMA id run a preclear and see what happens. Or do advanced RMA and wait for new drive then send failed one Sent from my SGH-I727R using Tapatalk I do have a backup, it is disk3. That's why it's in there. My server is crashing during a copy from disk2 to disk3 - what could be causing that? The syslog isn't capturing the error from the previous reboot -- how do I figure out what is causing the crash? Link to comment
dgaschk Posted February 17, 2012 Share Posted February 17, 2012 This describes how to capture the syslog: http://lime-technology.com/forum/index.php?topic=9880.0 Link to comment
dave Posted February 17, 2012 Author Share Posted February 17, 2012 This describes how to capture the syslog: http://lime-technology.com/forum/index.php?topic=9880.0 I'll try to reproduce the hang/crash once the parity check is completed (in 3 hrs...). I guess it will have to wait until morning. Then I will telnet in and run the -tail command. Thanks! Link to comment
dave Posted February 17, 2012 Author Share Posted February 17, 2012 Was able to reproduce the issue this morning. All I am doing is copying data from disk2 to disk3. After about 15-20 minutes, a Network Error pop-up appears saying that there is a problem accessing \\tower\disk2. When this occurs, the web UI is not accessible, neither is telnet. Here are the last lines from the syslog from when the transfer began and to when the freeze/crash occurred: Feb 17 09:18:47 Tower kernel: r8169: eth0: link up Feb 17 09:19:18 Tower last message repeated 40 times Feb 17 09:20:22 Tower last message repeated 49 times Feb 17 09:21:23 Tower last message repeated 38 times Feb 17 09:22:28 Tower last message repeated 42 times Feb 17 09:23:30 Tower last message repeated 41 times Feb 17 09:24:34 Tower last message repeated 43 times Feb 17 09:25:35 Tower last message repeated 37 times Feb 17 09:26:36 Tower last message repeated 51 times Feb 17 09:27:40 Tower last message repeated 33 times Feb 17 09:28:42 Tower last message repeated 42 times Feb 17 09:29:43 Tower last message repeated 34 times Feb 17 09:30:50 Tower last message repeated 31 times Feb 17 09:31:51 Tower last message repeated 40 times Feb 17 09:33:02 Tower last message repeated 18 times Feb 17 09:34:05 Tower last message repeated 14 times Feb 17 09:35:07 Tower last message repeated 8 times Feb 17 09:36:10 Tower last message repeated 13 times Feb 17 09:37:15 Tower last message repeated 14 times Feb 17 09:38:18 Tower last message repeated 12 times Feb 17 09:39:24 Tower last message repeated 7 times Feb 17 09:40:32 Tower last message repeated 9 times Feb 17 09:41:49 Tower last message repeated 3 times Link to comment
Joe L. Posted February 17, 2012 Share Posted February 17, 2012 Was able to reproduce the issue this morning. All I am doing is copying data from disk2 to disk3. After about 15-20 minutes, a Network Error pop-up appears saying that there is a problem accessing \\tower\disk2. When this occurs, the web UI is not accessible, neither is telnet. Here are the last lines from the syslog from when the transfer began and to when the freeze/crash occurred: Feb 17 09:18:47 Tower kernel: r8169: eth0: link up Feb 17 09:19:18 Tower last message repeated 40 times Feb 17 09:20:22 Tower last message repeated 49 times Feb 17 09:21:23 Tower last message repeated 38 times Feb 17 09:22:28 Tower last message repeated 42 times Feb 17 09:23:30 Tower last message repeated 41 times Feb 17 09:24:34 Tower last message repeated 43 times Feb 17 09:25:35 Tower last message repeated 37 times Feb 17 09:26:36 Tower last message repeated 51 times Feb 17 09:27:40 Tower last message repeated 33 times Feb 17 09:28:42 Tower last message repeated 42 times Feb 17 09:29:43 Tower last message repeated 34 times Feb 17 09:30:50 Tower last message repeated 31 times Feb 17 09:31:51 Tower last message repeated 40 times Feb 17 09:33:02 Tower last message repeated 18 times Feb 17 09:34:05 Tower last message repeated 14 times Feb 17 09:35:07 Tower last message repeated 8 times Feb 17 09:36:10 Tower last message repeated 13 times Feb 17 09:37:15 Tower last message repeated 14 times Feb 17 09:38:18 Tower last message repeated 12 times Feb 17 09:39:24 Tower last message repeated 7 times Feb 17 09:40:32 Tower last message repeated 9 times Feb 17 09:41:49 Tower last message repeated 3 times That seems to say your ethernet connection keeps being re-established. (and it might just be a networking issue you are fighting) Link to comment
dave Posted February 17, 2012 Author Share Posted February 17, 2012 That seems to say your ethernet connection keeps being re-established. (and it might just be a networking issue you are fighting) If this is a networking issue, can I confirm it by directly connecting a monitor and keyboard to my server? In other words, I should be able to direct connect no problem to rule that it *IS* a networking issue. If I cannot connect directly, then it could be something else? Link to comment
dgaschk Posted February 17, 2012 Share Posted February 17, 2012 Connect a monitor an keyboard and see if you can copy the entire syslog to the flash once the network goes down. Link to comment
dave Posted February 17, 2012 Author Share Posted February 17, 2012 Connect a monitor an keyboard and see if you can copy the entire syslog to the flash once the network goes down. How do I do that? I'll try tonight, thanks. Link to comment
dgaschk Posted February 17, 2012 Share Posted February 17, 2012 Connect a monitor an keyboard and see if you can copy the entire syslog to the flash once the network goes down. How do I do that? I'll try tonight, thanks. See here: http://lime-technology.com/forum/index.php?topic=9880.0 Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.