When the UNraid powers up it was hanging at the screen after checking both 8 channel raid cards. 1 card would sometimes give me a problem error and need to power down and reseat the card/cables. That seemed to fix the problem. Over the last week when I would start the UNraid It would hang on the bios/press space bar to continue. If I left it there for say 5 min it would continue on very slowly. Then up pops the blue screen as normal and with UNraid or check memory. The system would boot and get to the final Login: I can see the UNraid computer on each computer of the network (Windows7) I can click on the icon under network computers and access it only to see the flash drive. all other drives are missing. I am unable to access the UNraid box by IE GUI using its name or the 192.168.1...blah blah. Also I've experienced slow raid card check times. For giggles I switched both 8 channel cards leaving the cables connected to opposite slots. I rechecked all SATA and power connections. Powered up the UNraid and the cards checked much faster and UNraid started much faster getting me to the Login: But each computer still only lets me see the flash drive. Could the UNraid be rebuilding parity and not allow me access? It doesn't feel like I'm up the creek and lost it all as I've had trouble in the past with both UNraid servers not being accessible in the GUI or Windows and eventually they come on line. So folks any ideas as to what the problem might be?

running Unraid Rev5  beta12a

Tried moving to unRAID Server 5.0-rc5 AiO

Still get the same thing.

Thank you for your time,

Chris

 

I dug a little more to find out that it wont accept a connection. Could it be that unraid is doing somthing in the back ground and I need to wait it out? There is no noise or hard drive light indicating it's doing anything. I've force turned it off a couple times upgrading the software and all still give me the flash folder on windows 7 machines. all drives are powered on for sure pulling full watts. So I know that much monitoring it. Is there any way to also go into the USB drive and change the auto start unraid to off and atleast be able to see the drives and whats going on? Do I maybe need to rebuild my USB fresh and apply pro license and when starting unraid it asks me to reconfigure the order of the drives?

Thank you again,

Chris

This is what I see on my Windows7 Machines.

Is sharing enabled?

It was when it went down. I'm talking about the GUI I've had sharing turned on there for many months. It's like the drive and the shared folders just fell off. As you can see the only thing I can now see is the flash folder. Also the same with my XBMC machines. I just wish there was a way to tell what it's doing if the telnet screen just says login:

Attach a syslog. See the sticky in this forum.

It was when it went down. I'm talking about the GUI I've had sharing turned on there for many months. It's like the drive and the shared folders just fell off. As you can see the only thing I can now see is the flash folder. Also the same with my XBMC machines. I just wish there was a way to tell what it's doing if the telnet screen just says login:

there is

 

You log in as "root" and can then type

mount

to see the mounted disks

and

smbstatus

to see the samba shared drive status

and

smbclient -N -L localhost

to see the actual shares being advertised

and

/root/mdcmd status | strings | grep -i Sta

to get a general status of the array and disks

and

tail -n 100 /var/log/syslog

to see the last 100 lines of the syslog to see if the file systems are being mounted.

 

The usual way to get more assistance is to supply a copy of your syslog for analysis.

 

Thank you for that information. I have logged in using putty. Is there any way to get what I see copied from there or save to the USB so that I may post the System log. I know that’s important.

 

Okay I got it.

The second file below is everything else mentioned above plus syslog.

Thank you for your help and time in this matter.

Chris

R2D2_syslog.txt

R2D2_login.pdf

So thinking out loud. If I take the usb running my unraid server and put it into another computer and started it up shouldn't it default to the GUI screen and not run? Giving me the oppertunity to see if it's maybe something wrong on the USB that needs correcting if it does'nt get there to the GUI?

Okay after pluging the USB Flash into another computer I'm able to see thg e UNraid server in the GUI of course looking for all 18 drives. Okay now I went in to the setting screen and told it to not auto turn on. Saved that and went to shut down check box and the shutdown. Computer turned off. I then took the USB over to the server force the power off.(TAKE NOTE THE ARRAY was NOT running) Plugged in the USB and turned on the server. Everything was nice and fast on the boot up which I had noticed after swaping card slots with the 8 Ch card. The system is now accessible in the GUI. I'm gonna start the raid and let it run parity. It should be done by this time tomorrow. lol. I just really wish I could figure out what went wrong. Then again I'm not out of the woods yet. Parity has to pass for sure. I'll report back... Thanks again folks

Okay it looks like the woods are getting thicker. I clicked Identify to check all the disks. Each drive read fine. All drives are green dot's so it looks good there. I tried to start the array but it just sat there. The GUI screen went white fade like it was going to the next screen where you see all drives mounted and running parity. But it's not going. I Properly Shut Down. I rebooted and I'm attaching a system log this this message. All help is needed and welcome.

Thank you in advance.

System_Log_Dec_21_16.txt

Next time something goes wrong do not restart the system. Restarting or shutting down without letting the array cleanly stop will cause file system errors. And can lead to the problems your experiencing. Next time something goes wrong ask for help. There is no way to determine the problem at this point.

Hello dgaschk

 

    And thank you for your response. To tell you I'm asking for help as you can see. I'm making progress even just getting the GUI back up and running. That in it self is a success. I've now gone over each drive and made sure that each drive is in order. They are. It seems when I click the start button to start the array the drives don't want to start, yet respond by pressing identify before pressing start. The unraid server seemes to just lock and become unresponsive after pressing start. I can still access it with telnet putty though. Now to tell you all that I've done is in no worse then a power outage could do to the system and the APC backup running out of power. Thats a bad shutdown. What if it's set to come on after power out in the bios? Then the power goes out again? This Unraid system has to be more stable then this. To say there is no way to determine the problem at this point is giving up on something before giving it all you can on something. Why post the system log if it doesn't help find the problem? Now I really do appreciate you looking into the problem for me but this system with all it's data can't be a full loss as it sits. There has to be a way. I'll just keep reading were I can and find some way to make this system come back up.

 

