Installing first time firmware version 11

[JORDAORP]

I tried once more.

I started with this command: fdisk -b 512 /dev/sdb (to try to force 512 k sector and don't 4096).

And I created all partitions with the parameters of tutorial

But watch the message that appears.


Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 243201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes


Device Boot Start End Blocks Id System
/dev/sdb1 1 64 513056 83 Linux
/dev/sdb2 65 128 514080 83 Linux
/dev/sdb3 129 192 514080 82 Linux swap / Solaris
/dev/sdb4 193 243201 1951969792+ 5 Extended
/dev/sdb5 193 292 802226 83 Linux
/dev/sdb6 293 293 7008+ 83 Linux
Partition 6 does not start on physical sector boundary.
/dev/sdb7 294 357 513056 83 Linux
Partition 7 does not start on physical sector boundary.
/dev/sdb8 358 243201 1950643406 83 Linux
Partition 8 does not start on physical sector boundary.



After save the code above I went to fdisk to see the partition table.
That's the result:
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 30400 cylinders, total 488378646 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0000000

Device Boot Start End Blocks Id System
/dev/sdb1 2048 1028159 4104448 83 Linux
/dev/sdb2 1028160 2056319 4112640 83 Linux
/dev/sdb3 2056320 3084479 4112640 82 Linux swap / Solaris
/dev/sdb4 3084480 3907024064 2730856452 5 Extended
/dev/sdb5 3084736 4690979 6424976 83 Linux
/dev/sdb6 4691236 4707044 63236 83 Linux
/dev/sdb7 4707301 5735204 4111616 83 Linux
/dev/sdb8 5735461 488375999 1930562156 83 Linux


What do I do ? Buy another disk? :crazy
Thanks.

[fvdw]

...mmm I would not give up this disk yet

the problems seems to be that you have a disk where logical and physical sector size has been set at 4096 Bytes
Telling fdisk to use logical size of 512 Bytes seems not be able to solve

Thequestion is where did you loose the 512 bytes logical sector size, did you reformat the drive with Gparted or any other program ?

You need to get the setting back that logical block size is 512 Bytes (physical size may remain 4096 Bytes, maybe Gparted can do this.
Then you can use the partition table based on 512 bytes sectors.
The problem that some partition boundaries are not aligned then with physical sector limit can be solved by using the adapted partition table as I also use on my disk (see few post earlier)

Another thing you could try is to accept logical sector size to 4096 bytes and use following partition table
PS I don't know if the bootloader will be able to read disks with 4096 logical block size, but you do not have much to loose I can try and see what happens.

Code: Select all

partition  start      end
          cylinder  cylinder
sdb1       1            8
sdb2       9            16
sdb3       17          24
sdb4       25          30400  (extended part)
sdb5       25          36
sdb6      36          36
sdb7      37          44
sdb8     45         30400


as now sectors have size of 4096 Bytes one cylinder will be 8 times bigger then with 512 bytes so in principle all start and end cylinder numbers are divided by 8 as well as size of partition in cylinders (64->8)
Consequently total number of cylinders mentioned by fdisk should then be 30400, this matches with what is mentioned in your output

Remark your partition table is listed in sectors instead of cylinders. Thats not a real problem but there is one thing wrong
The end sector of partition 4 is far too big (its the one for a 512 bytes sector disk)
sdb4 end sector is specified as 3907024064 while there are only 488378646 sectors available (of 4096 bytes)
It also mentions 2730856452 blocks, knowing block size is 1024 bytes this means a size of 2,7 TB ! Thats bigger then actual size and not addressable by ms-dos partition table and this might be the reason why the nwsp2 can not read it.
The end sector of partition 8 the last one on the extended partition is correct (smaller then the max number)

Code: Select all

That's the result:
Disk /dev/sdb: 2000.4 GB, 2000398934016 bytes
255 heads, 63 sectors/track, 30400 cylinders, total 488378646 sectors
Units = sectors of 1 * 4096 = 4096 bytes
Sector size (logical/physical): 4096 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes

....

Code: Select all

dev/sdb4 3084480 3907024064 2730856452 5 Extended
....
/dev/sdb8 5735461 488375999 1930562156 83 Linux

So this partition table is invalid and might be the reason why the nwsp2 boot loader can not read it.

When using the one I proposed based on cylinders and assuming sectors of 4096 bytes then at least the problem of too many sectors on extended partition will be solved and maybe the nwsp2 can read it again.

[fvdw]

another user had a also a disk reporting logical/physical sector size of 4096/4096
see here viewtopic.php?f=11&t=666

unfortunate he never came back to report if the problem was solved

Also her some info on advanced format disk https://wiki.archlinux.org/index.php/Advanced_Format
the seagate you have should report 512/4096 (logical/physical sector size)

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

So without getting logical sector size back to 512 bytes I am afraid this disk will remain unusable

[JORDAORP]

Hi fvdw.

But the nwsp2 of the others user is the lite one, not the classic.
And yes, I should report 512/4096 but it seems isn't possible to do that (disabled smartalign).

another user had a also a disk reporting logical/physical sector size of 4096/4096
see here viewtopic.php?f=11&t=666

unfortunate he never came back to report if the problem was solved

Also her some info on advanced format disk https://wiki.archlinux.org/index.php/Advanced_Format
the seagate you have should report 512/4096 (logical/physical sector size)

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

So without getting logical sector size back to 512 bytes I am afraid this disk will remain unusable

[fvdw]

you could try to contact seagate :whistle maybe they have some software to restore it

[JORDAORP]

Hi fvdw.

As I posted before, I installed your firmware at a 100 gb disk (512 bytes) few days ago. I connected this HDD at nwsp2 and the bootloader worked fine, I browse to the web interface of firmware and turned off the device.
Well, today I turn it on again, started fine, I copy some files, and a few minutes later, the nwsp2 stucks again (with the 100 gb HDD).

About the original 2TB Seagate Barracuda Green (ST2000DL001), I couldn't boot, at nwsp2, with the disk of 4096 sector size.
But the disk is working fine. I create partitions to this Seagate HDD and copy a lot of data (to test) and it's OK.

So I have some conclusions:
1) Didn't work to install (in a Classic model of nwsp2) your firmware with a disk of 4096 sector size (both logical and physical). This Seagate HDD is working fine (probably I'll buy a external case to connect it). So the problem isn't this disk.
2) My problem is the nwsp2 itself, because my other disk (100 gb) didn't work either after few minutes. Happened the same problem of seagate.
I think it's overheating, and have some bug at the 'motherboard' of nwsp2.
So..... There's nothing to do about it.

