Jocko wrote:Sorry minibike12, but it will take more than 5 minutes to do this ;)
I know, was just wondering if it was possible to do in a future firmware, for example.
fvdw wrote:mmm... well its strange, it should spin down, something must keep it busy. But I do not believe its the loop device. More likely something in your network. Disconnect the network cable if it then spin downs it is something in your network.
Or the daemon is not running.
Type on the command line
- Code: Select all
ps -ef | grep noflushd
It should give one line output showing that the daemon is running.
This is the output, i assume it is running.
- Code: Select all
root@fvdwsl-base:/ # ps -ef | grep noflushd
root 724 1 0 Dec26 ? 00:00:11 /usr/sbin/noflushd -n 5 /dev/sda
root 18416 18306 0 09:51 ttyp0 00:00:00 grep noflushd
root@fvdwsl-base:/ #
fvdw wrote:50 oC is rather hot. (There is a temparature guard in our firmware to switch it down when it got above 50 or 55 oC)
ps I use my nwsp2 on its side wall instead of the normal feets . That keeps temps at least 5 to 10 oC lower
Indeed, but this is with the black cap off.
So just the base and bare hdd.
I think this is because it is always running at full speed.
The standard 1TB hdd used to be around 65oC i think, especially in summer.
fvdw wrote:everything is possible but we can not exceed 2,2 TB with a ms-dos partition table that is required by the boot loader.
Making then two partitions doesn't make sense.
As said I would make just sda8 occupying 2 TB, use for partition 8 this setting (cylinders).
- Code: Select all
Partition 8 start 409 end 243200
(I just have written a file of 50 GB to the nwsp2 with an average speed of 20 MB/s)
Ah okey, i though that the problem was that the partitions couldn't be bigger than 2TB.
But if it is the partition table, it would be useless indeed.
NTFS is not an option i guess?
When formatted correctly, NTFS can hold more than 2.2TB
fvdw wrote:I have a kernel that should be able to write to the flash memory, and I have an new compiled u-boot image (based on Lacie source code) that can be written to it and that would enable GPT support. Still waiting for someone to try it.
Hmm okey.
I will look into JTAG after new years eve.
When i've found a save way to flash the nwsp2 when bricked, i would like to try it.
Mijzelf wrote:When advanced format disks were new (and didn't exceed the 2TiB barrier yet) I read about an 'auto alignment' feature. On an Windows machine the first (and in most cases only) partition starts at the first cylinder (cylinder counting start at zero, for some unknown reason), which is in most cases on sector 61 or 63 (can't remember which). This is not a multiple of 8, so an ad disk in a Windows machine would be unaligned by default. This was solved by letting the first virtual sector start on an offset of the first physical sector.
I cannot remember how this behavior was triggered, I think a jumper. But maybe also by decoding sector 0 being written. First partition on cylinder 1 => offset.
It doesn't make sense that this would be in effect on a >2TiB disk, as it won't have an MBR partition table anyway, but who knows?
So you could do some speed measurements with different offsets. When I read well, the +1 option was already shot, so then remains the +512, +1024, +1536, ... ,+3584.
There is no need to format a loop device for each offset, the speedtest can be done on a lower level. You dd doesn't have speed feedback, but does the 'time' option work? Try a 'time dir' or something like that.
If 'time' works, you can do
- Code: Select all
losetup -o 3686809600 /dev/loop1 /dev/sda
time dd if=/dev/zero of=/dev/loop1 bs=4096 count=262144
losetup -d /dev/loop1
losetup -o 3686810112 /dev/loop1 /dev/sda
time dd if=/dev/zero of=/dev/loop1 bs=4096 count=262144
losetup -d /dev/loop1
....
And further with offsets 3686810624, 3686811136, 3686811648, 3686812160, 3686812672, 3686813184. This writes 1GiB low-level to the loopdevice. If 'time' doesn't work, you can do
- Code: Select all
date; dd if=/dev/zero of=/dev/loop1 bs=4096 count=262144; date
and do the math yourself.
BTW, this will destroy the current filesystem on the loop device.
Thanks for the info!
I will test different offsets today.
Will let you know if there is a change in performance.
Btw, web interface is a bit buggy after using dd if=/dev/zero .......
Hurray, i now have a 16TB hdd, hehe :hammerhead
- Code: Select all
Share Name Volume Total Size Free Size
public Default 16325.23 GB 2747.09 GB
openshare Default 16325.23 GB 2747.09 GB