How to install Transmission on Network Space 2

[fvdw]

Our firmware works and no doubt.

You seem to have an advanced formatted HDD that needs a different partition table.
There are posts on the forum about this topic and how to it can be solved.
(search for: advanced format)

I don't have time right now to look in detaill and search this info for you, maybe this evening

[fvdw]

it seems you have a fully advanced format HDD that does not emulate a conventional HDD with logical sector sizes of 512 bytes. That could mean that the kernel in the first time install package won't run.
Also you should use different block numbers for the partition table as now they are rather big although that is in principle not a problem only a waste of space that we won't use. In principe all numbers we must divide everything by 8 For example sda1 is now in your case 4 GB while we only need 512 MB

The partition table in your case should look like this

Code: Select all

Device Start End
/dev/sdd1 1 8
/dev/sdd2 9 16
/dev/sdd3 17 24
/dev/sdd4 25 30400
/dev/sdd5 25 36
/dev/sdd6 37 37
/dev/sdd7 38 45
/dev/sdd8 46 30400

I have sent you a pm (check your inbox) with a trial kernel with support of efi partitions. Now with this partition table an this trial kernel you have a change that it will boot.
Write this new kernel to sdb6 as described in the first time install package instead of the kernel as present in the original first time install package. (dd if=/path-to-new-kernel/new-kernel-name of=/dev/sdb6) assuming sdb is the disk you are preparing

If not you could consider to buy a not advanced formatted HDD or an advanced format disk that emulates 512 bytes sectors. But I expect it will not be necessaru

[Berny]

Thanks I got your message and the kernel. Just sent you a PM.

[fvdw]

H berny

some additional info

the a post from a user Matzi (viewtopic.php?f=4&t=581) proves it should be possible
he had the same problem. (His disk was an advanced format 2 TB disk BUT in his output uyou could see that this disk had a logical sector size of 512 and physical sector size of 4096 byte, your mentions 4096 for both.)
He also posted there a partition table that can be used when using fdisk to partition it but as your disk doesn't has logical sector size of 512 bytes this might not be right for you. The bootloader recognized both

Below a copy of his post to prepare a GPT disk that did run firmware

Thanks for the kernel - Good news!

I can confirm this kernel is running on a gpt partitioned disk. At least on a 2.0TB WD HDD, most likely it will work on bigger HDDs as well. But there are two things left. The externel USB HDD (GPT partitioned as well) is still not recognized. Maybe you know another trick ?

For partititoning I did the following with gparted:

sda1 504MB
sda2 503MB
sda3 503MB
sda4 1MB
sda5 784MB
sda6 8MB
sda7 503 MB
sda8 the rest

These sizes are taken from gparted on the prior installation.

Now, is there something to optimize? What are the required sizes? What about partition 4 which is not necessary now because there is no extended partition in gpt and part 4 was just providing the frame for part 5-8. I just set up a minimum partition 4 to provide the ususal parttion numbers.

[Berny]

Hi,

Thanks for that info. I actually found that thread and tried it a few times but it didn't work. In my case, in opposite to Matzi's case and Mamboman's cases both the logical and physical sectors are 4096. Matzi has mix cases and Mamboman has both 512. I tried what Mamboman did but still got red led blinking with the steady blue led. As you suggested I removed the disk from the case and turned on the NS2. It blinked the same way as with disk in it. That means the disk is not recognized at all and Matzi and Mamboman procedure didn't work with my advanced format disk.

Here is again the output of the fdisk:

Disk /dev/sdc: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 30400 cylinders
Units = cylinders of 16065 * 4096 = 65802240 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x00000000

Device Boot Start End Blocks Id System
/dev/sdc1 1 243202 2743214780 ee GPT

I worked on this for a week and now gave a break. Thanks for your support!

[Jocko]

Hi berny,

Could you tell us what is your disk ? (manufacter and reference)

[Berny]

Hi jocko,

It is a Seagate Barracuda Green 2TB.

[Jocko]

Hi berny,

At least, I understood now why your disk doesn't emulate 512kb logical sectors!

Seagate uses its SmartAlign technology with this disk, look at :
http://www.seagate.com/internal-hard-drives/desktop-hard-drives/barracuda-green/features/

So your fdisk output is normal : Sector size (logical/physical): 4096 bytes / 4096 bytes.

But, I don't see why your partition table is wrong... :dontknow

[fvdw]

reading the information smartAlign
"What is SmartAlign™ technology?
Seagate® SmartAlign technology is hard drive firmware that manages read-modify-write conditions resulting from partition misalignment conditions which are associated with the use of 4K sector drives, known as Advanced Format. SmartAlign technology does not realign hard drive partitions; it manages read-modify-write conditions dynamically inside the drive without host computer intervention or knowledge.
Without SmartAlign technology, read-modify-write conditions negatively impact hard drive performance. Seagate testing has demonstrated that SmartAlign technology’s functionality maintains consistent performance in our Advanced Format hard drives for the large majority of desktop workloads. The result for customers using SmartAlign technology is a hard drive that behaves just as legacy 512-byte sector hard drives without the use of additional software utilities."

This means that fidisk should see the disk as a disk with 512 bytes sectors.
I have a barracuda green 2TB and check it, it reports sectors of 512 bytes (I use it in a nwsp2 classic)

You must have done something that has disabled the smartAlign technology
I do not know any disk with physical and logical sector size of 4096 bytes. I even think that a lot of software will not work on such a disk

[fvdw]

see this page for more info
https://wiki.archlinux.org/index.php/Advanced_Format