Bug#766964: grml2usb (0.14.10) :fatal error
* Martin Ziegler [Mon Oct 27, 2014 at 10:05:13AM +0100]: >grml2usb --bootoptions=lang=de --bootoptions=nodhcp > grml64-full_2014.03.iso /dev/sdd1 > stops with the error >Executing grml2usb version 0.14.10 >Using ISO grml64-full_2014.03.iso >Fatal: 'NoneType' object has no attribute 'getFlag' [...] We finally managed to reproduce this issue with someone showing up on IRC exploring this issue. This issue is caused by certain USB devices which seem to have specific data on them causing python-parted to fail to properly recognize them. Sadly we didn't manage to identify the reponsible data on the usb device that causes this behaviour, but as soon as the device gets overwritten with zeros (dd if=/dev/zero of=/dev/sdX) the issue is gone and grml2usb/python-parted work as intended. We just commited a workaround to grml2usb to not fail in this situation and display a warning message and fall back to some legacy code instead. If someone should be able to reproduce this behaviour we'd be *very* interested in a dump of the USB device's data, please contact us then! Thanks everyone for your feedback and help in resolving this issue! regards, -mika- signature.asc Description: Digital signature
Bug#766964: grml2usb (0.14.10) :fatal error
Package: grml2usb Version: 0.14.10 Followup-For: Bug #766964 Not sure if it may be related, but today I got the Fatal: 'NoneType' object has no attribute 'getFlag' error when trying to run grml2usb via sudo: $ sudo grml2usb grml96-full_2014.11.iso /dev/sdb1 But everything worked fine when grml2usb was run from a full root session: $ sudo su - # grml2usb grml96-full_2014.11.iso /dev/sdb1 -- Michał Politowski Talking has been known to lead to communication if practiced carelessly. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#766964: grml2usb (0.14.10) :fatal error
Dear Evgeni, I succeeded to install grml on the same usbstick, doing the following: 1. the partion label was "loop". I changed it to "msdos" 2. I formatted /dev/sdb1 with mkfs.fat instead of mkfs.vfat After this df was as fast as it should be (I used /dev/sdd1 before, since the other device-names were used otherwise) The command 3. grml2usb --bootoptions=lang=de --bootoptions=nodhcp --grub grml64-full_2014.03.iso /dev/sdb1 resulted in: Executing grml2usb version 0.14.10 Using ISO /tmp/grml64-full_2014.03.iso Identified grml flavour "grml64-full". Copying files. This might take a while Installing default MBR mount: special device /dev/sdb1 does not exist Fatal: Error executing mount (no filesystem on the partition?) Cleaning up before exiting... Fatal: [Errno 2] No such file or directory: '/tmp/grml2usb3oHiCX' The grml-files were copied on /dev/sdb1, but the stick didn't boot. I tried then 4. grml2usb --bootloader-only --bootoptions=lang=de --bootoptions=nodhcp --grub grml64-full_2014.03.iso /dev/sdb1 The output was Executing grml2usb version 0.14.10 Using ISO grml64-full_2014.03.iso Identified grml flavour grml64-full. Installing default MBR Installing grub as bootloader /usr/sbin/grub-install: Fehler: Mehr als ein Installationsgerät?. Installing for i386-pc platform. /usr/sbin/grub-install: Warnung: Dateisystem »fat« unterstützt keine Einbettungen. /usr/sbin/grub-install: Warnung: Einbettung ist nicht möglich. GRUB kann in dieser Konfiguration nur mittels Blocklisten installiert werden. Blocklisten sind allerdings UNZUVERLÄSSIG und deren Verwendung wird daher nicht empfohlen.. installation beendet. Keine Fehler aufgetreten. Note: grml flavour grml64-full was installed as the default booting system. Note: you can boot flavour grml64-full using 'grml64-full' on the commandline. Finished execution of grml2usb (0.14.10). Have fun with your Grml system. Now a had a bootable gmrl-stick Best regards, Martin
Bug#766964: grml2usb (0.14.10) :fatal error
Hi Martin, On 10/27/2014 11:07 AM, Martin Ziegler wrote: > here is the output of fdisk: thanks! I see it is for /dev/sdb, while your initial report was about /dev/sdd. Is there a flacky USB connection that resets too often in between? > Disk /dev/sdb: 7,2 GiB, 7745830400 bytes, 15128575 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 > Disklabel type: dos > Disk identifier: 0x2c6b7369 > > Device Boot Start End Sectors Size Id Type > /dev/sdb1 * 2048 15128574 15126527 7,2G f2 DOS > secondary I created the very same setup here, and parted detects the partition just fine. Creation: evgeni@nana ~ % sudo dd if=/dev/zero of=/tmp/grml-test.img bs=1M count=1024 1024+0 records in 1024+0 records out 1073741824 bytes (1.1 GB) copied, 2.08537 s, 515 MB/s evgeni@nana ~ % sudo losetup --find --show /tmp/grml-test.img /dev/loop0 evgeni@nana ~ % sudo fdisk /dev/loop0 Welcome to fdisk (util-linux 2.25.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. Device does not contain a recognized partition table. Created a new DOS disklabel with disk identifier 0xa2378f95. Command (m for help): n Partition type p primary (0 primary, 0 extended, 4 free) e extended (container for logical partitions) Select (default p): Using default response p. Partition number (1-4, default 1): First sector (2048-2097151, default 2048): Last sector, +sectors or +size{K,M,G,T,P} (2048-2097151, default 2097151): Created a new partition 1 of type 'Linux' and of size 1023 MiB. Command (m for help): t Selected partition 1 Hex code (type L to list all codes): f2 Changed type of partition 'Linux' to 'DOS secondary'. Command (m for help): w The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. evgeni@nana ~ % sudo mkfs.vfat /dev/loop0p1 mkfs.fat 3.0.26 (2014-03-07) Loop device does not match a floppy size, using default hd params evgeni@nana ~ % sudo fdisk -l /dev/loop0 Disk /dev/loop0: 1 GiB, 1073741824 bytes, 2097152 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 Disklabel type: dos Disk identifier: 0xa2378f95 Device Boot Start End Sectors Size Id Type /dev/loop0p1 2048 2097151 2095104 1023M f2 DOS secondary Parted by hand: >>> import parted >>> d = parted.getDevice('/dev/loop0') >>> disk = parted.Disk(d) >>> part = disk.getPartitionByPath('/dev/loop0p1') >>> part >>> print part.getFlag(parted.PARTITION_BOOT) False > I observed that df needs very log to read informations from /dev/sdb1 That's odd. Could you try another USB drive with the same partition layout? Just to be sure? Greets Evgeni -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#766964: grml2usb (0.14.10) :fatal error
Dear Evgeni, here is the output of fdisk: Disk /dev/sdb: 7,2 GiB, 7745830400 bytes, 15128575 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 Disklabel type: dos Disk identifier: 0x2c6b7369 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 15128574 15126527 7,2G f2 DOS secondary I observed that df needs very log to read informations from /dev/sdb1 ~# mount -t vfat /dev/sdb1 /usb ~# time df /usb Dateisystem1K-Blöcke Benutzt Verfügbar Verw% Eingehängt auf /dev/sdb17548500 4 75484961% /usb real0m29.915s user0m0.000s sys 0m0.240s Regards, Martin
Bug#766964: grml2usb (0.14.10) :fatal error
Hi Martin, On 10/27/2014 10:05 AM, Martin Ziegler wrote: >grml2usb --bootoptions=lang=de --bootoptions=nodhcp > grml64-full_2014.03.iso /dev/sdd1 > > stops with the error > >Executing grml2usb version 0.14.10 >Using ISO grml64-full_2014.03.iso >Fatal: 'NoneType' object has no attribute 'getFlag' Can you provide a "fdisk -l" for /dev/sdd please? I do not really understand how "part" can be None here :/ In the meantime, you can override the bootflag detection with --skip-bootflag. Greets Evgeni -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org