plugout.net

Using latest console, using standalone kerner (kirkwood), script runs through until

mke2fs 1.41.14 (22-Dec-2010)
/dev/sda8: Memory allocation failed while setting up superblock

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

What can I do next to get a formatted disc ?

What I did so far:

- Updated to 18.2.
- reset internal disks in NAS using the firmware "(re-)Start the setup task : Reset internal disk(s)"

It takes quiet a long time (1h) ..... :roll: ... but it worked.

Remarks:

looking from behind the 2big network 2: Drive A (sda) is on RIGHT side, drive b (sdb) on LEFT side. This is different from the installation guide.
I doublechecked the SATA cable between pcb and drived. Right and left drive are indicated (written)

The firmware installation works on both sides no matter in which slot you put the drive.

The 2big2 owns a lba64 bit bootloader so it's capable to work with drives >2TB. I use a 8TB WD 3,5".

The fan can be tested plugged off. During the formatting and testing the drive was at 42°C.
For the warm ICs on the board I took care with raspberry pu heatsinks (3€ set).

The firmware installation works on both sides no matter in which slot you put the drive.

Yes, but...when booting the disk with firmware it must be in most lefthand side slot seen from back. The kernel is patched and it expects to find firmware in scsi port connected to that slot

Hi fvdw,

no.
The disk works (boots) in both slots.
On the right slot it's indicated as (Disk A) Volume A, on the left as (Disk A) Volume B.

I've not added a second disk yet but I will try.

wd9895 wrote:Hi fvdw,

no.
The disk works (boots) in both slots.
On the right slot it's indicated as (Disk A) Volume A, on the left as (Disk A) Volume B.

I've not added a second disk yet but I will try.

Yes but it will fails when a second disk is added and also when firmware is loaded from sda1 or sda2. On a first install it will boot from partition 7 as the bootloader sees it as sda7 but the kernel sees the disk as sdb. Upgrade firmware will fail using the disk in righthand side slot

Upgrade firmware will fail using the disk in righthand side slot

I did it yesterday. It worked flawlessly. In the right slot.
Don't get me wrong, I only tell you what I observed.

Hi wd9895

Anyhow if you keep the disk with the firmware in the right slot, you will erase the firmware if you make a reset setup job as the firmware set as system disk sda and then this job does not delete the partition table in such job whereas it makes it on the other disks like sdb...

wd9895 wrote:

Upgrade firmware will fail using the disk in righthand side slot

I did it yesterday. It worked flawlessly. In the right slot.
Don't get me wrong, I only tell you what I observed.

Just curious, please send dmesg output when the disk is in righthand slot