nwsp2 classic gpt support

[minibike12]

I am already busy with rebuilding the /loop1 partitions with the new offset.
So can't test it anymore, sorry.

I am using Waterfox x64 btw.

[Jocko]

So as waterfox is a variant of Firefox, it's normal that you have never had a problem with win8 ;) (issues only with IE and Chrome)

[minibike12]

Hmm i've tried to executed this:
losetup and mke2fs -j /dev/loop1 worked without problems
But mkdir /share/1000 already exists.
And i can't mount /dev/sda /share/1000

Code: Select all

losetup -o 3686809601 /dev/loop1 /dev/sda
mke2fs -j /dev/loop1
mkdir /share/1000
chmod 777 /share/1000
mount /dev/sda /share/1000
umount /share/1000
reboot (with web interface).

losetup -o 3686809601 /dev/loop1 /dev/sda
mount /dev/sda /share/1000


And when i try to mount it, it says
"mount: /dev/sda already mounted or /share/1000 busy"
But /dev/sda is not mounted

Code: Select all

root@fvdwsl-base:/ # mount /dev/sda /share/1000
mount: /dev/sda already mounted or /share/1000 busy
root@fvdwsl-base:/ # 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/root on /lacie-boot type ext3 (rw,relatime,errors=continue,barrier=0,data=ordered)


[fvdw]

you must mount /dev/loop1 :whistle

mount /dev/loop1 /share/1000

:twak

[minibike12]

Hehe, stupid.
Works now.
I will test speed tonight.
Got to go to work.

Thanks and see you tonight.

Only problem is that i still can't access the folder public.
It now says i have no right.
/share/1000 is chmodded with 777
I deleted all folders and made a new one with the web interface

[fvdw]

ok

I did a test with disk image file mounted using a loop device, it goes to about 25 MB/s and then drops again, goes up again, drops again, so average speed is around 8 MB/s. Reading is ok (22 MB/s). So this suffers also from a lower writing speed, this could also be misalignment as the disk image is created somewhere in sda8. But i it could also be a limitation of the loop device driver.

Maybe you should consider to follow my other suggestion. making a 2 TB partition sda8 and add later the remaining space with a loop device. At least you will have a higher writing speed on the 2 TB. Disadvantage will be that the extra space will be added as one shared folder until we are able to define a second volume in the firmware. If the loop device driver is limiting the speed then this reaming space will have the low writing speed. But maybe Mijzelf has some good ideas.

[minibike12]

Thanks for testing.
I think it is going to be hard to figure out if it is a misalignment or that it is an limitation of the loop device driver.

Making a 2TB partition on sda8 and place other 600GB on /dev/loop1 might be a good idea.
Can this be done on the same way as now (with an other offset that is), or do we need to do this on a other way.

I've also noticed that i now have 2.60TB free of the 2.72TB.
This means that 120GB is already in use by the other partitions.
Isn't this a bit much?

And indeed, maybe Mijzelf has a good idea left.

Oh, and my drive is not going in standby.
Maybe an other problem of the loop device?

[fvdw]

It will done a same way, only you will create a as extra an sda8 partition of 2 TB , just as you would on a 2 TB disk.
As offset for the loop device then we will need to use the first byte after the end of sda8.

The fact that so much space is already used is because you didn't use the -m option when formating the space (mke2fs command). See one of my previous post. As a result 5% of the total space will be reserved for superuser. You can reduce this space for instance by using -m 1 that will limit it 1% (See also the original how to guide there this -m option is used)

But let see what the speed is now with the new offset, although I am not optimistic, I did some reading on the internet and i think Mijzelf was right with the offset to use a mutiple of 4096.

[minibike12]

Current speed is around 7mb/s.
So, not much.

I forgot that indeed.
Will use -m 1 next time, thanks.

My drive is not going in standby.
Tried different timings.
Does this have to do with the loop device driver.
Maybe it is always busy with that...

[fvdw]

it seems even worse. That means the original offset was probably correct. Most likely it the loop device driver causing it.

Why it doesn't go to standby can be many reasons. Certainly if you access it via ssh and explorer or have a media server running that is indexing files. It will go it standby if no read or write request for the disk are made. There is a daemon running that cache some data to reduce spin ups. On my nwsp2 it works fine, but it not always spins down after 15 minutes (that the time I have set), sometimes it takes 30 minutes.