Joe L. Posted September 30, 2008 Share Posted September 30, 2008 Installed two more drives in the machine yesterday. Whilst it was clearing it crashed, so I re-ran it using the tail -f /var/log/syslog > /boot/syslog command. Find attached the results. Does it say anything? Fortunately, the machine is now at work, so it's easier to get up on the bench and work on. The only think I see that looks the least bit odd are the lines I highlighted in RED in this sample from your syslog. Because of their irregular timing, I'm guessing you were pressing the "Refresh" button on the web-interface to get an updated status? Sep 30 10:33:29 unRAID1 kernel: [ 2696.408248] md3: new disk Sep 30 10:33:29 unRAID1 kernel: [ 2696.554022] md4: new disk Sep 30 10:33:44 unRAID1 kernel: [ 2711.264360] md3: new disk <- 15 seconds later Sep 30 10:33:44 unRAID1 kernel: [ 2711.288264] md4: new disk Sep 30 10:33:51 unRAID1 kernel: [ 2717.980197] md3: new disk <- 6 seconds later Sep 30 10:33:51 unRAID1 kernel: [ 2717.990441] md4: new disk Sep 30 10:35:33 unRAID1 emhttp[1404]: ... clearing 21% complete Sep 30 10:37:38 unRAID1 emhttp[1404]: ... clearing 22% complete Sep 30 10:39:43 unRAID1 emhttp[1404]: ... clearing 23% complete Sep 30 10:40:16 unRAID1 kernel: [ 3102.684424] md3: new disk <- 4 1/2 minutes later Sep 30 10:40:16 unRAID1 kernel: [ 3102.686134] md4: new disk Sep 30 10:41:45 unRAID1 emhttp[1404]: ... clearing 24% complete Sep 30 10:42:27 unRAID1 kernel: [ 3232.983833] md3: new disk <- 30 seconds later Sep 30 10:42:27 unRAID1 kernel: [ 3233.038071] md4: new disk Sep 30 10:42:28 unRAID1 kernel: [ 3234.609140] md3: new disk <- 1 second later Sep 30 10:42:28 unRAID1 kernel: [ 3234.629783] md4: new disk Sep 30 10:43:47 unRAID1 emhttp[1404]: ... clearing 25% complete Sep 30 10:45:26 unRAID1 kernel: [ 3412.282231] md3: new disk <- 3 minutes later Sep 30 10:45:26 unRAID1 kernel: [ 3412.361517] md4: new disk Sep 30 10:45:48 unRAID1 emhttp[1404]: ... clearing 26% complete There are no other clues in the supplied syslog segment that I can see. Usually, a crash like this is hardware related, so suspect memory and power supply first, then everything else. Joe L. Quote Link to comment
Cessquill Posted September 30, 2008 Author Share Posted September 30, 2008 Could be my doing a refresh, yes. Having not added disks since initial build, I was probably trying to work out time remaining until live (something which disk clearing doesn't tell you). Probably got carried away and bored waiting I let the supplied memory test run from Friday midday to Monday morning, cycled through 173 times without error. Does that rule out memory problems, or could it still be that? Could quite easily be the power supply - it was one I bought with the case. I'd happily switch it out for a reliable one, since when I bought it I was far too noob to think it'd matter Thanks Joe L EDIT: I was also refreshing to see the status of the existing hard drives, since the spin down seems unpredictable on them. Quote Link to comment
Cessquill Posted January 6, 2009 Author Share Posted January 6, 2009 Hi guys - I had to put this problem on hiatus, as work went crazy. Anyways - I plugged the server in again today, upgraded the flash drive to 4.4, and tried performing actions that used to crash it, and it's been fine so far. Copying a DVD folder from one drive to another used to crash it, but it appears to be much happier, which I'm guessing could be down to an updated version of linux. Thanks for all your help on this, and so far so good... Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.