bouilloncube fails creating partition table
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| bouilloncube |
Fix Committed
|
Critical
|
krgn | ||
Bug Description
sudo ./make-
fails with this output:
[?] Are you sure your target is /dev/sdb ? (y/n)y
[*] mounting ISO
[*] ISO file is 1172 MB
[*] force unmounting partitions from /dev/sdb
[*] erasing target's partition table
[*] creating system partition of 1222 MB
parted: invalid token: primary
Error: Expecting a file system type.
Error: Partition doesn't exist.
[*] force unmounting partition /dev/sdb1
umount: /dev/sdb1: not found
mkfs.vfat 3.0.3 (18 May 2009)
/dev/sdb1: No such file or directory
[*] creating persistence partition
parted: invalid token: primary
Error: Expecting a file system type.
[*] force unmounting partition /dev/sdb2
umount: /dev/sdb2: not found
mke2fs 1.41.9 (22-Aug-2009)
Could not stat /dev/sdb2 --- No such file or directory
The device apparently does not exist; did you specify it correctly?
[*] copying live folder
mount: special device /dev/sdb1 does not exist
/mnt/make-live-iso ~/code/
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
/mnt/make-
^C~/code/
[*] sylinux configuration
/dev/sdb1: No such file or directory
[*] cleaning up, unmounting and ...
umount: /mnt/make-
[*] ...done.
note the line:
parted: invalid token: primary
this is the process I use:
-plug in the stick
-stick gets automounted as /media/disk
-exectute command line above
I can fix the problem when I manually re-create a partition table as msdos and re-run the script
| Changed in bouilloncube: | |
| importance: | Undecided → Critical |
| Claude Heiland-Allen (claudiusmaximus) wrote | #1 |
| Claude Heiland-Allen (claudiusmaximus) wrote | #2 |
| krgn (karsten-goto10) wrote | #3 |
| krgn (karsten-goto10) wrote | #4 |
| krgn (karsten-goto10) wrote | #5 |
| krgn (karsten-goto10) wrote | #6 |
| Changed in bouilloncube: | |
| status: | New → Fix Committed |
| assignee: | nobody → krgn (karsten-goto10) |
At a guess (and a general consideration too): the script seems to assume that the device has a valid partition table to start with, and deletes the partitions on it one by one. I'm not sure if the order in which partitions are deleted is handled correctly (extended partitions must go before their owner primary partitions at a guess?), but I think it's the wrong approach anyway: As the device will be wiped anyway, it might be better to use dd to wipe the partition table to a known pristine/clean state before starting to avoid bugging out when an unusual partition table is encountered?
http://