Hi,

 

I just changed my case as I recently bought a Fractal Design R4 - I removed and replaced all my hardware from the old box to the new one.

 

Everything went well - except for the fact that i am nt able to access the web GUI or UU after the change. If connected to a monitor I can see that the boot process goes through fine and I can login and excute commands through the command line. But the tower in inaccessible when headless, not even via telnet (host not found).  I have verified that all the hardware and the connection via the NIC is working fine. Attaching the most recent syslog. ifconfig eth0 does return my IP address as it was before and ensures that the tower is connected to the net.

 

I have tried going stock 5.0.5 without any plugins but that hasn't worked either. Confirmed that the SATA controller is running in AHCI mode and that all the drives are being recognized at boot by the BIOS. So all hardware seems to be working fine - not sure why the web GUI is not coming up.

 

Any and all help is appreciated.

 

Thanks,

Abhi

syslog-20140314-114619.zip

You have a number of these:    Seagate Barracuda 7200.14 (AF)

 

I'm not sure how to read your log...it LOOKS like 3 or 4 different Seagates are FAILING NOW according to the SMART reports.

 

The probability that so many are failing together seems pretty low...I'm wondering about power/SATA expansion card or some other system failure is making it appear the drives are all failing at once.  My syslog skills aren't  good enough to pinpoint that.

 

BUT, there's something wrong..I would NOT write to the array until someone smart figures out what's happening.

You have a number of these:    Seagate Barracuda 7200.14 (AF)

 

I'm not sure how to read your log...it LOOKS like 3 or 4 different Seagates are FAILING NOW according to the SMART reports.

 

The probability that so many are failing together seems pretty low...I'm wondering about power/SATA expansion card or some other system failure is making it appear the drives are all failing at once.  My syslog skills aren't  good enough to pinpoint that.

 

BUT, there's something wrong..I would NOT write to the array until someone smart figures out what's happening.

 

WOW - that was not what I was hoping to hear! Thank you for looking at it though!

 

I have 6 Seagate Barracuda 7200.14 drives out of a total of 8 in the build. The other 2 are a Hitachi and a Samsung SSD (cache).

 

Only 7 out of these 8 are being used the 8th one is just a back up or an extra drive (2TB). It seems highly unlikely that all Seagate drives have failed at the same time (there are 6 of those messages in the log, one each for each of the drves), and I am hoping that this isn't the case.

 

Could I ask what does AF mean - is that what got you to think that these 6 are failing?

You have a number of these:    Seagate Barracuda 7200.14 (AF)

 

On googling the same it seems as though that the AF is just part of the model number/name - http://www.ebay.com/itm/Seagate-Barracuda-7200-14-AF-ST2000DM001-P-N-1CH164-515-FW-CC47-TK-/271352278444 - what in the log specifically leads you to belive that the drives are failing?

 

 

Don't have a heart attack!  I'm not the disk drive expert...you might wait for one of the real experts to check the syslog. 

• There's something about Seagates and SMART reports that is different than other drives' reports..there have been several threads about that...but I don't own any Seagates and didn't pay close attention.
  
• You have one Seagate drive that reports it wants a firmware update...again, there are threads on that. You may or may not want to update the drive's firmware.  There are pros and cons. Get a better opinion for your specific model of Seagate.
  
• And you have an error logged on your Hitachi drive.
  

Here are examples of what I saw in the SMART report:

Mar 14 11:46:11 Tower smartctl[5267]: Device Model:    ST3000DM001-9YN166

Mar 14 11:46:11 Tower smartctl[5267]: Serial Number:    Z1F0GEMK

...

Mar 14 11:46:11 Tower smartctl[5267]: 184 End-to-End_Error        0x0032  099  099  099    Old_age  Always  FAILING_NOW 1

Similar messages appear a couple of other places.

Then there's this message for the Hitachi drive:

Mar 14 11:46:15 Tower smartctl[5267]:

Mar 14 11:46:15 Tower smartctl[5267]: Error 1 occurred at disk power-on lifetime: 13106 hours (546 days + 2 hours)

Mar 14 11:46:15 Tower smartctl[5267]:  When the command that caused the error occurred, the device was active or idle.

Mar 14 11:46:15 Tower smartctl[5267]:

Mar 14 11:46:15 Tower smartctl[5267]:  After command completion occurred, registers were:

Mar 14 11:46:15 Tower smartctl[5267]:  ER ST SC SN CL CH DH

Mar 14 11:46:15 Tower smartctl[5267]:  -- -- -- -- -- -- --

Mar 14 11:46:15 Tower smartctl[5267]:  84 51 01 c7 00 00 00  Error: ICRC, ABRT at LBA = 0x000000c7 = 199

Mar 14 11:46:15 Tower smartctl[5267]:

Mar 14 11:46:15 Tower smartctl[5267]:  Commands leading to the command that caused the error were:

Mar 14 11:46:15 Tower smartctl[5267]:  CR FR SC SN CL CH DH DC  Powered_Up_Time  Command/Feature_Name

Mar 14 11:46:15 Tower smartctl[5267]:  -- -- -- -- -- -- -- --  ----------------  --------------------

Mar 14 11:46:15 Tower smartctl[5267]:  ca 00 00 c7 00 00 e0 ff      00:08:04.917  WRITE DMA

Mar 14 11:46:15 Tower smartctl[5267]:  ca 00 08 c0 00 00 e0 08      00:08:04.900  WRITE DMA

Mar 14 11:46:15 Tower smartctl[5267]:  c8 00 38 70 99 00 e0 08      00:08:04.900  READ DMA

Mar 14 11:46:15 Tower smartctl[5267]:  c8 00 08 68 99 00 e0 08      00:08:04.900  READ DMA

Mar 14 11:46:15 Tower smartctl[5267]:  c8 00 08 60 99 00 e0 08      00:08:04.900  READ DMA

Mar 14 11:46:15 Tower smartctl[5267]:

 

I'd wait for an informed opinion about the disk errors before writing anything to the array.

Okay Thank You DaleWilliams

I am glad we are talking about disk errors and I appreciate that very much. Will wait for someone to give some direction on whether these are actual indictors that I should be replacing the drives or do I have the liberty of ignoring it for sometime and replace them slowly. Since the threshold for this error is set at 99 I assume it is a critical fail. But the internet is awash with discussion on this and there are suggestions that sometimes this corrects itself by retransmitting the data. not sure what any of this means in this scenario.

 

All that said - I am still puzzled by the fact that I can't get the web GUI to come up? Would that be related to any of this as I said with a monitor connected it looks like the boot process goes through fine and I can log in - but I cannot access the tower headless not even via telnet. Chrome just rerturns a "oops chrome could not find tower" error when I know it is connected to the same home network through the

ifconfig eth0

results. I have a inet address showing on that.

 

Any ideas on why this is happening?

Does the GUI show up if you type in the IP address in the browser?

 

In that first syslog, your unRAID is at address 192.168.1.133

 

 

 

Does the GUI show up if you type in the IP address in the browser?

 

In that first syslog, your unRAID is at address 192.168.1.133

 

No. Tried with IP on the browser and putty but no luck.

Networking:

Are there TWO ethernet connectors on the back of your new unRAID box?  (you may be in the wrong socket)

Where the ethernet cable plugs into your unRAID, there should be little lights blinking to show active ethernet. (you may have a network controller problem)

On the OTHER end of that ethernet cable is either a switch or router...are there little lights blinking there? (..perhaps a differnet network controller interface problem)

 

Can  you access the unRAID box from your PC if you run an ethernet cable directly between the two? (removes all other network devices and likely failure points.)