Still bricked… no help in sight so far.
First of all, I do not care about my data, I made backup before upgrade firmware.
After power cycle or reboot I see “Building RAID” and “Making filesystem” and have factory defaults setting on my SS.
I can login to SS by WEB as admin/admin and create RAID0 (but can not create RAID5). I can change password and allow access for root by ssh. But, after reboot I have factory default setting again and failed RAID (DataVolume RAID Type - Span)…
I have previous version microcode, but I have not any idea how I can downgrade it.
In the result of successfull firmware update to version 2.3.01 I got my ShareSpace bricked. Fortunately I’ve made a backup of boot partition and I’m going to downgrade…
AKazak,
How can I downgrade microcode?
I have old firmware but I have not any way to downgrade it… I could not downgrade manually also due to I received error : You have latest version!!!
-defender- wrote:
AKazak,
How can I downgrade microcode?
Prior to upgrade I connected all 4 HDDs to my Linux box and made a backup image of md0 (boot partition). Now I will connect 4 HDDs to my Linux box again and restore md0 from the image.
Cool! I made data backup only…
The update went fine. I then prcceeded to transfer 1.5TB of data (3000+ files) and while it started out fast, it has slowed down to a crawl : 940KB per second. I want to cry.
Anyone in the same situation ?
Adi
Would you be so kind and upload that md0 image somewhere - we have another bricked SS here - after 2.3.01 upgrade. older fw version (laying on your md0) would be a great help … we dont’ care about the data, all we need is a working fw image… thanks
citronik wrote:
Would you be so kind and upload that md0 image somewhere - we have another bricked SS here - after 2.3.01 upgrade. older fw version (laying on your md0) would be a great help … we dont’ care about the data, all we need is a working fw image… thanks
IMHO, some of us have default setting after 2.3.01 upgrade. Maybe, SS has default IP-adress too.
So, Can you try to connect by WEB GUI to the SS (use default IP-adress for just in case)? If you can see the similar of: RAID rebuilding or making filesystem, you have to waiting for it will be done and try to configure SS as first time…
I just restored md0 from backup and realized the possible reason of firmware update failure: not enough free space at md0 before update. Before updating, everybody please ensure that you have at least 70% free at md0!
Useful Linux commands:
- df — to see disk usage
- du — to see folders’ size
OK
1. answer to -defender-
- after fw update to 2.3.01 I was unable to connect to box, so I hit the rear reset button - reset (“IP + name + basic settings restore” went through -I can find the box on new IP (wd discovery shows that new ip is assignet to box by dhcp), but the problem is that the box does not start http or ssh services on this new ip, so is not accessible.
- kind request to AKazak
- can you upload your previous md0 somewhere (I was not smart enough to save it before upgrade…).
I took disks out and attached it on other linux box, so I have “offline access” to broken sw, that’s why I would really appreciate a lot having your working md0 (with previous fw version). btw : du -hs on my mounted md0 (the broken one) shows 183MB occupied, so I believe problem of not starting services, wasn’t enough free space.
I am going now to try to edit my md0 - touch /etc/.factory_restore, put it back to bricked box and let it boot, maybe this will help. I’ll keep you informed (if it will work, it will take about a day to finish) - but I warn you - don’t do this factory restore if you want your data (it will rearange raid and destroy all data). I don’t need my data - fortunatelly I backed them up before update.
But I think even factory_restore won’t help (I think new fw is just broken and will not go through factory restore) , that’s I would really like to have someones md0 backup - to be able to use it on my box. I don’t care about configuration - will reset it, I just need a working md0. Please, upload it somewhere (you ca reach me at citronik@yahoo.com if you dont’ like the idea of sharing it public).
thank you all.
WD - SHAME ON YOU - apparently you did not test the new fw correctly - a lot of users are having bricked products now - isn’t it time for you to respond!? It’s not about the data (data are still there on 4.th partitions of disks) - so a warning - backup you data before upgrade is not important. This is a SERIOUS PROBLEM of turning a device to useless piece of hardware!
Btw, on my broken box, there are this ports open( found by nmap):
21/tcp open ftp
111/tcp open rpcbind
548/tcp open afp
720/tcp open unknown
1025/tcp open NFS-or-IIS
2049/tcp open nfs
9000/tcp open cslistener
54034/tcp open unknown
So no http or ssh is running.
--------------------------------------------------------------------------------------------
--------------------------------------------------------------------------------------------
OK, I don’t wanna issue new post - to have everything better organized.
Currently = after modifying my broken md0 (raid build from 4x first (214MB) partitions of broken SS) with this: “touch /etc/.factory_restore” and putting back to box, I can connect to the box over http (btw only port 80 is open at this stage on the box, as nmap shows), its web page is announcing raid being rebuild, so finaly I have at least a bit “accessible box”. However - before definitelly issuing VICTORY signal I will wait for the unit to finish raid, than I’ll inform you about the status.
AKazak, please, post your md0, as I’m not sure how this all is going to finish (and I don’t trust this restore at all, even thought it seems to be doing something expectable now).
Currently = after modifying my broken md0 (raid build from 4x first (214MB) partitions of broken SS) with this: “touch /etc/.factory_restore” and putting back to box, I can connect to the box over http (btw only port 80 is open at this stage on the box, as nmap shows), its web page is announcing raid being rebuild, so finaly I have at least a bit “accessible box”. However - before definitelly issuing VICTORY signal I will wait for the unit to finish raid, than I’ll inform you about the status.
I have factory restored SS each time after reboot or power cycle…
Sorry, but I cannot post my an image of my md0 , because it contains:
-
serial number of my unit
-
hardware MAC adress of the network adapter
For the sake of purity of the experiment I strongly reccomend you to connect 4 drives to a Linux box, backup all data from NASRAID volume to somewhere, boot under Windows start Data LifeGuard Diagnostic for Windows and make this:
After quick erase of 4 HDD’s mark each drive with number from 1 to 4 and insert to ShareSpace according to the numbers. Power on ShareSpace and wait 30-40 hours before factory restore is completed. In the result you will get your own clean md0 volume and you can easily back it up.
aKazak - I undestand that you don’t like the idea of posting your md0 - it’s ok.
I don’t feel like deleting system partition by writing zeroes to it right now.
I just finished a little while ago my factory restore. The box is accessible ever http, however - I cannot get past this ERROR: “System is busy now! Please try it later.”, after issuing “finish” (right after init phase of new start). So - I’ll get back to it on tommorrow - maybe that would be enough time for my box to settle after the rebuild.
a Kazak - one more question - how big is this file on your box: md0:/proto/SxM_webui/admin/config.xml - I am a little suspicious that it’s somehow screwed on my box (it’s 68MB on my saved image of broken box -don’t know current size - as I said - I just had enough trouble with this product for today).
If it will still not be accessible on tomorow, I will take the disks out and again, will try to free some more space and edit starting scripts of it “especialy /etc/rcS”.
anybody - any other ideas?
thank you.
citronik wrote:
I don’t feel like deleting system partition by writing zeroes to it right now.
It’s up to you. I’ve already made Factory Default Restore (with prior data backup and Quick Erase of 4 HDDs) 4-5 times and every time I fresh system.
citronik wrote:
a Kazak - one more question - how big is this file on your box: md0:/proto/SxM_webui/admin/config.xml - I am a little suspicious that it’s somehow screwed on my box (it’s 68MB on my saved image of broken box -don’t know current size - as I said - I just had enough trouble with this product for today).
I’m affraid something went wrong with your system, because config.xml is just simple XLM file of size less than 10 KB. I will look and write you back.
citronik wrote:
If it will still not be accessible on tomorow, I will take the disks out and again, will try to free some more space and edit starting scripts of it “especialy /etc/rcS”.
anybody - any other ideas?
thank you.
I’ve already tried this path. However as you don’t see what is happening during boot, you will probably wrap you starting scripts (rcS is not the only strarting script) in error logging to md0. Also you will probably have to do quite a number of plug/unplug operations.
After such bad experience with WD ShareSpace I started looking for serial access option.
IMHO an interesting observation. Today my ShareSpace finished Factory Default Restore after “successful” firmware update. This is what I saw after first login:
I check for the firmware update by pushing well know button. The system informed me that there is a new version of firmware available. I downloaded and upgraded the system. In the result of really successful upgrade I saw the following:
Conclusion: after Factory Default Restore (with prior Quick Erase of 4 HDDs) one doesn’t have MioNet installed. But WD by unknow reason force users to have MioNet by implicit istallation during “firmware upgrade”.
So, is there going to be a fix for this? Something that us users that have lost http access (and are lucky enough to still have ssh access) can run from the terminal to update / fix the httpd daemon?
Same problem here. These are the symptoms:
-
autodownload of FW halted;
-
manual download of FW completed without error. Multiple downloads of FW gave same byte-size;
-
manual update of FW completed without interuption (no power off, no browser error);
-
after FW update Sharespace restarted, but not accesible anymore through http, nfs, afp, smb or bonjour;
-
disk-LED’s okay, also network-LED;
-
not visible in DHCP-register (although hardcoded based on MAC-address);
Created a ticket at WD-support on monday 9/19/2011. No response thusfar.
Remedial actions and results:
-
connected USB-drive to USB-port 1 and pressed for auto-backup (from NAS to USB). No result;
-
hardware reset (just IP, admin password, devicename);
-
NAS accesible again through http;
-
folders and userrights still in NAS database;
-
user-list empty. Does not accept entry of former user-credentials as the user is supposedly still present (although not visible in the user list);
-
RAID configuration broken: no volume information and disk spanning is selected, ready to be submitted (but that would really create more problems and make it harder to recover my data.
NOTE: my original configuration was 4TB in RAID5 with 1.8TB of data ( so 1.2 TB freespace still left).
Question: does anyone have any idea how to proceed? Is there a possibility of rebuilding my RAID5-config without losing my data? Is it possible to access the 4 individual HD’s with a disk-editor and retrieve my data? Any other options or ideas?
Many thanks for thinking along. Good luck to everyone who has this same problem.
One frustrated, dissapointed and angry Sharespace-user,
Jannem
hmmm - AppleFanboi - I wish I would have ssh… OK - if you really have access, get conected to terminal as root (!!! root password is something like welc0me!!!). Then check df -h (take a closer look on free space) As suspected by others - you should have enough of free space on the root partition ( / or md0 ). In my case is probably about 40MB free not enough. So first check this. If you want to start your http service - try issuing simple: “service httpd start”. If it fails - check logs (cat /var/log/messages). You can get inspiration ofwhat the box is doing, by readind init scripts (located here - /etc/init.d/ - especially importnant is this: cat /etc/init.d/rcS).
Let us know if “service httpd start” helped.
Some more observations for others:
Try to check, when your httpd is down,if you don’t have by a chance twonky accessible (just issue in browser http://ipofyourbox:9000). Perhaps you can free some space on your root partition by deleting twonky logs (in my case it was like 7 MB).
