plugout.net

Posted: **Sat Dec 28, 2013 11:23 pm**

I have problems creating the ext3 filesystem on partion 8 on big harddisks (3TByte).

This is the error message:

mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
182968320 inodes, 731841137 blocks
7318411 blocks (1.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=0
22335 block groups
32768 blocks per group, 32768 fragments per group
8192 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872, 71663616, 78675968,
102400000, 214990848, 512000000, 550731776, 644972544

Killed

There was an error formatting /dev/sda8.
Installer will exit.
Disk will boot but partition for shared folders will be not availailable
root@none:

I used the last version distributed for poor internet connections on a NWSP2
Any idea? Is mke2fs short of memory?

Posted: **Sun Dec 29, 2013 8:06 am**

which partition type did you chose ms-dos or GPT. Must be GPT for disks bigger then 2 TB

in vs 2 of the fvdw-sl console a separate binary is included that should be capable to format a disk bigger then 2 TB. (GPT partition table)
You can also try what happens if you use the command manually in the telnet client
mke2fs-64 -j -m 1 /dev/sda8 (assuming it is /dev/sda8 you want to format)

Posted: **Sun Dec 29, 2013 1:15 pm**

which partition type did you chose ms-dos or GPT. Must be GPT for disks bigger then 2 TB

I used the installer shell which comes with the fvdw-sl-console-version-5-2. I told it to format a blank disk bigger than 2 TB.

At least I booted the NWSP2 without a formated partition 8, and did the formating and the creation of the folder "public" with the fvdw firmware.

Code: Select all: mkfs.ext3 -j -m 1 /dev/sda8 mkdir /sda8 mount /dev/sda8 /sda8 mkdir /sda8/public chmod 777 /sda8/public umount /sda8 reboot -f

You can also try what happens if you use the command manually in the telnet client
mke2fs-64 -j -m 1 /dev/sda8 (assuming it is /dev/sda8 you want to format)

The installer script uses mke2fs-ext3 and not mke2fs-64.?
I used this command manually in the telnet client

Code: Select all: mkfs.ext3 -j -m 1 /dev/sda8

which works with smaller partitions (1024GB) but not with bigger ones (2.7TB).

PS: what is the difference of mke2fs-ext3 used with the fvdw-sl-console-version-5-2 and mkfs.ext3 (mke2fs) supplied with the firmware?

Posted: **Sun Dec 29, 2013 2:16 pm**

mke2fs-ext3 and not mke2fs-64 are the same binaries, they are static compiled against ulibc
It could be that ulibc has a problem with bigger disks
YUsing static compiled binaries is necessary because the standalone kernel doen't contain any libraries (like libc) adding those will make it too big.

The mkfs.ext3 in the firmware is a sym link to mke2fs which dynamically compiled against libc.

plugout.net

fvdw-sl-installer formatting problem

fvdw-sl-installer formatting problem

Re: fvdw-sl-console for ms windows install without removing

Re: fvdw-sl-installer formatting problem

Re: fvdw-sl-installer formatting problem