My brand new Freenas setup has crashed and burned (I think).

[shelzmike]

I am new to Freenas. Bought a new whitebox system just for this purpose (using it as a place to store backups from Backup Exec). Setup went smooth and I had no issues. In fact, it ran fine (web interface, etc.) until after the first backup took place. I have two brand new 2TB sata drives setup in a RAID 0 (UFS).

Here are the server specs:
WD Caviar Green 2 TB Hard Drives (x2)
Intel Core 2 Quad/Intel P43/DDR3/A&GbE/ATX Motherboard (BOXDP43BF)
Intel Core 2 Quad CPU (BX80590Q8300)
Corsair 4GB Memory

After initial backup (which completed), I was getting that the RAID was degraded via FreeNas GUI. I was not in the office for the past 5 days though so I had not messed with it at all.

Came back in today and the screen was showing the following (over and over):
arp: 10.0.0.21 moved from 00:15:17:c4:f6:ed to 00:15:17:c4:f6:ec on bge0
arp: 10.0.0.21 moved from 00:15:17:c4:f6:ec to 00:15:17:c4:f6:ed on bge0

Again, this was over and over and over...and there was nothing that I could do but a dirty shutdown. Upon resume, even more hell was breaking loose in the following manner:
This was the first try at loading it up:

and then this is the second, and this is where it will go no further:

What are my options here. I mean, I know that SATA drives fail, but I am not sure in this situation because it is literally only like a week old. Not unheard of, but want to know what this is telling me before I do an RMA on the drive. Thanks.

 

[peterh]

the messages "arp: 10.0.0.21 moved ..." was by an ip duplicate address on the net ( or someone connecting 2 NIC's
using the same ip )

About your discs, ada1 seems screwed, you could continue your fsck "(run fsck manually" via the console as suggested)
it will clean up ada0 , then you could go multiuser ( just exit the shell). Afterwords you will have to replace ada1
with a fresh drive and have the gui replace it. Make shure you replace the right disc!!

 

[shelzmike]

Okay, I did a few things, so here is an update. #1, I changed in bios from AHCI to IDE because I do not need the hot-swappable capability here and I know that lots of times, AHCI causes these kinds of problems. Now, I also put the discs in a Windows Machine and ran WD's Data Lifeguard Diagnostics on both and they both come out clean so I am not sure what the deal is.

Once I did this, FreeNas boots with no issues at all anymore, which is weird. However, RAID Volume still says degraded. One thing I did notice was that it is 99% full, which may be an issue. THis was an oversight on my part and I made the wrong selections on Backup Exec, which I have since fixed so that it is not going to be that large any longer. When I try to to an in-place replace of ada1, it tells me that there was an error but offers no further information. The data is pretty much useless at this point since it is unrecoverable - in fact, Backup Exec is unable to even connect to it, though I can still see it via NTFS surfing. Is there a remedy to the error when replacing the drive getting the error? Or can I find logs somewhere that gives me a little more info?

WD Data Lifeguard has always been pretty spot on and since it says the discs are fine, and because they are less than a week old, I tend to believe it, so I want to use the same discs. Should I just export the volume and start all over again? Thanks!

Mike