Lacie 5Big2 Failed After Firmware Update

[Mijzelf]

Invalid argument. I suppose the disk has a unsupported filesystem. @Jocko, is it possible to create an ext3 volume using this software?

[unlucky1]

I can't get it. What am I doing wrong? I may need to reformat the disk, right?

[Jocko]

@mijzelf
If I remember well, mkfs.ext3 is included with this sofware

[Jocko]

Found the binary name is mke2fs-ext3

[Mijzelf]

@fvdw: mdev should be able to do it. It does in the Lacie initrd. And else a simple script parsing /proc/partitions can do.

[unlucky1]

Binary not found :(

[unlucky1]

Oops, my bad- typo. But it fails:

Code: Select all

 mke2fs -ext3 /dev/sef1
mke2fs: invalid option -- e
BusyBox v1.21.0 (2013-02-04 10:48:06 GMT+1) multi-call binary.

Usage: mke2fs [-Fn] [-b BLK_SIZE] [-i INODE_RATIO] [-I INODE_SIZE] [-m RESERVED_PERCENT] [-L LABEL] BLOCKDEV [KBYTES]

        -b BLK_SIZE     Block size, bytes
        -F              Force
        -i RATIO        Max number of files is filesystem_size / RATIO
        -I BYTES        Inode size (min 128)
        -L LBL          Volume label
        -m PERCENT      Percent of blocks to reserve for admin
        -n              Dry run

root@(none):/ # mke2fs --ext3 /dev/sef1
mke2fs: unrecognized option `--ext3'
BusyBox v1.21.0 (2013-02-04 10:48:06 GMT+1) multi-call binary.

Usage: mke2fs [-Fn] [-b BLK_SIZE] [-i INODE_RATIO] [-I INODE_SIZE] [-m RESERVED_PERCENT] [-L LABEL] BLOCKDEV [KBYTES]

        -b BLK_SIZE     Block size, bytes
        -F              Force
        -i RATIO        Max number of files is filesystem_size / RATIO
        -I BYTES        Inode size (min 128)
        -L LBL          Volume label
        -m PERCENT      Percent of blocks to reserve for admin
        -n              Dry run


[fvdw]

in the meantime I had a spare moment to fire up my 5big2 and I can confirm that it uses the same funny partition allocation to the the device nodes

This is my output running 2 disks (sda is in slot1 and sdb is in slot 2)

Code: Select all

root@5big5:/ # cat proc/partitions
major minor  #blocks  name

  31        0       1024 mtdblock0
  31        1      16384 mtdblock1
  31        2     244736 mtdblock2
   8        0  976762584 sdb
   8        1     524288 sdb1
   8        2     524288 sdb2
   8        3     524288 sdb3
   8        4       4096 sdb4
   8        5     786432 sdb5
   8        6       8192 sdb6
   8        7     524288 sdb7
   8        8  973865671 sdb8
   8       16  976762584 sda
   8       17     524288 sda1
   8       18     524288 sda2
   8       19     524288 sda3
   8       20       8192 sda4
   8       21     786432 sda5
   8       22       8192 sda6
   8       23     524288 sda7
   8       24  973860551 sda8
root@5big5:/ #

This corresponds with what i find in /dev

Code: Select all

root@5big5:/dev # ls -al sd*
brw-rw----  1 root root 8, 16 2013-06-26 20:28 sda
brw-rw----  1 root root 8, 17 2013-06-26 20:28 sda1
brw-rw----  1 root root 8, 18 2013-06-26 20:28 sda2
brw-rw----  1 root root 8, 19 2013-06-26 20:28 sda3
brw-rw----  1 root root 8, 20 2013-06-26 20:28 sda4
brw-rw----  1 root root 8, 21 2013-06-26 20:28 sda5
brw-rw----  1 root root 8, 22 2013-06-26 20:28 sda6
brw-rw----  1 root root 8, 23 2013-06-26 20:28 sda7
brw-rw----  1 root root 8, 24 2013-06-26 20:28 sda8
brw-rw----  1 root root 8,  0 2013-06-26 20:28 sdb
brw-rw----  1 root root 8,  1 2013-06-26 20:28 sdb1
brw-rw----  1 root root 8,  2 2013-06-26 20:28 sdb2
brw-rw----  1 root root 8,  3 2013-06-26 20:28 sdb3
brw-rw----  1 root root 8,  4 2013-06-26 20:28 sdb4
brw-rw----  1 root root 8,  5 2013-06-26 20:28 sdb5
brw-rw----  1 root root 8,  6 2013-06-26 20:28 sdb6
brw-rw----  1 root root 8,  7 2013-06-26 20:28 sdb7
brw-rw----  1 root root 8,  8 2013-06-26 20:28 sdb8
root@5big5:/dev #

The reason that it is corresponding is probably cause our firmware updates the device nodes when booting. In the standalone kernel this is not done so the default /dev definitions are wrong

mmm...never noticed this
need to check if the update is also possible in the standalone kernel

[fvdw]

Great. So do

Code: Select all

mke2fs-ext3 /dev/sef1

and get a coffee. This is gonna take some time.

BTW, this will destroy the data on the usb disk.

wait a moment he needs to use a different version, as the one in busybox will not be able to handle a 3TB drive.
Give me a minute (or 2)

[Jocko]

@fvdw
I made a mistake the binary must be uploaded and it is present in the folder tftp. This binary must support this big disk.