Jared Potter
Dabbler
- Joined
- Jan 30, 2015
- Messages
- 18
Hello all, I'm new to this Forum as I usually direct my questions/problems to the NCIX Forum but since I'm new to FreeNAS/ NAS's in general I figured I should direct my questions here as well even though the problem is mostly hardware... However there have been some "security" emails sent each night that might be the system telling me there was a problem... Not that I have yet been able to figure out what most of the data means yet. (Yay learning!) Thanks for your help, sorry this is a copy and paste from the other post and is hastily edited.
So last week...to the day... I built my first NAS using FreeNAS Everything's been working pretty smoothly learning as I go along and finding I get a nightly report emailed to me with mostly useless information(to me at least) A couple times I've gone to access the NAS and found it powered down but with no real information as to what has happened I've just assumed it crashed. Powers up and resumes without a problem. SMART checks and scrubs all come back clean but a couple times I've received a "security report" with this:
Quote:
> (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 18 a2 60 40 a5 00 00 01 00 00
> (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
> (ada1:ahcich1:0:0:0): Retrying command
coming up three times, one each night in a row.
Upon doing research most people say it's probably a faulty cable but they also report dozens or hundreds of these errors. I only get one... and when I did a scrub and a short SMART test both came back clean. They recommended replacing the SATA cable as an easy suggestion. That was what I was going to do today before the system failed.
This morning I came to wake up and again find the NAS powered down but this time at 0300 with a big long security report. Some of it I understand as it's sort of a summary of the changes I've done like playing with adding and removing the media servers. But this time when I go to turn it back on I just get an infinite power cycle, 1 second on with lights fans spin then off.. repeat repeat repeat.
So I took it apart and did a paperclip test on the PSU which powered on and idled nicely. I re-seated everything and re fiddled with the cables to clean it up a bit more but no dice. The system immediately starts the power cycling again... Is the MOBO dead!? I spent a tonne of money on this system I've never had a system dead in a week before.
Specs:
ASRock Motherboard E3C226D2I Server mobo
Kingston KVR16E11/8 8GB DDR3-1600 ECC CL11 DIMM W/TS Memory x2
Itel Pentium G3220 Dual Core 3.0GHZ Processor LGA1150 Haswell 3MB Cache Retail
Corsair CX Series CX600M 600W ATX 12V 80 Plus Bronze Modular Power Supply
6x3TB WD-Red NAS HDD they're configured in a RaidZ2 setup and have been working really well
as well as a 16GB kingston flash drive for the FreeNAS OS.
Everythings connected to a 1000VA UPS
I know the PSU is a bit on the overpowered side but it was what was needed to get a enough sata power cables.
After the system failed to boot/post I swapped ada1's sata cable like the forums suggested anyways and also repleaced a second cable that is horribly bent sideways fro the chassis closing and pushing against it but I can't see the HDD/cables being an issue for the system not posting.
Thanks!
So last week...to the day... I built my first NAS using FreeNAS Everything's been working pretty smoothly learning as I go along and finding I get a nightly report emailed to me with mostly useless information(to me at least) A couple times I've gone to access the NAS and found it powered down but with no real information as to what has happened I've just assumed it crashed. Powers up and resumes without a problem. SMART checks and scrubs all come back clean but a couple times I've received a "security report" with this:
Quote:
> (ada1:ahcich1:0:0:0): WRITE_FPDMA_QUEUED. ACB: 61 00 18 a2 60 40 a5 00 00 01 00 00
> (ada1:ahcich1:0:0:0): CAM status: Uncorrectable parity/CRC error
> (ada1:ahcich1:0:0:0): Retrying command
coming up three times, one each night in a row.
Upon doing research most people say it's probably a faulty cable but they also report dozens or hundreds of these errors. I only get one... and when I did a scrub and a short SMART test both came back clean. They recommended replacing the SATA cable as an easy suggestion. That was what I was going to do today before the system failed.
This morning I came to wake up and again find the NAS powered down but this time at 0300 with a big long security report. Some of it I understand as it's sort of a summary of the changes I've done like playing with adding and removing the media servers. But this time when I go to turn it back on I just get an infinite power cycle, 1 second on with lights fans spin then off.. repeat repeat repeat.
So I took it apart and did a paperclip test on the PSU which powered on and idled nicely. I re-seated everything and re fiddled with the cables to clean it up a bit more but no dice. The system immediately starts the power cycling again... Is the MOBO dead!? I spent a tonne of money on this system I've never had a system dead in a week before.
Specs:
ASRock Motherboard E3C226D2I Server mobo
Kingston KVR16E11/8 8GB DDR3-1600 ECC CL11 DIMM W/TS Memory x2
Itel Pentium G3220 Dual Core 3.0GHZ Processor LGA1150 Haswell 3MB Cache Retail
Corsair CX Series CX600M 600W ATX 12V 80 Plus Bronze Modular Power Supply
6x3TB WD-Red NAS HDD they're configured in a RaidZ2 setup and have been working really well
as well as a 16GB kingston flash drive for the FreeNAS OS.
Everythings connected to a 1000VA UPS
I know the PSU is a bit on the overpowered side but it was what was needed to get a enough sata power cables.
After the system failed to boot/post I swapped ada1's sata cable like the forums suggested anyways and also repleaced a second cable that is horribly bent sideways fro the chassis closing and pushing against it but I can't see the HDD/cables being an issue for the system not posting.
Thanks!