cannot create new profile ZS-2.0RC1 ALIX img file

Forums Network Management ZeroShell cannot create new profile ZS-2.0RC1 ALIX img file

  • This topic is empty.
Viewing 1 post (of 1 total)
  • Author
  • #43452

    I have dd’d the ALIX img file to a 2GB CF. Installed the CFs to an ALIX board it boots fine with the “default” profile.

    However when I try to create a new profile on the “Profiles” web page, I see:

    /dev/sda3 “Unknown filesystem”

    See screenshot:

    When I select the radio button for /dev/sda3 to create a new profile, it offers to format /dev/sda3!

    In my first attempt, I went ahead and formatted /dev/sda3. However, the system would not come up on a reboot. I think the reformat blew away the “default” profile and the FS label etc.

    Second attempt, I have tried to figure out the problem.

    When I select /dev/sda3 and click on “View FS” button there is no information about the file system.

    I logged into the serial console and did the following:

    1. fdisk -l
    2. fsck.ext4 -pDf /dev/sda3
    3. dumpe2fs
    4. file -s
    5. blkid

    Output of the respective utility listed below.

    fdisk is indeed showing three partitions. However fsck.ext4 is complaining that the size of the ext4 file system (331884) is larger than the /dev/sda3 device size (315424) 😯

    Booting system rescue CD (v2.8.1) along with the ALIX image file; I used the above utils and got the same results.

    BTW, the 2.0RC1 Soekris image has the same manifestation for /dev/sda3.

    How to create a new Profile w/o reformatting /dev/sda3?

    Any work around for this?

    — Arun Khan

    root@zeroshell root> fdisk -l

    Disk /dev/sda: 1949 MB, 1949999616 bytes
    255 heads, 63 sectors/track, 237 cylinders, total 3808593 sectors
    Units = sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disk identifier: 0xcf5090fb

    Device Boot Start End Blocks Id System
    /dev/sda1 63 96389 48163+ 83 Linux
    /dev/sda2 96390 1285199 594405 83 Linux
    /dev/sda3 1285200 4030463 1372632 83 Linux
    root@zeroshell root> fsck.ext4 -pDf /dev/sda3
    ZS_Profiles: The filesystem size (according to the superblock) is 331884 blocks
    The physical size of the device is 315424 blocks
    Either the superblock or the partition table is likely to be corrupt!

    (i.e., without -a or -p options)

    root@zeroshell root> dumpe2fs /dev/sda3 | head -n20
    dumpe2fs 1.42 (29-Nov-2011)
    Filesystem volume name: ZS Profiles
    Last mounted on: /Database
    Filesystem UUID: 227a3861-c04e-41ba-a600-1d84adc623c0
    Filesystem magic number: 0xEF53
    Filesystem revision #: 1 (dynamic)
    Filesystem features: has_journal ext_attr resize_inode dir_index filetype extent flex_bg sparse_super large_file huge_file uninit_bg dir_nlink extra_isize
    Filesystem flags: signed_directory_hash
    Default mount options: user_xattr acl
    Filesystem state: clean with errors
    Errors behavior: Continue
    Filesystem OS type: Linux
    Inode count: 83072
    Block count: 331884
    Reserved block count: 16594
    Free blocks: 284034
    Free inodes: 82087
    First block: 0
    Block size: 4096
    Fragment size: 4096
    Reserved GDT blocks: 81

    root@zeroshell root> for x in 1 2 3; do file -s /dev/sda${x}; done
    /dev/sda1: Linux rev 1.0 ext3 filesystem data
    /dev/sda2: ISO 9660 CD-ROM filesystem data ‘CDROM ‘ (bootable)
    /dev/sda3: Linux rev 1.0 ext3 filesystem data (errors) (large files)

    root@zeroshell root> for x in 1 2 3; do blkid /dev/sda${x}; done
    /dev/sda1: LABEL=”ZS-2.0.RC1″ UUID=”3d846a4a-c976-4bde-9adc-6d1ee06a4e56″ SEC_TYPE=”ext2″ TYPE=”ext3″
    /dev/sda2: LABEL=”CDROM” TYPE=”iso9660″
    /dev/sda3: LABEL=”ZS Profiles” UUID=”227a3861-c04e-41ba-a600-1d84adc623c0″ TYPE=”ext4″

Viewing 1 post (of 1 total)
  • You must be logged in to reply to this topic.