nwsp2 classic gpt support

[fvdw]

Sorry guys but I just returned from Christmas party
--edit
The fact that you could not use /tmp as mountpoint is strange, /tmp is a symlink to /rw_fs/tmp and that directoy is world r/w should you should be able to create a folder there to be used as mountpoint :scratch.

Using the command reboot is not enough. A bit must be set in an eeprom to set proper shutdown/reboot method.
Use the the restart or shutdown buttons in the web interface of fvdw-sl firmware that should solve this problem as they set the eeprom correctly.

To reset it pull the power plug and press power button several times to drain all power. Wait a few minutes and then put power plug in and press the power button if it doesn't boot by itself. When you have once shut it down with fvdw-sl webinterface buttons then it should boot automatically when restoring power.

[minibike12]

No problem :).

Ok.
What should i use then to mount?
Instead of :

Code: Select all

mkdir /tmp/mountpoint
mount /dev/loop0 /tmp/mountpoint


Btw, Merry Christmas you guys, and thanks for the help so far.

Edit:
Pulled the power for 25 minutes.
Still not booting...
Powerbutton does not react either when turned on.

[fvdw]

No problem :).

Ok.
What should i use then to mount?
Instead of :

Code: Select all

mkdir /tmp/mountpoint
mount /dev/loop0 /tmp/mountpoint


Btw, Merry Christmas you guys, and thanks for the help so far.

Edit:
Pulled the power for 25 minutes.
Still not booting...

Not booting :scratch what does the blue led do when connecting power. if it is steady on press the power button on the back and hold it for 2 seconds and release it.

Regarding the mountpoint. Try to create the directory mointpoint in the root of the file system
mkdir /mountpoint and try to mount it on that folder.

As said /tmp is a symlink to /rw_fs/tmp and sda5 is mounted in /rw_fs apparently sda5 is mounted readonly which should not happen but thats for later. First need to get it booting again

[fvdw]

this is the "normal" output of mount on a running fvdw-sl system
Of course you won't have sda8 mount. probably also not sda1 as you did a first install. sda1 and sda2 are only used when installing a new firmware
Also /dev/loop0 might not yet be there as you did not create a disk image yet.
As you can see sda5 mounted on /rw_fs is mounted r/w

Code: Select all

/$ mount
rootfs on / type rootfs (rw)
/dev/root on / type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda1 on / type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
none on /proc type proc (rw,relatime)
none on /sys type sysfs (rw,relatime)
/dev/sda5 on /rw_fs type ext3 (rw,noatime,errors=continue,barrier=0,data=ordered)
tmpfs on /rw_fs/tmp/usr/var type tmpfs (rw,relatime,size=5000k)
/dev/sda8 on /share/1000 type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
/dev/loop0 on /share/1000/disk-images/image-1 type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp850,iocharset=utf8,shortname=mixed,errors=remount-ro)
/dev/root on /lacie-boot type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)
/dev/sda5 on /rw_fs type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)

[minibike12]

Not booting :scratch what does the blue led do when connecting power. if it is steady on press the power button on the back and hold it for 2 seconds and release it.

Regarding the mountpoint. Try to create the directory mointpoint in the root of the file system
mkdir /mountpoint and try to mount it on that folder.

As said /tmp is a symlink to /rw_fs/tmp and sda5 is mounted in /rw_fs apparently sda5 is mounted readonly which should not happen but thats for later. First need to get it booting again

Blue led flashed 2 times short but quick, then goes off again.
When i push the power button short, it does this again.
Holding the power button for 2 seconds starts the nwsp2, and the drive is spinning up.
But after this, solid blue led, no appearance in router, and power button dies.
No way to turn it off or to set it in standby

this is the "normal" output of mount on a running fvdw-sl system
Of course you won't have sda8 mount. probably also not sda1 as you did a first install. sda1 and sda2 are only used when installing a new firmware
Also /dev/loop0 might not yet be there as you did not create a disk image yet.
As you can see sda5 mounted on /rw_fs is mounted r/w

I did make sda1 and sda2 as shown in the guide?
And i did use /dev/loop1 with your recommendation.

[fvdw]

describe what the blue led does when connecting the power

[minibike12]

I did in previous post ;)\

Btw, i used the partition table as shown in this post :
Click
I used the guide of this page :
Click
Used the howto-fvdw-on-lacie nwsp2-5jan2012.zip pdf.

[fvdw]

the good news is the red led is not coming on, so it recognized a disk.
probably again a problem with the partition structure.
The blue led should flicker fast when HDD is spinning up and then start to blink with disk activity when loading the kernel and the rest of the firmware.
Seems it is not loading the kernel or the firmware. You need to check the partitions. if it can not read sda5 where the nas database is then the boot process will stop. maybe you trick with the mountpoint corrupted sda5. Also the fact that it was readonly mounted indicates an issue with sda5. So try to restore sda5

[minibike12]

Restore sda5 only will do the trick.
Or do i have to rebuild whole structure?

There was one problem with partition 4 though.
I described it here in case you missed it.
Is this an important error?
http://www.plugout.net/viewtopic.php?f=11&t=1061&start=40#p6439

[fvdw]

did make sda1 and sda2 as shown in the guide?
And i did use /dev/loop1 with your recommendation.

Thats ok you must do that. I meant that mounting sda1 or sda2 will only happen when you install a new firmware. So if you did only first install you won't see sda1 or sda2 being mounted. Only after first upgrade you will see one of them being mounted.
Its the way we use to be able to install a new firmware while another is still running.