July 20, 201510 yr unRAID: version 5.0.5 MOBO: Asus M4A88T-M 880G CPU: AMD Sempron 145 2.8GHz RAM G.SKILL Ripjaws Series 2x2GB DDR3 1600 PSU Corsair CX 430 CASE Coolmaster Haf 932 HDDs: Samsung 6TB (parity) Western digital 6TB X2 Western Digital WD Green WD20EARX 2TB 64MB Cache SATA 6.0Gb/s X2 SAMSUNG Spinpoint F3 HD103SJ 1TB 7200 RPM 32MB Cache SATA 3.0Gb/s 3.5" Internal (cache) Hey guys. So the other day watching movie and abruptly stopped and couldn't access tower/home from pc so restarted the whole server. Now i cannot start the array and get online. Each time it resets the whole server when i hit the start button. I do relies I've been on 5.0.5 for long time and this would be probably be best time to upgrade to latest version but i want back up all my stuff but without having array online i can't pull the files i need. Also thinking of overhauling my whole tower build but since so lazy i thinking just using dirtysanchez's build.
July 20, 201510 yr Now i cannot start the array and get online. Each time it resets the whole server when i hit the start button. This happens abruptly, like a power cut (removed)? If so, sounds like a bad PSU to me.
July 20, 201510 yr Author There was no power cut unless the psu gave up so if that is the case should i should use this as an opportunity to change the parts over. It would seem the lights are on but no one is home. Works up until you hit start for array to go online then last thing i see is restart smb then nothing.
July 20, 201510 yr There was no power cut unless the psu gave up so if that is the case should i should use this as an opportunity to change the parts over. It would seem the lights are on but no one is home. Works up until you hit start for array to go online then last thing i see is restart smb then nothing. May be stating the obvious - but must a hardware problem. Power supplies, in my experience, often blink out all at once. If dying a slower death, often issues show up by difficulty powering up. This does not scream "PSU failure", but it could be. When starting the array after a dirty shutdown, the system would be starting a parity check. If a parity check is causing a hard crash then it could be related to a disk controller, MB or even a misbehaving disk. Hardware problems can be hard to diagnose. I might suggest creating a fresh memory stick to play with, and seeing if you can create a one disk array with no parity, and if you are able to start it, and build from there. If doing this type of debugging, don't do any writes to the array. If the server is old and you are considering an upgrade, this may not be a bad time ...
August 16, 201510 yr Author So after upgrading everything seems ok guess hardware problem although was rather dusty in case.
Archived
This topic is now archived and is closed to further replies.