Hello I recently upgraded to 5.0 and did the permission fix, followed instructions as per website. I noticed after I did a shutdown and reboot I could not access the GUI but I could access my disks.

 

I then decided to go back to my 4.7 backup. I can access the GUI config is valid, but I can not access my disks/shares anything?

 

How can I fix this ?

 

I can see TOWER in networking, but as soon as I try to connect I can't... GUI everything looks good, not sure how to get access back to my disks

 

I can not access my data, I am a little worried now everything in my array is gone... please help

 

I put 5.0 back on and

 

I managed to get it STARTED (in Maintenance Mode)  and a Parity-Check is in progress.

 

Total size:2 TB

Current position:

GB (0%)

Estimated finish:

1159 minutes

 

 

Hope this works !

If everything looks good, as in all drives (except maybe parity) with green dots, then it is unlikely anything has happened to your data.

 

How are you trying to access your drives? Windows, Apple, Linux, Telnet, Console?

windows, I just went to check on the parity sync process now, and cant get GUI up.... I can ping my server IP but cant access anything

 

Connecting To tower...Could not open connection to the host, on port 23: Connect

failed

 

trying to take a syslog from console, and when i type the command, it just says 'killed'

 

Nothing seems to be happening on the server, no hdd light going nothing, I am out of ideas, I almost want to get all data off (dont know where I can store it) then delete everything and start fresh. I have no idea how I am going to get access to my data back

 

 

Trying to upload my syslog but it is too big

here is syslog from 5.0

 

could I just start a fresh flash drive, and rebuild parity ? or will it rebuild blank ? do I lose all my data ... I wish i never upgraded to 5.0 now

 

 

Alright I have once again 4.7 back on my usb flash and booted.... all disks are GREEN in GUI.... I cant telnet into unraid server.... but I have no way of accessing the disks, I have been trying to find a command that will allow me to see the disks from telnet / console session but can not find it

 

I can not access 'TOWER' from windows, network error

 

What a mess, I am back on 4.7 after formatting the drive and loading my backup back onto the flash. Seems to be ok... I will pull a syslog and post it just to be sure... what a day :-(

2013-5.0-syslog2.txt

Maybe no point in trying to diagnose this syslog since you said you have gone back to 4.7, but there are a lot of read errors on several disks at the end. Probably some sort of cable or controller problem to affect so many disks.

 

If you think it is OK now in 4.7 and you can telnet and access the webGUI but not access any shares from Windows then it sounds like you just need to reconfigure your shares and maybe SMB.

 

If you want to try to look at your disks from telnet the simplest thing is to run mc from the command line and then browse to /mnt where you should be able to see your disks and any shares.

 

I haven't used 4.7 for a while so don't know how to tell you to proceed with getting SMB sharing going again but I think you should be able to use the webGUI to check if SMB is enabled and to allow sharing of your disks.

 

 

Awesome appreciate that. Yah it seems since I have gone back to 4.7 (formatted my usb/made bootable/copied my old backup back on) I seem not to be losing connection when writing to the server. As well there has been no faults that I can see within the few hours thus far.

 

I am going to keep testing over the weeks to come.

 

is this only necessary from console/telnet --> http://lime-technology.com/wiki/index.php/Powerdown_script

 

Performing a clean shutdown the server from GUI also have the same affect as that script?

Based on your v5 syslog (the only one I can see), you may have motherboard issues.  A parity check was started after the previous bad shutdown, but after about an hour and a half, the onboard bridge chipset failed.  This chipset controlled the 6 onboard SATA ports.  All 6 attached drives lost all contact, at the same time.  (Well technically, the 6th port hung on for a bit, and was the only one that established briefly a SATA link, but the link did not work correctly, as the attached drive could not be identified.)  So rather quickly, the system disabled all 6 drives, and you can completely ignore all subsequent errors, including all of the disk read errors.  I don't see any indication of any actual issues with the drives themselves, so you should not worry about your data, just needs access restored to them.

 

The only causes I can think of, are either a serious power issue at that time (eg. bad power spike), or an overheated northbridge/southbridge chipset (check for failed bridge fan on motherboard), or a faulty motherboard (which can only be fixed by replacing the board).  At this time, I cannot think of any way that moving to v5 could have caused this, but perhaps others will have ideas...

Awesome appreciate that. Yah it seems since I have gone back to 4.7 (formatted my usb/made bootable/copied my old backup back on) I seem not to be losing connection when writing to the server. As well there has been no faults that I can see within the few hours thus far.

 

I am going to keep testing over the weeks to come.

 

is this only necessary from console/telnet --> http://lime-technology.com/wiki/index.php/Powerdown_script

 

Performing a clean shutdown the server from GUI also have the same affect as that script?

 

Both the powerdown script and the GUI perform clean shutdowns. Make sure that you MB BIOS is the latest.