nwsp2 classic gpt support

[fvdw]

Found something interesting.
Made the 3TB with mbr and partition 1 till 7 (i didn't make sda8) to flash uboot 4.
I can still access the folder "public"? (\\ipadress\public)
When i put a file there, uboot 4 for example, ssh into the drive, and use "ls /share/1000/public", it shows the uboot 4 file.
How can i use the folder when i didn't make sda8 and the folder?

when sda8 is not mounted the firmware will create in /share a folder with name 1000 and in that one a subfolder with name public.
So they are created in the system partition. Which is not too big (250 MB) so don't store big files there for the moment.

About the "freeze" you were talking about. When it is running the Linux kernel is in control and u-boot doesn't do anything, so I guess that the Lacie kernel/firmware caused the freeze. U-boot does only load the kernel in memory and gives control to it and only waits there for the next boot.
There is an eeprom present that influences the way it shutdown and powers up. That need to be reset properly at shutting down. If the Lacie firmware halted then you probably pulled the power plug and put in in again to reboot it. If this time is too short then it can happen what you describe, that it won't boot. Taking of power and pressing power button fa few times and wait a few minutes will restore the normal behavior.

[minibike12]

Ah ok.

I've installed the nas with GPT table and uboot 4.
Works like a charm with fvdw 11 uimage 59.
But i've ran the update to fvdw 14.
This installs uimage 57, now i can't access the disk anymore in explorer.

I'm going to manually install uimage 59 again, and look if i can retrieve access again.

[fvdw]

Ah ok.

I've installed the nas with GPT table and uboot 4.
Works like a charm with fvdw 11 uimage 59.
But i've ran the update to fvdw 14.
This installs uimage 57, now i can't access the disk anymore in explorer.

I'm going to manually install uimage 59 again, and look if i can retrieve access again.

It should also work with uimage 57.
all users run 57, the only difference with 59 is that with 59 you can write to flash and with 57 not.

Boot it again and check that you have set workgroup same as on the PC in your LAN

[minibike12]

Hmm i can access the root after reboot.
\\ipadress\
But not the public folder.
I've deleted the folder and made a new one.
Rebooting now.

Edit:
Succes, i have access :D
I am copying a 8GB file to the nwsp2.
Average of 18mb/s write.
And 27mb/s read.
What speeds do you get?

[fvdw]

I get similar speeds, sometimes a little higher write speed

[minibike12]

Okey.
1 more question.
Does your drive go in standby after a while?

[fvdw]

yes, but only if there are no activities requiring reading or writing data from disk

[minibike12]

Hmm, mine is going in standby, but spins up after about a minute.
This happens in a loop.
-Spinning few minutes
-Standby ~one minute
-Spinning few minues, etc

I am not using it, and the other don't know how to access it yet, so they aren't using it either.
Any way to find out what is causing the drive to spinup?

[fvdw]

why are you so concerned about spin down ? be happy that it is up and running and that you can use 3 TB
(When may I expect delivery of a disk ? :-D )

first test you could do is disconnect it from your LAN and be sure that no mediaserver is running on the NAS (especially twonky can take a long time to index the media files)
Furthermore the time for spindown can be set in the firmware, minimum is 5 minutes (default =15 minutes). I advise to use a value of at least 10 minutes.
Lot of spinning up and down might reduce life span. if your disk spins down in a time shorter then set in the firmware then it is the firmware of your harddisk doing it.

If it does spin down when disconnected from your LAN then something in your LAN is causing it

[minibike12]

Oh but i'm psyched that it works :hail . :bananadance
So many thanks, again.

I would be happy to sponsor you with a disk, but life of a student is pretty expensive unfortunately.
Anything else maybe?

Spin down is more for the others, energy savings blah blah blah. :twak :pound
Also, lots of spinup and spindown is indeed bad for the drive, so wanted to keep this to minimum.
Standby when nobody is using it, and only spinup when needed.

But if that doesn't work, too bad.
3TB of space is more important to me, hehe

Edit:
Tested it without LAN cable.
Spins down, spins up again almost instant :scratch