plugout.net

Hello all,

I had some issues updating to v17.. but after reading multiple posts I figured it out and was able to update succesfully (according to the messages) to v17
after the reboot however, I can't reach it anymore?!
(it does not show up in my router, nor with advanced ip scanner)
the LED's seem to work normal, first some flashing then stable, then some more flashing then stable again.. for ever)

=> what can I do?!
(wanted to give this nas to a friend, since I have upgraded a few times .. went to synology...)

Best regards

The flashing you mention seems normal behavior. Did you try switch it off and boot again?

HI fvdw,

yes I did, I also did a 5 sec reset while powering up
I did the update last weekend, but initialy thought it was rebuilding a database and let it be ..
today I did the restart (unplug the power) 3x and last time also the rest button pressed for >5sec while booting

scanner can't reach him still..

:thinking

:dontknow currently scanning the complete network (192.168.0-254.0-254).. in the hope to find it in a different range than normal

after that I will: extract the drive and connect it to my computer
- check it for errors
- in worst case restart procedure to install a new drive..
:pound

:thinking finaly got to it to get the HD out of the casing and connect it to a virtual machine running linux...
all data can still be accessed = nice

I get following error for one partition:
"
Failed to moError mounting /dev/sdb5 at /media/demo/03f26d25-6dc9-4ba8-8051-7e3cb9828f19: Command-line `mount -t "ext3" -o "uhelper=udisks2,nodev,nosuid" "/dev/sdb5" "/media/demo/03f26d25-6dc9-4ba8-8051-7e3cb9828f19"' exited with non-zero exit status 32: mount: wrong fs type, bad option, bad superblock on /dev/sdb5,
missing codepage or helper program, or other error

In some cases useful info is found in syslog - try
dmesg | tail or so.unt "394 MB Volume".
"

would it be wise to follow the procedure for the sdb5 of the new HD instructions?.. or is there a better way to revive this HD?! :thinking

going to try the alternative procedure to setup sda5

You could try to run e2fsck on sda5 as the file system can gave a fault
When using e2fsck the partition should be not mounted

Code: Select all

e2fsck -y /dev/sda5

Ps. To mount sda5
Create a directory with name /sda5 and mount using default options

Code: Select all

mkdir /sda5
mount /dev/sda5 /sda5

If that works aldo the spd8020 should be able to mount it
sda5 contains the nas database and other settings. If you replace content all your settings will be lost.
So better first try to repair it with e2fsck

mm.. did not work.. or I did something wrong... (i'm a novoice in Linux.. so it's a big adventure again ...)
I will be removing everything from the HD.. (lukly I still have the original images.. so that should be oke, the content i have somewere else also ..)