[1.9.1] Vfat & FAT32 Issues

[Luis]

:/var/log/maas$ dpkg -l '*maas*'|cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-====================================-=====================================-============-============================================================================================================
ii maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server all-in-one metapackage
ii maas-cli 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS command line API tool
ii maas-cluster-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server cluster controller
ii maas-common 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server common files
ii maas-dhcp 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DHCP server
ii maas-dns 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS DNS server
ii maas-proxy 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Caching Proxy
ii maas-region-controller 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server complete region controller
ii maas-region-controller-min 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS Server minimum region controller
ii python-django-maas 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server Django web framework
ii python-maas-client 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS python API client
ii python-maas-provisioningserver 1.9.1+bzr4543-0ubuntu1~trusty1 all MAAS server provisioning libraries

[Blake Rouse (blake-rouse)]

What version of Ubuntu were you trying to deploy?

[Blake Rouse (blake-rouse)]

Also please provide the full installation log for the node.

[Luis (luis-ramirez)]

Ubuntu Trusty. I've been deployed 3 servers 3 weeks ago without any issue.

[Luis (luis-ramirez)]

The cloud-init-output.log.

Regards
Luis

[Ryan Harper (raharper)]

The curtin configuration is specifying fstype: vfat, instead use fstype: fat32 (or fat, fat16, fat12 as needed).

From the cloud-init-output.log:

An error occured handling 'sda-part1_format': ValueError - unsupported fs type 'vfat'
unsupported fs type 'vfat'
Installation failed with exception: Unexpected error while running command.
Command: ['curtin', 'block-meta', 'custom']

[Luis (luis-ramirez)]

I try to use fat32 but grub can not boot with this message: unsupported fs.

I've installed other 3 nodes 3 weeks ago with this conf without any issues. I've attached the cloud-init-log from one node deployed without issues...

Regards
Luis

[Ryan Harper (raharper)]

Your last log is from a boot after deployment, not the actual node
deployment.

What we really need is the curtin config used in the successful case as
well as the failure case.

maas <user> node get-curtin-config <system_id>

On Thu, Mar 17, 2016 at 12:32 PM, Luis <email address hidden> wrote:

> I try to use fat32 but grub can not boot with this message: unsupported
> fs.
>
> I've installed other 3 nodes 3 weeks ago with this conf without any
> issues. I've attached the cloud-init-log from one node deployed without
> issues...
>
> Regards
> Luis
>
> ** Attachment added: "Right Deployment with VFAT"
>
> https://bugs.launchpad.net/cloud-init/+bug/1557334/+attachment/4602412/+files/cloud-init-output.log.OK
>
> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https://bugs.launchpad.net/bugs/1557334
>
> Title:
> [1.9.1] Vfat unsupported
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1557334/+subscriptions
>

[Luis (luis-ramirez)]

Curtin Config for the node.

[Ryan Harper (raharper)]

Thanks for the attachment. Is that for the failing case? Do you have the config for the node that successfully deployed?

Please query the maas server for which version of package curtin is installed? (dpkg --list | grep curtin)

[Luis (luis-ramirez)]

Yes... It's for failed deployment node.

xavier:~$ dpkg --list | grep curtin
ii curtin-common 0.1.0~bzr359-0ubuntu1 all Library and tools for curtin installer
ii python-curtin 0.1.0~bzr359-0ubuntu1 all Library and tools for curtin installer

[Luis (luis-ramirez)]

I can make

# mkfs.vfat /dev/sda1

and mount the device, but if try to make

# parted /dev/sda 1 [fat16/fat32/ext2/..]

i get this message:

root@ample-cactus:~# parted /dev/sda mkfs 1 fat16
WARNING: you are attempting to use parted to operate on (mkfs) a file system.
parted's file system manipulation code is not as robust as what you'll find in
dedicated, file-system-specific packages like e2fsprogs. We recommend
you use parted only to manipulate partition tables, whenever possible.
Support for performing most operations on most types of file systems
will be removed in an upcoming release.
Warning: The existing file system will be destroyed and all data on the partition will be lost. Do you want to continue?
parted: invalid token: 1
Yes/No? Yes
Partition number? 1
File system type? [ext2]? fat16
Backtrace has 9 calls on stack:
  9: /lib/x86_64-linux-gnu/libparted.so.0(ped_assert+0x31) [0x7ffa7964c4b1]
  8: /lib/x86_64-linux-gnu/libparted.so.0(+0x25d53) [0x7ffa79662d53]
  7: /lib/x86_64-linux-gnu/libparted.so.0(fat_create+0x189) [0x7ffa79665fd9]
  6: /lib/x86_64-linux-gnu/libparted.so.0(ped_file_system_create+0x51) [0x7ffa7964def1]
  5: parted() [0x4083b1]
  4: parted(non_interactive_mode+0x8f) [0x40dc5f]
  3: parted(main+0x146d) [0x4064ed]
  2: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5) [0x7ffa78e2aec5]
  1: parted() [0x406617]