Thanks a lot for your help. :thumbup :thumbup
JORDAORP

[fvdw]

Probably you are right, something is wrong with the MB if the 100GB disk also fails

ps I use my nwsp2 on its "side" wall instead of the normal way, allowing the heat the escape and avoid overheating, till now no probelems en they run for more then year now. The disk temperature never exceeded 50 oC (our firmware has a disk temp monitor that will shutt it down if it gets above 50 or 55 oC)

[favroom]

[quote=The disk temperature never exceeded 50 oC (our firmware has a disk temp monitor that will shutt it down if it gets above 50 or 55 oC)[/quote]

I am having trouble running the NWSP2 these days. Probably because of the heat.
I have read 55 and 58 degrees centigrade...

I don't use the auto shutdown feature of the firmware...

How can I debug the system to see if actually the heat is the problem here?

Ferdinand

[fvdw]

How can I debug the system to see if actually the heat is the problem here?

the firmware can only read the HDD (hard disk) temperature, the mainboard has no other temp sensors

However the cpu is located under the HDD and nif the HDD is 58 oC the CPU will probably be hotter.

I use the nwsp2 on it side wall and not on its normal feet that helps to keep CPU cooler.
You can also take of the black cover to release heat from the harddisk

Some people lost the nwsp2 (or HDD) because of overheating thats why we included the temperature guard

It would have been better if Lacie would have build in a fan...certainly during hot summer days

[favroom]

I use the nwsp2 on it side wall and not on its normal feet that helps to keep CPU cooler.
You can also take of the black cover to release heat from the harddisk

I have put it on it's side now too. What logs should I check to see what happened?

Ferdinand