We need to look at the syslog when the system is not working correctly. Restarting without the proper procedure is akin to a sudden power loss and every time this happens the problem may be compounded. After a restart the syslog is started anew. When the system is misbehaving do not restart. That is the wrong thing to do and will make things worse. The next time the problem occurs, STOP. Collect a syslog and attach here. DO NOT RESTART THE SERVER. Leave it as it is. After reviewing the syslog we can determine the next course of action.

Hello Dgaschk and All,

 

      I'm posting a syslog I got through telnet the last 100 lines. It looks like there is sas errors. on ports working drive 15 on up. I'm wondering if that card/cable is bad. 19 and 20 don't have drives yet error as well which might be normal.  What the weird part is the GUI doesn't even want me to make a new unraid setup which again feels like something wrong with the software setup on the USB somewhere on it.

just an update on the progress. Thank for reading and helping where you can.

R2D2_telnet_after_pressing_start_array.txt

We need the entire syslog that contains a period when the system faulting. The longer the better.

Okay I'm hoping this will give the info needed. I went to 500 lines and that seem to be all available at this time. Unless it's available as a backup feature saved on the original USB drive.

Please take a look. Based on what I'm reading in this is the errors mentioned in the last couple pages of the drive errors. I ordered another raid card to replace this one if it's in fact bad. If not I can use it in my other raid box which unfortunately doesn't have this card to try out or I would. Also ordering extra cables for the card in case that’s the main problem and not the card. At least I'll have parts for future issues if they arise.

 

R2D2_Syslog_Telnet_500_lines_Dec_21_18drives.txt

See here: http://lime-technology.com/forum/index.php?topic=9880.0

Okay I've replaced the one raid card believed to be bad as well as both it's 4ch sata cables. The system boots to the unraid menu. Tried to start raid in maintenance mode. Parity check started and was cruzin' along for say 25 min. During which I check a couple times the speed rate and that everything was fine to leave it alone. The process was going to be about 6 hours which was alot faster then in the past. Came back to see if everything was fine at about that 25min mark and lost network. IE just spins looking for it. (Flash is still accessible thus the syslog.) Now in my past experiences I remembered seeing this happen but it may have been during pre-clear that that happened. I have included a full system log this time and the UNraid computer is still on and running. Any ideas as what to do now except wait? Any help would be great as I've tried several searches to find out if the unraid systems is not accessible during parity checks of any kind. With none to be found yet. Please help. Thank you

syslog_R2D2_12_29_2012.txt

Okay I've replaced the one raid card believed to be bad as well as both it's 4ch sata cables. The system boots to the unraid menu. Tried to start raid in maintenance mode. Parity check started and was cruzin' along for say 25 min. During which I check a couple times the speed rate and that everything was fine to leave it alone. The process was going to be about 6 hours which was alot faster then in the past. Came back to see if everything was fine at about that 25min mark and lost network. IE just spins looking for it. (Flash is still accessible thus the syslog.) Now in my past experiences I remembered seeing this happen but it may have been during pre-clear that that happened. I have included a full system log this time and the UNraid computer is still on and running. Any ideas as what to do now except wait? Any help would be great as I've tried several searches to find out if the unraid systems is not accessible during parity checks of any kind. With none to be found yet. Please help. Thank you

In maintenance mode all you'll see is the flash drive.

 

Let the parity check complete.  (in other words, wait)

The syslog looks fairly normal.

 

Joe L.

Thanks Joe L.

 

    Yes I understand that I will only see the flash drive. And it's good to hear it's looking normal. I was just concerned about loosing contact via IE and see whats happening during  parity check.

 

Thanks Joe L.

 

    Yes I understand that I will only see the flash drive. And it's good to hear it's looking normal. I was just concerned about loosing contact via IE and see whats happening during  parity check.

you should be able to log in via telnet or on the system console and type:

/root/mdcmd status | strings | grep sync

and see the sync (parity check) position incrementing

Hi All,

 

 

I've still running this parity check. Do you think it's still running okay? Just very slow. As you can see it's been a couple days so far. About 67hours give or take. I don't understand what these numbers mean except that  this mdResyncDt= is counting up. (Slow as all get out) The others stay the same.

This is a 2tb parity system with 18 drives. Normally it's done within 24 hours. Any idea's as whats going on? Do I need another system log post?

Guess I'll just wait it out as well.

 

 

 

root@R2D2:~# /root/mdcmd status | strings | grep sync

mdResync=1953514552

mdResyncCorr=1

mdResyncPos=88334552

mdResyncDt=162210

mdResyncDb=1550580

root@R2D2:~# /root/mdcmd status | strings | grep sync

mdResync=1953514552

mdResyncCorr=1

mdResyncPos=88334552

mdResyncDt=191744

mdResyncDb=1550580

root@R2D2:~# /root/mdcmd status | strings | grep sync

mdResync=1953514552

mdResyncCorr=1

mdResyncPos=88334552

mdResyncDt=236333

mdResyncDb=1550580

root@R2D2:~# /root/mdcmd status | strings | grep sync

mdResync=1953514552

mdResyncCorr=1

mdResyncPos=88334552

mdResyncDt=243813

mdResyncDb=1550580

root@R2D2:~#

 

I would expect the resync position to increment as well.  I'd send an e-mail to [email protected] and include a link to your prior post describing what you are seeing...  (an apparent frozen-in-place parity sync) and see what he thinks.

 

Yes, a current attached syslog will help too.

 

Joe L.

Okay Joe L. I did just that and I'm also posting the latest system log here. Man I hope I can get this fixed.

R2D2_System_Log_01_01_2013.txt