You found a bug in GNU Parted! Here's what you have to do:

Don't panic! The bug has most likely not affected any of your data.
Help us to fix this bug by doing the following:

Check whether the bug has already been fixed by checking
the last version of GNU Parted that you can find at:

        http://ftp.gnu.org/gnu/parted/

Please check this version prior to bug reporting.

If this has not been fixed yet or if you don't know how to check,
please visit the GNU Parted website:

        http://www.gnu.org/software/parted

for further information.

Your report should contain the version of this release (2.3)
along with the error message below, the output of

        parted DEVICE unit co print unit s print

and the following history of commands you entered.
Also include any additional information about your setup you
consider important.

Assertion (bs != NULL) at ../../../../libparted/fs/fat/bootsector.c:282 in function fat_boot_sector_set_boot_code() failed.

Aborted (core dumped)

[Luis (luis-ramirez)]

I think i get the bug... mke2fs.conf has not defined vfat filesystem...

root@ample-cactus:/var/lib/cloud/instance/scripts/curtin/curtin# mkfs -v -t vfat /dev/sda1
mke2fs 1.42.9 (4-Feb-2014)

Your mke2fs.conf file does not define the vfat filesystem type.
Aborting...
root@ample-cactus:/var/lib/cloud/instance/scripts/curtin/curtin# cat /etc/mke2fs.conf
[defaults]
        base_features = sparse_super,filetype,resize_inode,dir_index,ext_attr
        default_mntopts = acl,user_xattr
        enable_periodic_fsck = 0
        blocksize = 4096
        inode_size = 256
        inode_ratio = 16384

[fs_types]
        ext3 = {
                features = has_journal
        }
        ext4 = {
                features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
                auto_64-bit_support = 1
                inode_size = 256
        }
        ext4dev = {
                features = has_journal,extent,huge_file,flex_bg,uninit_bg,dir_nlink,extra_isize
                inode_size = 256
                options = test_fs=1
        }
        small = {
                blocksize = 1024
                inode_size = 128
                inode_ratio = 4096
        }
        floppy = {
                blocksize = 1024
                inode_size = 128
                inode_ratio = 8192
        }
        big = {
                inode_ratio = 32768
        }
        huge = {
                inode_ratio = 65536
        }
        news = {
                inode_ratio = 4096
        }
        largefile = {
                inode_ratio = 1048576
                blocksize = -1
        }
        largefile4 = {
                inode_ratio = 4194304
                blocksize = -1
        }
        hurd = {
             blocksize = 4096
             inode_size = 128
        }

[Ryan Harper (raharper)]

On Fri, Mar 18, 2016 at 4:50 AM, Luis <email address hidden> wrote:

> Yes... It's for failed deployment node.
>

OK

>
> xavier:~$ dpkg --list | grep curtin
> ii curtin-common 0.1.0~bzr359-0ubuntu1
> all Library and tools for curtin installer
> ii python-curtin 0.1.0~bzr359-0ubuntu1
> all Library and tools for curtin installer
>

Thanks

>
>
> ** Attachment added: "curtin-config.OK"
>
> https://bugs.launchpad.net/maas/+bug/1557334/+attachment/4602977/+files/curtin-config.OK
>
>
The OK config has the same issue with curtin, fstype: vfat;
This should fail as well as the curtin code expects: fat32, fat16, fat12 or
fat.

Would you be able to recommission a node that passes, deploy it again, and
collect cloud-init*.log ?

[Ryan Harper (raharper)]

We don't use parted to create filesystems in curtin, so I don't think
that's an issue with this bug.
Could you open a separate bug against parted?

On Fri, Mar 18, 2016 at 7:50 AM, Luis <email address hidden> wrote:

> I can make
>
> # mkfs.vfat /dev/sda1
>
> and mount the device, but if try to make
>
> # parted /dev/sda 1 [fat16/fat32/ext2/..]
>
> i get this message:
>
> root@ample-cactus:~# parted /dev/sda mkfs 1 fat16
> WARNING: you are attempting to use parted to operate on (mkfs) a file
> system.
> parted's file system manipulation code is not as robust as what you'll
> find in
> dedicated, file-system-specific packages like e2fsprogs. We recommend
> you use parted only to manipulate partition tables, whenever possible.
> Support for performing most operations on most types of file systems
> will be removed in an upcoming release.
> Warning: The existing file system will be destroyed and all data on the
> partition will be lost. Do you want to continue?
> parted: invalid token: 1
> Yes/No? Yes
> Partition number? 1
> File system type? [ext2]? fat16
> Backtrace has 9 calls on stack:
> 9: /lib/x86_64-linux-gnu/libparted.so.0(ped_assert+0x31) [0x7ffa7964c4b1]
> 8: /lib/x86_64-linux-gnu/libparted.so.0(+0x25d53) [0x7ffa79662d53]
> 7: /lib/x86_64-linux-gnu/libparted.so.0(fat_create+0x189)
> [0x7ffa79665fd9]
> 6: /lib/x86_64-linux-gnu/libparted.so.0(ped_file_system_create+0x51)
> [0x7ffa7964def1]
> 5: parted() [0x4083b1]
> 4: parted(non_interactive_mode+0x8f) [0x40dc5f]
> 3: parted(main+0x146d) [0x4064ed]
> 2: /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
> [0x7ffa78e2aec5]
> 1: parted() [0x406617]
>
>
> You found a bug in GNU Parted! Here's what you have to do:
>
> Don't panic! The bug has most likely not affected any of your data.
> Help us to fix this bug by doing the following:
>
> Check whether the bug has already been fixed by checking
> the last version of GNU Parted that you can find at:
>
> http://ftp.gnu.org/gnu/parted/
>
> Please check this version prior to bug reporting.
>
> If this has not been fixed yet or if you don't know how to check,
> please visit the GNU Parted website:
>
> http://www.gnu.org/software/parted
>
> for further information.
>
> Your report should contain the version of this release (2.3)
> along with the error message below, the output of
>
> parted DEVICE unit co print unit s print
>
> and the following history of commands you entered.
> Also include any additional information about your setup you
> consider important.
>
> Assertion (bs != NULL) at ../../../../libparted/fs/fat/bootsector.c:282
> in function fat_boot_sector_set_boot_code() failed.
>
> Aborted (core dumped)
>
> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https://bugs.launchpad.net/bugs/1557334
>
> Title:
> [1.9.1] Vfat unsupported
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1557334/+subscriptions
>

[Luis (luis-ramirez)]

Forget it... is only for ext2, ext3 & ext4...

[Luis (luis-ramirez)]

The Ok config was deployed without any issue.

sorry but i can not redeploy the nodes, we have a ceph cluster deployed and i can not remove the nodes.

[Ryan Harper (raharper)]

On Fri, Mar 18, 2016 at 8:58 AM, Luis <email address hidden> wrote:

> I think i get the bug... mke2fs.conf has not defined vfat filesystem...
>

mke2fs is for ext filesystems, so not related.

I believe the following update[1] to curtin should resolve the issue.
However, I'm concerned that there may be something else going on
since you have machines that deploy OK despite using the exact same curtin
configuration; v359 of curtin should fail the same
everywhere when specifying fstype: vfat.

1. Prior to commit 343, block_meta custom handled 'fstype: vfat' via
fallthrough and invoked mkfs.vfat without options. Restore this by adding
'vfat' to the fstype dictionary. Add a unittest to ensure we don't break
fstype: vfat in the future.
http://bazaar.launchpad.net/~curtin-dev/curtin/trunk/revision/363?start_revid=363

[Luis (luis-ramirez)]

If i deploy with fat32, the deployment was sucesfull, but when the server boots, grub display an error:

fs unsupported.

MAAS only allow to create VFAT, FAT32, EXT2 & EXT4 FS, and this server needs UEFI active because we are using 4k disks. We have deployed 80 nodes, 75 with flat ext4 fs and 5 with uefi boot with vfat. This node could not be deployed at the sametime because it has hw issues and when we try to deploy it 2 weeks later, we can not do it with this failure.

Regards
Luis

[Ryan Harper (raharper)]

On Fri, Mar 18, 2016 at 9:20 AM, Luis <email address hidden> wrote:

> If i deploy with fat32, the deployment was sucesfull, but when the
> server boots, grub display an error:
>
> fs unsupported.
>
> MAAS only allow to create VFAT, FAT32, EXT2 & EXT4 FS, and this server
> needs UEFI active because we are using 4k disks. We have deployed 80
> nodes, 75 with flat ext4 fs and 5 with uefi boot with vfat. This node
> could not be deployed at the sametime because it has hw issues and when
> we try to deploy it 2 weeks later, we can not do it with this failure.
>

Can you attach the fat32 version of curtin config? Let's debug this
grub/uefi
boot issue.

>
> Regards
> Luis
>
> --
> You received this bug notification because you are subscribed to curtin.
> Matching subscriptions: curtin-bugs-all
> https://bugs.launchpad.net/bugs/1557334
>
> Title:
> [1.9.1] Vfat unsupported
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1557334/+subscriptions
>

[Luis (luis-ramirez)]

Sure... the VFAT deployment is working... thank you very much. Deployed with FAT32, you could find attached the curting_config.

Regards
Luis?field.comment=Sure... the VFAT deployment is working... thank you very much. Deployed with FAT32, you could find attached the curting_config.

Regards
Luis

[Luis (luis-ramirez)]

Deployed sucessfully but as i told you... we get this failure...

[Ryan Harper (raharper)]

Can you attach the curtin/maas log of the install with fat32 that fails to boot?

[Luis (luis-ramirez)]

Sorry, I can not attach the log for a Fat32 install. We have deployed all nodes as vfat.

Regards
Luis

[Launchpad Janitor (janitor)]

[Expired for curtin because there has been no activity for 60 days.]