Re: [Bug 1875548] Re: Its not easy to determine how to skip the filesystem check
I do not think I have had a Live USB to do a disk check with 20.10 and later, except with 22.04 daily. On Tue, Mar 22, 2022 at 11:36 AM Mauricio Faria de Oliveira < 1875...@bugs.launchpad.net> wrote: > The first issue in comment #18 (fsck.mode=skip is ignored if it's > last on cmdline) is in progress in bug 1892369 (comment 34) [1]. > > The second issue (ctrl-c doesn't abort the disk check) is also > described there, and unfortunately it's a limitation which was > introduced as part of another change, apparently (not a bug), > and is no longer an option. > > ... > > Currently, to skip the disk integrity check (casper-md5check), > please insert 'fsck.mode=skip' before '---' in kernel cmdline > (i.e., make sure it's not the last string). > > [1] > https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1892369/comments/34 > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1875548 > > Title: > Its not easy to determine how to skip the filesystem check > > Status in casper package in Ubuntu: > Fix Released > > Bug description: > I see that Live Ubuntu 20.04 is plagued by disk checking on boot. > > Not just with Live USB but with Persistent USB also. > > If not fast enough to cancel with ctl-c it starts on > filesystem.squashfs and runs until over 90% complete. > > Very irritating. There have been quite a few complaints on Ask Ubuntu > already. > > If it was just a run once it would not be so bad. > > Is there some way to get rid of this or is it a bug we have to live > with? > > Perusing Ask Ubuntu everyday for many years I have never seen anybody > ask for such a feature. > > A run once filesystem check might have its uses on a Live installer > drive but is not needed on a Persistent utility drive. > > The only alternative I see is to use a Full install USB drive were > automatic disk checking is not run. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: ubuntu-release-upgrader-core 1:20.04.18 > ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 > Uname: Linux 5.4.0-26-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > CasperMD5CheckResult: skip > CasperVersion: 1.445 > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > Date: Tue Apr 28 06:07:32 2020 > LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) > PackageArchitecture: all > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=C.UTF-8 >SHELL=/bin/bash > SourcePackage: ubuntu-release-upgrader > Symptom: dist-upgrade > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions > > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875548 Title: Its not easy to determine how to skip the filesystem check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1875548] Re: Its not easy to determine how to skip the filesystem check
Jay: What are you using to make your USB, ISO boot using GRUB2, or a tool like Rufus or mkusb? I can not duplicate your result using Rufus with Syslinux boot in BIOS mode. I will try ISO boot using GRUB2 next. On Sat, Feb 6, 2021 at 10:30 AM Jay Michael <1875...@bugs.launchpad.net> wrote: > "fsck.mode=skip" does *not* skip disk check unless "quiet" is also > on the kernel command line. > > Without "quiet" on the kernel command line, even with > "fsck.mode=skip", I see lines flying by until it gets to the squashfs > file, at which point it pauses long enough for me to read some lines. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1875548 > > Title: > Its not easy to determine how to skip the filesystem check > > Status in casper package in Ubuntu: > Fix Released > > Bug description: > I see that Live Ubuntu 20.04 is plagued by disk checking on boot. > > Not just with Live USB but with Persistent USB also. > > If not fast enough to cancel with ctl-c it starts on > filesystem.squashfs and runs until over 90% complete. > > Very irritating. There have been quite a few complaints on Ask Ubuntu > already. > > If it was just a run once it would not be so bad. > > Is there some way to get rid of this or is it a bug we have to live > with? > > Perusing Ask Ubuntu everyday for many years I have never seen anybody > ask for such a feature. > > A run once filesystem check might have its uses on a Live installer > drive but is not needed on a Persistent utility drive. > > The only alternative I see is to use a Full install USB drive were > automatic disk checking is not run. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: ubuntu-release-upgrader-core 1:20.04.18 > ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 > Uname: Linux 5.4.0-26-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > CasperMD5CheckResult: skip > CasperVersion: 1.445 > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > Date: Tue Apr 28 06:07:32 2020 > LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) > PackageArchitecture: all > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=C.UTF-8 >SHELL=/bin/bash > SourcePackage: ubuntu-release-upgrader > Symptom: dist-upgrade > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875548 Title: Its not easy to determine how to skip the filesystem check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1875548] Re: Its not easy to determine how to skip the filesystem check
Jay: A line comes up about disk check but no disk check is performed. If you remove the line "fsck.mode=skip" from grub you should see the difference, the check shows every file. On Fri, Feb 5, 2021 at 11:21 AM Jay Michael <1875...@bugs.launchpad.net> wrote: > Ubuntu 20.04.2 behaves the same way. > > "quiet" kernel parameter seems to enable skipping the disk check: With > "quiet" on the kernel command line, one of the few lines to appear on > the screen is "disk check skipped", and the boot completes noticeably > faster. (35s instead of 55s, booting from an ISO file on a hard disk) > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1875548 > > Title: > Its not easy to determine how to skip the filesystem check > > Status in casper package in Ubuntu: > Fix Released > > Bug description: > I see that Live Ubuntu 20.04 is plagued by disk checking on boot. > > Not just with Live USB but with Persistent USB also. > > If not fast enough to cancel with ctl-c it starts on > filesystem.squashfs and runs until over 90% complete. > > Very irritating. There have been quite a few complaints on Ask Ubuntu > already. > > If it was just a run once it would not be so bad. > > Is there some way to get rid of this or is it a bug we have to live > with? > > Perusing Ask Ubuntu everyday for many years I have never seen anybody > ask for such a feature. > > A run once filesystem check might have its uses on a Live installer > drive but is not needed on a Persistent utility drive. > > The only alternative I see is to use a Full install USB drive were > automatic disk checking is not run. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: ubuntu-release-upgrader-core 1:20.04.18 > ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 > Uname: Linux 5.4.0-26-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu27 > Architecture: amd64 > CasperMD5CheckResult: skip > CasperVersion: 1.445 > CrashDB: ubuntu > CurrentDesktop: ubuntu:GNOME > Date: Tue Apr 28 06:07:32 2020 > LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) > PackageArchitecture: all > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=C.UTF-8 >SHELL=/bin/bash > SourcePackage: ubuntu-release-upgrader > Symptom: dist-upgrade > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875548 Title: Its not easy to determine how to skip the filesystem check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886148] Re: failure to boot groovy daily
@sudodus *-display description: VGA compatible controller product: Iris Pro Graphics 6200 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 0a width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:33 memory:f600-f6ff memory:e000-efff ioport:f000(size=64) memory:c-d -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886148 Title: failure to boot groovy daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886148] Re: failure to boot groovy daily
@Sudodus Hardinfo follows Computer: Gigabyte GB-BXi7-5775R Processor : Intel(R) Core(TM) i7-5775R CPU @ 3.30GHz Memory : 7959MB (1088MB used) Machine Type: Desktop Operating System: Ubuntu 20.04 LTS User Name : cscameron (cscameron) Date/Time : Sat 26 Sep 2020 11:20:29 AM -Display- Resolution : 1920x1080 pixels OpenGL Renderer : Mesa Intel(R) Iris(R) Pro Graphics 6200 (BDW GT3) X11 Vendor : The X.Org Foundation -Audio Devices- Audio Adapter : HDA-Intel - HDA Intel HDMI Audio Adapter : HDA-Intel - HDA Intel PCH -Input Devices- Sleep Button Power Button Power Button Microsoft Microsoft® 2.4GHz Transceiver v8.0 Microsoft Microsoft® 2.4GHz Transceiver v8.0 Mouse Microsoft Microsoft® 2.4GHz Transceiver v8.0 Consumer Control Microsoft Microsoft® 2.4GHz Transceiver v8.0 Consumer Control Microsoft Microsoft® 2.4GHz Transceiver v8.0 System Control SIGMACHIP USB Keyboard SIGMACHIP USB Keyboard Consumer Control SIGMACHIP USB Keyboard System Control Video Bus HDA Intel HDMI HDMI/DP,pcm:3 HDA Intel HDMI HDMI/DP,pcm:7 HDA Intel HDMI HDMI/DP,pcm:8 HDA Intel HDMI HDMI/DP,pcm:9 HDA Intel HDMI HDMI/DP,pcm:10 HDA Intel PCH Front Headphone -Printers- No printers found -SCSI Disks- ATA TOSHIBA MQ01ABD1 ATA RD-S350MCN-N1283 SanDisk Ultra Fit -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886148 Title: failure to boot groovy daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895329] Re: when booting cloned live drive 3rd partition is created without file system
Oops, I dont think F6 and persistent during boot works with 20.10. I think I meant pressing "e" and typing persistence, sorry. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895329 Title: when booting cloned live drive 3rd partition is created without file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1895329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895329] Re: when booting cloned live drive 3rd partition is created without file system
Used "sudo mkfs.ext4 -L writable /dev/sdx3" And partition sdx3 became persistent after using F6 and persistent during boot. Being able to make the spare space useful between Ubuntu and Windows for data is still a big deal for me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895329 Title: when booting cloned live drive 3rd partition is created without file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1895329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895329] Re: when booting cloned live drive 3rd partition is created without file system
Using sudo mkfs.ntfs -f -L data /dev/sdx3 and sudo mkfs.vfat -n data /dev/sdx3 I can format the third partition. It is then accessible in Disks but it is not accessible in Windows. With 20.04 the third partition was accessible in Windows after such formatting. I have not tested if It can be formatted ext4 an labeled "writable yet. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895329 Title: when booting cloned live drive 3rd partition is created without file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1895329/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886148] Re: failure to boot groovy daily
Creating a Live Only USB using 20.10 20200924 and 12.9.3 ave similar results to the Persistent install. Worked fine in BIOS mode. Gave initramfs unpacking error in UEFI mode plain persistent boot. Gave initramfs unpacking error in UEFI mode persistent boot with nomodeset edit, but quickly continued booting to desktop. Safe Graphic Mode boot also had initramfs unpacking error in UEFI mode but continued on to Language screen and beyond. This is similar to my experience trying to boot ISO files directly, but I only recall the unpacking error that continued to boot with the Live only USB. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886148 Title: failure to boot groovy daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886148] Re: failure to boot groovy daily
Everything "Plain Persistent boot ended in initramfs unpacking error". and after were in UEFI mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886148 Title: failure to boot groovy daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886148] Re: failure to boot groovy daily
@sudodus: I made a persistent 20.10 USB using 12.6.3 unstable. Persistent boot in BIOS mode worked okay with a distorted desktop. Plain Persistent boot ended in initramfs unpacking error. Safe Mode boot menu option worked with resume option. Persistent boot edited adding nomodeset to the linux line eventually worked okay with a distorted desktop. Boot process took over five minutes. I will try a clone using mkusb, My guess is that nomodeset will work okay here also. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886148 Title: failure to boot groovy daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1886148] Re: failure to boot groovy daily
Booting ISO Files using GRUB 2 I believe another concern of this Bug is the booting of Groovy ISO files directly using GRUB 2. Programs that use this method include Ventoy. YUMI and MultiBootUSB. I mostly use a BIOS-UEFI Template image developed by sudodus, see: https://askubuntu.com/questions/1269462/bios-uefi-template-image-for- booting-iso-files BIOS mode booting of ISO files now appears to work okay with the latest Groovy Daily ISO. The only way I have been able to get UEFI mode booting to work is by using "nomodeset" which results in a distorted desktop. This also works for Ventoy, however YUMI BIOS/GRUB and MultiBootUSB are not yet working with 20.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1886148 Title: failure to boot groovy daily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-cdimage/+bug/1886148/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1895131] Re: Groovy Desktop *BREAKS* the most common method of creating UEFI bootable drives for Ubuntu installation
I have been trying to boot the latest Groovy daily by loop mounting the ISO file. It works in BIOS mode but not in UEFI mode. This is worse than the problems with GRUB 2.04. I am wondering if this is related to Bug https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1892754 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1895131 Title: Groovy Desktop *BREAKS* the most common method of creating UEFI bootable drives for Ubuntu installation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1895131/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875548] Re: Its not easy to determine how to skip the filesystem check
Oops, casper - 1.334 was for 18.04. With 20.02 I get: "casper is already the newest version (1.445)". Hopefully 1.447 will be working with 20.04 soon, this is the version the bug is written about. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875548 Title: Its not easy to determine how to skip the filesystem check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875548] Re: Its not easy to determine how to skip the filesystem check
I ran: sudo apt-get update sudo apt-get install -y casper And got, "casper is already the newest version (1.334)". Am I doing something wrong? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875548 Title: Its not easy to determine how to skip the filesystem check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
Oops!
It looks like my "{FAILED} Failed to start Login Service..." was due to
snaps eating up all my casper-rw memory.
The ISO persistent USB is booting without error as long as "rmmod tpm"
is anywhere above the menuentry when booting either BIOS or UEFI.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
loopback command hangs in 2.04 under UEFI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
I notice that with BIOS mode booting, that if rmmod tpm is put in the
body of the menuentry, then there is the message "error: no such
module", and "Press any key to continue..."
If it is put anywhere above fi the computer boots without an error
message.
If it is put anywhere above the menuentry and below fi, we get scrolling
"{FAILED} Failed to start Login Service...", etc. (but I have not tried
indenting in these locations.
Booting in UEFI mode it seems that anywhere that "rmmod tpm" works in
BIOS mode, works for UEFI also.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
loopback command hangs in 2.04 under UEFI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
if loadfont /boot/grub/font.pf2 ; then
set gfxmode=auto
insmod efi_gop
insmod efi_uga
insmod gfxterm
terminal_output gfxterm
rmmod tpm
fi
set menu_color_normal=white/black
set menu_color_highlight=black/light-gray
set timeout=5
menuentry "ubuntu-20.04 ISO" {
set root=(hd0,3)
set isofile="/ubuntu-20.04-desktop-amd64.iso"
loopback loop $isofile
linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile
fsck.mode=skip persistent persistent-path=/ubuntu-20.04/ splash --
initrd (loop)/casper/initrd
}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
loopback command hangs in 2.04 under UEFI
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
On a previous post I mentioned that I put `rmmod tpm` on it's own line in grub.cfg menuentry, above the "loopback loop $isofile" line and that I got "error: no such module" when booting in BIOS mode. I have discovered, (after testing the latest mkusb - unstable), that putting `rmmod tpm` up top just above the fi line allows booting ISO's in UEFI mode without getting the no such module error when booting in BIOS mode. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: loopback command hangs in 2.04 under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877222] Re: Casper-rw Persistence files not working with 20.04
@Adam W https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877222 Title: Casper-rw Persistence files not working with 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1877222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
Separate bug report at https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1877222 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: loopback command hangs in 2.04 under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
It appears that the reason casper-rw persistent files are not working for me is that their name has been changed in Ubuntu 20.04 to "writable" -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: loopback command hangs in 2.04 under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877222] Re: Casper-rw Persistence files not working with 20.04
The persistent file/partition name in Ubuntu 20.04 has been officially changed from casper-rw to writable. On my computer a persistent partition can be named either casper-rw or writable and it will still work. However a persistent file must now be named writable. One Live USB expert compared this to America changing the name of the dollar to "valuable". -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877222 Title: Casper-rw Persistence files not working with 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1877222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1877222] [NEW] Casper-rw Persistence files not working with 20.04
Public bug reported: I have just noticed that casper-rw persistent files are not working with Ubuntu 20.04 when booted from an ISO file. Persistent partitions are working, however persistent partitions do not work with "persistent-path" and only one persistent partition is allowed per USB disk. This means that a multiboot, multipersistence USB drive is no longer possible using ISO files. Hopefully someone will point out that I am making an error somewhere. I have also just tested BIOS boot of a Persistent UNetbootin USB drive and there is no persistence. ** Affects: grub2 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877222 Title: Casper-rw Persistence files not working with 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1877222/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
It appears that Persistent casper-rw files are not just working with GRUB booted ISO files in BIOS mode, they do not seem to be working with Syslinux boot drives either. I have just tested BIOS boot of a Persistent UNetbootin USB drive and there is no persistence. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: loopback command hangs in 2.04 under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
I have just noticed that casper-rw persistent files are not working with Ubuntu 20.04 when booted from an ISO file. Persistent partitions are working, however persistent partitions do not work with persistent-path and only one persistent partition is allowed per USB disk. This means that a multiboot, multipersistence USB drive is no longer possible using ISO files. Hopefully someone will point out that I am making an error somewhere. I will fill out a separate bug report when I get time. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: loopback command hangs in 2.04 under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: loopback command hangs in 2.04 under UEFI
@alkisg Thank you for the workaround, easier that installing grub 2.02 via mkusb. I put `rmmod tpm` on it's own line in grub.cfg, above the "loopback loop $isofile" line. Booting BIOS mode grub 2.02 I get "error: no such module" and then after a bit it boots okay. Booting UEFI mode grub 2.04 it boots with no error messages. Both modes go to Disk Check. Neither mode goes to the Try/Install screen when booting, nor to remove drive and press enter when quitting. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: loopback command hangs in 2.04 under UEFI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875548] Re: Its not easy to determine how to skip the filesystem check
The line "Checking disks: 0% complete" still comes up but **fsck** does not run, and boot time is not increased, very good. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875548 Title: Its not easy to determine how to skip the filesystem check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1875548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1875548] [NEW] Live USB disk check
Public bug reported: I see that Live Ubuntu 20.04 is plagued by disk checking on boot. Not just with Live USB but with Persistent USB also. If not fast enough to cancel with ctl-c it starts on filesystem.squashfs and runs until over 90% complete. Very irritating. There have been quite a few complaints on Ask Ubuntu already. If it was just a run once it would not be so bad. Is there some way to get rid of this or is it a bug we have to live with? Perusing Ask Ubuntu everyday for many years I have never seen anybody ask for such a feature. A run once filesystem check might have its uses on a Live installer drive but is not needed on a Persistent utility drive. The only alternative I see is to use a Full install USB drive were automatic disk checking is not run. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.18 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CasperVersion: 1.445 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 06:07:32 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-release-upgrader (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1875548 Title: Live USB disk check To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1875548/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863672] Re: The 'new' persistent live method starting in 19.10 no longer works
@sudodus: 20.04 is the first Ubuntu version to have "maybe-ubiquity" in grub.cfg. previously Ubuntu's grub had an "Install Ubuntu" menuentry option. >From Ubuntu 19.10: linux /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed only-ubiquity quiet splash --- This would make the Try/Install screen redundant. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863672 Title: The 'new' persistent live method starting in 19.10 no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863672] Re: The 'new' persistent live method starting in 19.10 no longer works
Best I think if the Disk check only ran once on the first boot of a new Live or Persistent USB drive and then vanished forever. Is there really any need for it to run every boot?. It also seems that the Try Ubuntu / Install Ubuntu screen is back with a vengeance. It disappeared from persistent drives for a while, but I see it has returned to Rufus and mkusb persistent USB drives. It is easy to get rid of in Rufus, by overwriting syslinux.cfg, but I have not been able to disable it in mkusb. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863672 Title: The 'new' persistent live method starting in 19.10 no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489855] Re: Change to mount sequence order breaks persistence on casper-rw partitions
So is there still a bug with 20.04 as you suggest? If the bug was only squashed with 19.10 are you going to give up on persistence for Rufus and just wait for the bug to get fixed? Perhaps another five years. Seems better to me to work with what we have rather that wait for a perfect world. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1489855 Title: Change to mount sequence order breaks persistence on casper-rw partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489855] Re: Change to mount sequence order breaks persistence on casper-rw partitions
Making a Grub2 booter that uses Persistent partitions is not a problem. Start with a 1MB grub2 core.img partition flagged bios_grub. Add a 250MB FAT32 EFI partition flagged boot,esp. next add an ext4 partition large enough for the Ubuntu ISO's contents and finish with a ext4 casper-rw partition and a NTFS data partition if desired. Copy the ISO's contents to the root partition and recopy boot and EFI folders to to the EFI partition. Mount the EFI partition to mnt and Install grub. Add set root=(hd0,3) to grub.cfg. Add " persistent" after ---. I think Grub2 does not like a FAT32 root. I believe the above works on all versions of Ubuntu since 12.04. Bootloading is based on mkusb by Sudodus. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1489855 Title: Change to mount sequence order breaks persistence on casper-rw partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1489855] Re: Change to mount sequence order breaks persistence on casper-rw partitions
I added a persistent partition to a UNetbootin focal-desktop- amd64-20200325 install and it works okay. Just like pre-14.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1489855 Title: Change to mount sequence order breaks persistence on casper-rw partitions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1489855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863672] Re: The 'new' persistent live method starting in 19.10 no longer works
For those who have dad a problem with scrolling when shutting down, I noticed that pressing enter shuts things down. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863672 Title: The 'new' persistent live method starting in 19.10 no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863672] Re: The 'new' persistent live method starting in 19.10 no longer works
Sort of like asking the British to change the name of the pound to dollar. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863672 Title: The 'new' persistent live method starting in 19.10 no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863672] Re: The 'new' persistent live method starting in 19.10 no longer works
Ubuntu has been using casper-rw and home-rw ever since it was changed from casper-cow back around 7.04. If it ain't broke, don't fix it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863672 Title: The 'new' persistent live method starting in 19.10 no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863672] Re: The 'new' persistent live method starting in 19.10 no longer works
The persistent file/partition names casper-rw and home-rw should be retained. However home-rw partitions still work when the other persistent file/partition is named writable. It is nice having the option for a home-rw file/partition. It is interchangeable with /home partition in a Full install and can be copied back and forth, if having duplicate homes in the desktop and Persistent thumb drive is desired.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863672 Title: The 'new' persistent live method starting in 19.10 no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863672] Re: The 'new' persistent live method starting in 19.10 no longer works
@Akeo Not sure renaming the persistent partitions to persistent works. There are two kinds of persistent file or partition in Ubuntu. casper-rw is the catch all and takes new programs, data and settings, when there is no home-rw persistent partition. When there is a home-rw partition, home-rw takes the user data and settings like /home does in a full install. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863672 Title: The 'new' persistent live method starting in 19.10 no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863672] Re: The 'new' persistent live method starting in 19.10 no longer works
I agree with Sudodus, when I started using Ubuntu the persistent partition was labeled casper-cow. I have finally gotten used to casper-rw. Why change it to writable, It seems to be identical to casper-rw and works the same way with home-rw. Are we going to change the name of home-rw to settingable? If it ain't broke, don't fix it. Best regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863672 Title: The 'new' persistent live method starting in 19.10 no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863672] Re: The 'new' persistent live method starting in 19.10 no longer works
Tried mkusb persistent using focal-desktop-amd64 20200223, changing partition label from "casper-rw" to "writable". This time it worked, Now have persistent partition labeled writable. Home stuff and installed programs are persistent. Create an additional partition labeled home-rw, home stuff went there while downloaded programs went to writable similar to having casper-rw + home-rw partitions. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863672 Title: The 'new' persistent live method starting in 19.10 no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1863672] Re: The 'new' persistent live method starting in 19.10 no longer works
Made a Live drive using balenaEtcher. Changed the label on focal-desktop-amd64 20200223 writable partition to home-rw, resulted in a partition that was persistent for home stuff, wallpaper, etc, but not for new installed programs, as would be expected for a home-rw partition. Made a persistent Focal drive using mkusb. Relabeled the "casper-rw" partition to "writable". Persistence did not work. The writable label only seems to work for persistence with Live USB. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1863672 Title: The 'new' persistent live method starting in 19.10 no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1863672/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
Have a look in casper on the xubuntu ISO. Confirm your menuentry uses the same as ISO: vmlinuz or vmlinuz.efi initrd or initrd.lz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
Simple ISO Booter using mkusb. https://askubuntu.com/questions/1075755/create-bootable-ubuntu-usb-on-a -partition-instead-of-overwriting-the-entire-usb/1080749#1080749 When setting up mkusb select "usb-pack-efi" per post #18 above. It should insure the use of grub 2.02. More Complex ISO Booter using mkusb If you wish to add up to 8GB of persistence to each ISO using casper-rw and home-rw files with persistent-path see: https://askubuntu.com/questions/1183191/handmade-live-usb- multisystem/1184111 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
@Pino:
Sudodus fix worked for me.
See posts 17 to 21 for workaround.
If you want instructions turning mkusb into an ISO booter let me know.
On Thu, Dec 26, 2019 at 3:00 PM pino <1851...@bugs.launchpad.net> wrote:
> Isn't there at least some workaround, e.g. downgrading grub? I urgently
> need to work around it somehow. If it isn't at least possible to get
> such things fixed early, Ubuntu is maybe the wrong distribution for real
> usage...
>
> What additional information do you need? I can even reproduce it easily
> in my VMs...
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1851311
>
> Title:
> Grub 2.04 Out of memory error, No server error
>
> Status in grub2 package in Ubuntu:
> Confirmed
>
> Bug description:
> Trying to loop mount ISO.
>
> Installed grub 2.04 to flash drive in UEFI mode from 19.10
> Flash drive does not boot and gives Out of memory error & no server
> error. Must load kernel first.
>
> Re-installed grub from 18.04 to same flash drive using same boot stanza.
> Booted without issue.
>
> From 18.04
> fred@Bionic-Z170N:~$ grub-install -V
> grub-install (GRUB) 2.02-2ubuntu8.13
>
> from 19.10
> fred@fred-Z170N-eoan:~$ grub-install -V
> grub-install (GRUB) 2.04-1ubuntu12
>
> Boot stanza that works in 2.02 but not in 2.04
>
> menuentry "Focal Live ISO" {
> set isofile="/ISO/focal-desktop-amd64.iso"
> loopback loop (hd0,1)$isofile
> linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile
> toram noeject
> initrd (loop)/casper/initrd
> }
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
Grub 2.04 Out of memory error, No server error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
@tsger: You did not mention if you are booting in BIOS or UEFI mode. I have only had problem when using both UEFI and Grub 2.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
@sudodus:
Made a persistent 4GB flash drive using mkusb menu item usb-pack-efi with
19.10.
Used this drive to make a second 4GB flash drive using mkusb menu item
usb-pack-efi with 19.10.
(Just to make sure grub 2.02 had no way to sneak in).
Deleted ISO9660 partiton #4, stretched Casper-rw partition #5 into place
and expanded usbdata NTFS partition #1.
Dropped 19.10 ISO into iso folder on NTFS partition.
Updated grub.cfg on usbboot partition #2 to loopmount the 19.10 ISO.
Booted in BIOS using grub 2.04
Booted in UEFI using grub 2.02~Beta2
This solution works for me. I am impressed.
Is there way to retro fit this to a working system so sundar-ima can use it
to boot ISOs from his internal dive? I wonder how Qemu is doing with this
bug?
Mkusb would work fine for setting up a small SSD, as either Full or
Persistent install for booting ISOs, but my SSD booting option seems to be
missing?
On Sun, Nov 17, 2019 at 11:30 PM sudodus <1851...@bugs.launchpad.net>
wrote:
> @ C.S.Cameron,
>
> Yes, I think it is enough with a single test. Please tell us the result
> of your test when usb-pack-efi is selected in the settings menu of
> mkusb. Will it make a difference in order to make it possible to boot
> into an iso file?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1851311
>
> Title:
> Grub 2.04 Out of memory error, No server error
>
> Status in grub2 package in Ubuntu:
> Confirmed
>
> Bug description:
> Trying to loop mount ISO.
>
> Installed grub 2.04 to flash drive in UEFI mode from 19.10
> Flash drive does not boot and gives Out of memory error & no server
> error. Must load kernel first.
>
> Re-installed grub from 18.04 to same flash drive using same boot stanza.
> Booted without issue.
>
> From 18.04
> fred@Bionic-Z170N:~$ grub-install -V
> grub-install (GRUB) 2.02-2ubuntu8.13
>
> from 19.10
> fred@fred-Z170N-eoan:~$ grub-install -V
> grub-install (GRUB) 2.04-1ubuntu12
>
> Boot stanza that works in 2.02 but not in 2.04
>
> menuentry "Focal Live ISO" {
> set isofile="/ISO/focal-desktop-amd64.iso"
> loopback loop (hd0,1)$isofile
> linux (loop)/casper/vmlinuz boot=casper iso-scan/filename=$isofile
> toram noeject
> initrd (loop)/casper/initrd
> }
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1851311
Title:
Grub 2.04 Out of memory error, No server error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
@sudodus, I tried a fresh install or two yesterday, I ran sudo apt-get install usb-pack-efi(# for persistent live drives that work in UEFI and BIOS mode with 32-bit iso files). when installing. Is that enough? Will try again today. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
Oops, After a little more experimenting, it appears that it is the version of Ubuntu that mkusb uses to create the persistent drive that determines the version of grub, not the version of Ubuntu mkusb is installed in. I guess that this should have been obvious. I created an ISO booter foundation using mkusb installed in 18.04 using a 19.10 ISO. I added both 18.04 and 19.10 ISOs to the ISO folder on the usbdata NTFS partition. Both had problems booting in UEFI as mentioned above, they uses grub 2.04 I then created another ISO booter foundation using mkusb installed in 19.10 using a 18.04 ISO. I added both 18.04 and 19.10 ISOs to the ISO folder. Both booted fine in UEFI mode, they used grub 2.02. I will try duplicate my findings tomorrow. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
To clarify, if I install mkusb in 18.04 the USBs it makes boot with grub 2.02. If I install mkusb in 19.10 the USBs it makes boot with grub 2.04. Grub 2.02 boots ISOs, grub 2.04 does not boot ISOs. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
But only when mkusb is installed in Ubuntu 19.10 or later, ie grub 2.04 the ISOs don't boot. When mkusb is installed in 18.04, grub 2.02, the ISOs on the USBs it makes boot fine. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
Workaround I used mkusb installed in 18.04, (grub 2.02), to make the foundation of an ISO booter. ISO's in an ISO folder on usbdata partition, with casper-rw partition for persistence, (one distro only). Usbboot partition has loop mounting grub.cfg. Boots 18.04 and 19.10, both UEFI and BIOS, (I got a new power brick for my UEFI computer). UEFI boot fails using mkusb installed in 19.10, (grub 2.04). whether 18.04 or 19.10. I think the problem is grub 2.04 myself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
One reason I did not have problems booting a 19.10 ISO was because I used mkusb installed in 18.04 to create the foundation for the boot disk. This used grub 2.02 to boot 19.10. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851123] Re: Ubuntu 19.10 and focal live cloned create and mount casper-rw partition
Been chatting with Sudodus. Back in the days of 4GB and 8GB flash drives it was not so bad when SDC, mkusb and Rufus used the whole drive to make a Live USB. Nowadays with 64GB and larger flash drives it seems like a waste. Making the remaining space Persistent is a great start but even on my desktop, my /home partition is only about 30GB. Any chance using some of this excess persistence space as NTFS so the drive could be used for data both by Windows and Linux? Sorta like mkusb does with Persistent drives. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851123 Title: Ubuntu 19.10 and focal live cloned create and mount casper-rw partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1851123] Re: Ubuntu 19.10 and focal live cloned create and mount casper-rw partition
I tried booting a Startup Disk Creator 19.10 flashdrive with F6. I typed a space and then "persistent". The drive booted persistent and stayed persistent every time I used this procedure, otherwise it just booted Live. I then tried F6 with the word "toram", it booted to RAM. Then with "nomodeset" and combinations of these and they all worked. Finally I tried F6 and "nopersistent". I was able to unmount the casper-rw partition using Disks. I tried formatting it FAT and NTFS but that did not work. Finally I was able to wipe the partition using Disks and it just went back to ISO9660 space. I lost everything that was in casper-rw, but it was all in the name of research. On Fri, Nov 8, 2019 at 9:20 PM sudodus <1851...@bugs.launchpad.net> wrote: > Exploring the boot option 'nopersistent': > > The bug is there, but there is a workaround: add the boot option > 'nopersistent'. This means that with 'nopersistent' and 'toram' all > partitions on the boot drive can be unmounted and the drive can be > unplugged or the casper-rw partition can be repaired or backed up > without problems. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1851123 > > Title: > Ubuntu 19.10 and focal live cloned create and mount casper-rw > partition > > Status in casper package in Ubuntu: > Confirmed > > Bug description: > It is very good that it is easy to create and use a casper-rw > partition to run Ubuntu persistent live in the versions 19.10 and > Focal Fossa, and that it is even created automatically, when there is > unallocated drive space behind the used part in a live drive. > > But I think the system for doing that is 'too eager'. Maybe it is a > feature that is left from the development and debugging phase. > > - It would be enough (best), if the casper-rw partition is created > only when it is needed, that is when the live system is booted with > the boot option 'persistent'. > > - We (I am talking for users who like persistent live drives) can > accept that the casper-rw partition is created even when the drive is > booted live only (without the boot option 'persistent'). > > - But we think it is a bug, that the live-only system is also mounting > the casper-rw partition on the mount point /var/log and/or /var/crash > and keeps it busy so that it cannot be unmounted. > > This way the drive is not really live-only, and it is not possible to > manage the drive space behind the system in an independent way. For > example, it is not possible to detach the drive by using the boot > option 'toram', and it is not possible to repair the casper-rw > partition when running live in the same drive. It will be necessary to > have two linux systems to do such tasks. > > ProblemType: Bug > DistroRelease: Ubuntu 20.04 > Package: casper 1.428 > ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 > Uname: Linux 5.3.0-18-generic x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > ApportVersion: 2.20.11-0ubuntu9 > Architecture: amd64 > CasperVersion: 1.428 > CurrentDesktop: ubuntu:GNOME > Date: Sun Nov 3 11:15:29 2019 > LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191103) > ProcEnviron: >TERM=xterm-256color >PATH=(custom, no user) >XDG_RUNTIME_DIR= >LANG=sv_SE.UTF-8 >SHELL=/bin/bash > SourcePackage: casper > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851123 Title: Ubuntu 19.10 and focal live cloned create and mount casper-rw partition To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1851123/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1851311] Re: Grub 2.04 Out of memory error, No server error
I have not had problem Booting ISO files in BIOS mode in 19.10. When booting my grub menu shows grub 2.02 at the top. When I tried upgrading grub it tells me grub 2.04 is already installed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1851311 Title: Grub 2.04 Out of memory error, No server error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1851311/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1619188] Re: Unattended upgrades can break persistent live media
I will be watching for your results, I have not been able to get persistent partitions working with 64bit 16.04 using UNetbootin or SDC. Drive fails to boot similar to having a full casper-rw. On Wed, Oct 26, 2016 at 10:16 AM, sudodus <1619...@bugs.launchpad.net> wrote: > Even if it works for you with a live seesion, it does not work for me > with a persistent live session using a casper-rw partition. starting > from the Ubuntu 16.04.1 LTS iso file. I don't think mkusb has anything > at all to to with this functionality because it does not touch the > mechanism (unless you tell it to do it, and then it will prevent > unattended upgrades). > > mkusb has a work-around feature, and I think all other tools and manual > methods, that create persistent live drives will need some work-around > to avoid this problem. For example, if you create a cloned system with > the Ubuntu Startup Disk Creator, the cloned result will be exactly like > cloning with mkusb. It is possible in such cases to create persistence > by using a casper-rw partition (or file) in another drive. I will test > tonight, if such a system is also vulnerable to this bug. > > I plan to start the test from the Ubuntu 16.04.1 LTS desktop amd64 iso > file. I intend to upgrade casper, but no other program package unless > you advice what must also be upgraded for your fix to work. > > But don't tell me that I must try with the current daily iso file, > because then I would have to test for a very long period of time for > something to happen. In that case (if you know things have changed to > the better, but don't know which program packages are involved) maybe I > should zsync today's daily iso file and keep it for some weeks before I > start it and let it run for at least 24 hours. > > The important thing here is to get something working for the next point > release, 16.04.2 LTS, so I think it should be tested thoroughly. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1619188 > > Title: > Unattended upgrades can break persistent live media > > Status in casper package in Ubuntu: > Fix Released > Status in casper source package in Xenial: > Fix Committed > Status in casper source package in Yakkety: > Fix Released > > Bug description: > Test Case > - > 1) Boot an Ubuntu 16.04 Live CD > 2) Choose Try Ubuntu > 3) head -n5 /etc/apt/apt.conf.d/50unattended-upgrades > 4) Observe -security is enabled in line 3. (// is a comment) > 5) Run /usr/lib/apt/apt.systemd.daily > 6) Observe your Live environment run out of space! (I received a pop-up > re lack of free space and > /var/log/unattended-upgrades/unattended-upgrades-dpkg.log > contained an error installing a package due to disk full.) > > With the version of the package in -proposed step 4 will reveal the > -security pocket being disabled and step 6 won't fill your live > environment. > > Regression Potential > > Persistent live users will not receive updates from -security, but that > seems less bad than destroying people's live environment by filling up > their disk. > > Original Bug Description > > Looking at the persistent live Ubuntu 16.04 LTS system - the Software & > Updates screen / Update - I notice, that Automatic updates is set to > 'Download and install automatically'. This is bad in a persistent live > system. > > After leaving the persistent live Ubuntu 16.04 LTS system running > overnight, I found that it had performed an automatic upgrade: > > df revealed that the content in casper-rw had increased to 1.6 GiB. > > It was a surprise that the persistent live system started an automatic > upgrade. This is not caused by the installer (mkusb), because the > files controlling those actions are not touched. Instead it is caused > by a change of the default action, when there are security updates. > And the survey indicates that this default setting is different > between the flavours and versions of Ubuntu. Lubuntu keeps the setting > 'Display immediately', while the other tested flavours change it from > 14.04 LTS to 16.04 LTS. > > Until this is resolved, it is a good idea to disable unattended- > upgrades manually, but above all, to take regular backups, when you > use a persistent live system. > > The survey is described in this link to the Ubuntu Forums: > > https://ubuntuforums.org/showthread.php?t=2335669= > 13538805#post13538805 > > and it contains some screenshots illustrating the settings manager for > automatic updates for different versions and flavours of Ubuntu. > > -o- > > There are various scripts in the casper package that change things to > be more appropriate for the live environment. I suggest to change the > default for security updates to 'Display immediately', when the system > is running live and persistent live. > > See also this link to Ask
[Bug 278361] From: Courtley Cameron
Hi http://ruanlife.com/ever.php?huge=eqyyfs3635xcppc Courtley Cameron -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/278361 Title: Persistence install stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/278361/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 276822] Re: busybox with (initramfs) / boot: / kernel not found
Daily-build of April 20th 2009 worked without incident for me also. -- busybox with (initramfs) / boot: / kernel not found https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 287228] Re: installer does not see second flash drive if plugged in after boot
This is quite old. I recall that, (after fixing the formatting on my 8G Kingston), everything worked fine. Have been using an U-C install for the last month as my main O/S. The only thing that I find missing is a method to boot my dual monitor Nvidia desktop then switch to ATI drivers for my ATI laptop. (I think switchconf is crippled in 8.10 anyway). On Tue, Nov 25, 2008 at 10:18 AM, Evan Dandrea [EMAIL PROTECTED] wrote: Moving to partman-base for lack of a better place given the uncertain nature of the bug. ** Changed in: usb-creator (Ubuntu) Status: New = Invalid ** Changed in: partman-base (Ubuntu) Status: New = Incomplete -- installer does not see second flash drive if plugged in after boot https://bugs.launchpad.net/bugs/287228 You received this bug notification because you are a direct subscriber of the bug. Status in partman-base source package in Ubuntu: Incomplete Status in usb-creator source package in Ubuntu: Invalid Bug description: Binary package hint: usb-creator Using latest usb-creator and 8.10 Daily I installed full Ubuntu to second flash drive. Installer did not see second flash drive when plugged in after system has booted. It sees the second flash drive ok if it is plugged in at the first menu, (Language). It installs to second drive fine. -- installer does not see second flash drive if plugged in after boot https://bugs.launchpad.net/bugs/287228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 298091] Re: create a usb startup disk does not work with 8.04.1
*** This bug is a duplicate of bug 276822 *** https://bugs.launchpad.net/bugs/276822 8.04.1 Is a hassle to make persistent because of the casper file. I was concerned at first, but after using Ubuntu 8.10 on a 8 GB stick for a while I found other uses for my flash drives with Ubuntu and Xubuntu 8.04.1 installs On Fri, Nov 21, 2008 at 4:54 PM, Bryan Quigley [EMAIL PROTECTED] wrote: *** This bug is a duplicate of bug 276822 *** https://bugs.launchpad.net/bugs/276822 ** This bug has been marked a duplicate of bug 276822 busybox with (initramfs) -- create a usb startup disk does not work with 8.04.1 https://bugs.launchpad.net/bugs/298091 You received this bug notification because you are a direct subscriber of the bug (via bug 276822). Status in usb-creator source package in Ubuntu: Incomplete Bug description: When I use the new option create a usb startup disk on the System menu it will not work with either a 8.04.1.iso or 8.04.1 disk. It looks like it runs well, but then when I try to boot into the Ubuntu on the USB drive I just get a BusyBox shell. This is very important to me as I need to install 8.04 on my wifes computer or it is a very expensive paperweight. -- create a usb startup disk does not work with 8.04.1 https://bugs.launchpad.net/bugs/298091 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 295025] Re: Could not find kernel image
*** This bug is a duplicate of bug 276822 *** https://bugs.launchpad.net/bugs/276822 I have had similar problems installing to a 8 GB Kingston Traveller. Usb-creator would not install to it out of the wrapper. Nor after reformatting to fat 32 in gparted and Windows or after letting U-C format from unallocated space. What worked was using UNetbootin to install 8.10, deleting the files, then using U-C. I created a couple ext3 partitions and labeled them casper-rw and home-rw. It's been my primary Ubuntu machine for almost a month. On Fri, Nov 21, 2008 at 5:02 PM, Bryan Quigley [EMAIL PROTECTED] wrote: *** This bug is a duplicate of bug 276822 *** https://bugs.launchpad.net/bugs/276822 ** This bug has been marked a duplicate of bug 276822 busybox with (initramfs) -- Could not find kernel image https://bugs.launchpad.net/bugs/295025 You received this bug notification because you are a direct subscriber of the bug (via bug 276822). Status in usb-creator source package in Ubuntu: New Bug description: Binary package hint: usb-creator hi first thanks for the tool. I have try to make a usb boot stick from a 8.10 ubuntu system (i386 HP laptop) using a 8.10 i386 iso and creating a 1gb casper-rw on a 8gb sandisk cruzer micro usb stick (stick is new out of the box) if i boot it i became the could not find kernel image error i search with google but i dont find a working solution to fix it. thanks for your help update fdisk : disk /dev/sdb: 8086 MByte, 8086617600 Byte 255 Heads, 63 Sectors / cycles , 983 Zylinder Einheiten = Zylinder von 16065 × 512 = 8225280 Bytes Disk identifier: 0x000d41d9 Gerät boot. beginEnd Blocks Id System /dev/sdb1 * 1 976 7839698b W95 FAT32 -- Could not find kernel image https://bugs.launchpad.net/bugs/295025 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 276822] Re: busybox with (initramfs)
Having some space left over from the 2G to 4G clone, I made two ext3 partitions and labeled one as casper-rw and the other as home-rw. I had to use gparted Live CD as partitioner in Ubuntu gave errors trying to label a partition as casper-rw. I deleted the casper file from the U-C installation. Everything seems to working ok now. On Tue, Oct 28, 2008 at 10:58 AM, Courtley Cameron [EMAIL PROTECTED]wrote: Installed today using usb-creator on 2G Kingston, works with persistence. Install to 4G Kingston gives grub_ Cloning 2G to 4G using sudo dd if=/dev/sdc of=/dev/sdd makes 4G Kingston bootable and persistent. On Mon, Oct 27, 2008 at 5:45 PM, Courtley Cameron [EMAIL PROTECTED]wrote: Trying to install Xubuntu 8.0.1 to 2G Kingston ends up at (initramfs)_. On Mon, Oct 27, 2008 at 4:56 PM, Courtley Cameron [EMAIL PROTECTED]wrote: A comment on upgrading Intrepid to the latest version, casper-rw seems to get filled up if this is done often, and then I get ownership errors trying to install any more applications. On Mon, Oct 27, 2008 at 4:35 PM, fjgold [EMAIL PROTECTED] wrote: Just got finished testing usb-creator 0.1.5 thru 0.1.9 in intrepid 64 bit RC. Successfully created bootable live USB drives with Dapper, Hardy 64 and Intrepid 64. Used raw .iso's in all tests. Drive used was a Sandisk 4 GB Titanium. Usb-creator versions 0.1.9 and 0.1.10 failed with the Busybox error. All versions were installed using .deb's. Have kept the 0.1.8 version installed. The only trouble is Intrepid keeps trying to update to the latest version. In all cases persistence doesn't work. -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Fix Released Bug description: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 276822] Re: busybox with (initramfs)
Sorry I meant to say I deleted the casper-rw file from the U-C installation. On Wed, Oct 29, 2008 at 11:30 AM, Courtley Cameron [EMAIL PROTECTED]wrote: Having some space left over from the 2G to 4G clone, I made two ext3 partitions and labeled one as casper-rw and the other as home-rw. I had to use gparted Live CD as partitioner in Ubuntu gave errors trying to label a partition as casper-rw. I deleted the casper file from the U-C installation. Everything seems to working ok now. On Tue, Oct 28, 2008 at 10:58 AM, Courtley Cameron [EMAIL PROTECTED]wrote: Installed today using usb-creator on 2G Kingston, works with persistence. Install to 4G Kingston gives grub_ Cloning 2G to 4G using sudo dd if=/dev/sdc of=/dev/sdd makes 4G Kingston bootable and persistent. On Mon, Oct 27, 2008 at 5:45 PM, Courtley Cameron [EMAIL PROTECTED]wrote: Trying to install Xubuntu 8.0.1 to 2G Kingston ends up at (initramfs)_. On Mon, Oct 27, 2008 at 4:56 PM, Courtley Cameron [EMAIL PROTECTED]wrote: A comment on upgrading Intrepid to the latest version, casper-rw seems to get filled up if this is done often, and then I get ownership errors trying to install any more applications. On Mon, Oct 27, 2008 at 4:35 PM, fjgold [EMAIL PROTECTED] wrote: Just got finished testing usb-creator 0.1.5 thru 0.1.9 in intrepid 64 bit RC. Successfully created bootable live USB drives with Dapper, Hardy 64 and Intrepid 64. Used raw .iso's in all tests. Drive used was a Sandisk 4 GB Titanium. Usb-creator versions 0.1.9 and 0.1.10 failed with the Busybox error. All versions were installed using .deb's. Have kept the 0.1.8 version installed. The only trouble is Intrepid keeps trying to update to the latest version. In all cases persistence doesn't work. -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Fix Released Bug description: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 278361] Re: Persistence install stopped working
Persistence has been working fine for me with the latest issues. Even works if caser-rw and home-rw are partitions on a separate flash drive. Seems to default to them first. On Wed, Oct 29, 2008 at 3:20 AM, Evan Dandrea [EMAIL PROTECTED] wrote: Marking as fixed, given the previous comments. ** Changed in: usb-creator (Ubuntu) Status: Incomplete = Fix Released -- Persistence install stopped working https://bugs.launchpad.net/bugs/278361 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Fix Released Bug description: Binary package hint: usb-creator Installed usb-creator a few days ago. installing 8.04 ubuntu and xubuntu both got busybox. installing 8.10 alpha 6 got persistence drive, but could not install 8.10 to other drive. installing 8.10 Beta worked well as persistence, used Live USB to install to other drive. This morning tried drive and got grub with blinking curser. Tried on second computer and got error also. Reinstalled usb-creator into both 8.04 and 8.10 beta systems. Tried several times building persistent drives using these using both iso and CD. Got same errors at boot. Installed 8.10 once more as non persistent, this is now working. -- Persistence install stopped working https://bugs.launchpad.net/bugs/278361 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 276822] Re: busybox with (initramfs)
Installed today using usb-creator on 2G Kingston, works with persistence. Install to 4G Kingston gives grub_ Cloning 2G to 4G using sudo dd if=/dev/sdc of=/dev/sdd makes 4G Kingston bootable and persistent. On Mon, Oct 27, 2008 at 5:45 PM, Courtley Cameron [EMAIL PROTECTED]wrote: Trying to install Xubuntu 8.0.1 to 2G Kingston ends up at (initramfs)_. On Mon, Oct 27, 2008 at 4:56 PM, Courtley Cameron [EMAIL PROTECTED]wrote: A comment on upgrading Intrepid to the latest version, casper-rw seems to get filled up if this is done often, and then I get ownership errors trying to install any more applications. On Mon, Oct 27, 2008 at 4:35 PM, fjgold [EMAIL PROTECTED] wrote: Just got finished testing usb-creator 0.1.5 thru 0.1.9 in intrepid 64 bit RC. Successfully created bootable live USB drives with Dapper, Hardy 64 and Intrepid 64. Used raw .iso's in all tests. Drive used was a Sandisk 4 GB Titanium. Usb-creator versions 0.1.9 and 0.1.10 failed with the Busybox error. All versions were installed using .deb's. Have kept the 0.1.8 version installed. The only trouble is Intrepid keeps trying to update to the latest version. In all cases persistence doesn't work. -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Fix Released Bug description: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 276822] Re: busybox with (initramfs)
With today's install of U-C I am only getting grub_ with my Kingston 4G. It is still installing ok to my 2G Kingston, Persistence seems to be working fine except for hardware drivers. On Mon, Oct 27, 2008 at 3:24 AM, Evan Dandrea [EMAIL PROTECTED] wrote: ** Changed in: usb-creator (Ubuntu) Status: Incomplete = Fix Released -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Fix Released Bug description: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 276822] Re: busybox with (initramfs)
A comment on upgrading Intrepid to the latest version, casper-rw seems to get filled up if this is done often, and then I get ownership errors trying to install any more applications. On Mon, Oct 27, 2008 at 4:35 PM, fjgold [EMAIL PROTECTED] wrote: Just got finished testing usb-creator 0.1.5 thru 0.1.9 in intrepid 64 bit RC. Successfully created bootable live USB drives with Dapper, Hardy 64 and Intrepid 64. Used raw .iso's in all tests. Drive used was a Sandisk 4 GB Titanium. Usb-creator versions 0.1.9 and 0.1.10 failed with the Busybox error. All versions were installed using .deb's. Have kept the 0.1.8 version installed. The only trouble is Intrepid keeps trying to update to the latest version. In all cases persistence doesn't work. -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Fix Released Bug description: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 276822] Re: busybox with (initramfs)
Trying to install Xubuntu 8.0.1 to 2G Kingston ends up at (initramfs)_. On Mon, Oct 27, 2008 at 4:56 PM, Courtley Cameron [EMAIL PROTECTED]wrote: A comment on upgrading Intrepid to the latest version, casper-rw seems to get filled up if this is done often, and then I get ownership errors trying to install any more applications. On Mon, Oct 27, 2008 at 4:35 PM, fjgold [EMAIL PROTECTED] wrote: Just got finished testing usb-creator 0.1.5 thru 0.1.9 in intrepid 64 bit RC. Successfully created bootable live USB drives with Dapper, Hardy 64 and Intrepid 64. Used raw .iso's in all tests. Drive used was a Sandisk 4 GB Titanium. Usb-creator versions 0.1.9 and 0.1.10 failed with the Busybox error. All versions were installed using .deb's. Have kept the 0.1.8 version installed. The only trouble is Intrepid keeps trying to update to the latest version. In all cases persistence doesn't work. -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Fix Released Bug description: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 276822] Re: busybox with (initramfs)
sorry, Xubuntu 8.04.1 On Mon, Oct 27, 2008 at 5:45 PM, Courtley Cameron [EMAIL PROTECTED]wrote: Trying to install Xubuntu 8.0.1 to 2G Kingston ends up at (initramfs)_. On Mon, Oct 27, 2008 at 4:56 PM, Courtley Cameron [EMAIL PROTECTED]wrote: A comment on upgrading Intrepid to the latest version, casper-rw seems to get filled up if this is done often, and then I get ownership errors trying to install any more applications. On Mon, Oct 27, 2008 at 4:35 PM, fjgold [EMAIL PROTECTED] wrote: Just got finished testing usb-creator 0.1.5 thru 0.1.9 in intrepid 64 bit RC. Successfully created bootable live USB drives with Dapper, Hardy 64 and Intrepid 64. Used raw .iso's in all tests. Drive used was a Sandisk 4 GB Titanium. Usb-creator versions 0.1.9 and 0.1.10 failed with the Busybox error. All versions were installed using .deb's. Have kept the 0.1.8 version installed. The only trouble is Intrepid keeps trying to update to the latest version. In all cases persistence doesn't work. -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Fix Released Bug description: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 276822] Re: busybox with (initramfs)
Yes, my problem is also with a Kingston 4G (purple) also. Have tried installing from the RC Live CD onto 2 different Kingston 4G, from 2 different computers today. Still getting Error 17. -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 276822] Re: busybox with (initramfs)
Well I installed several times yesterday to a 2G flash with success using U-C. Tried a dozen time to install to a 4G flash but only got error 17, have tried everything. On Mon, Oct 20, 2008 at 11:20 PM, Evan Dandrea [EMAIL PROTECTED] wrote: I believe this is fixed in the latest daily-live CDs. Can anyone that was seeing a busybox prompt, please try creating an image using one of the CDs found here: http://cdimage.ubuntu.com/daily-live/ Thanks! ** Changed in: usb-creator (Ubuntu) Importance: Undecided = High Status: New = Incomplete -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Incomplete Bug description: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 287684] [NEW] U-C installs from Live CD but not from Live USB
Public bug reported: Binary package hint: usb-creator Using the Live CD I can install directly to USB using usb-creator. Using the Live USB thus created, usb-creator requires the Live CD or an iso. It does not seem to recognize the USB as a source for the install. This is using the Daily for 081021. ** Affects: usb-creator (Ubuntu) Importance: Undecided Status: New -- U-C installs from Live CD but not from Live USB https://bugs.launchpad.net/bugs/287684 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 276822] Re: busybox with (initramfs)
Downloading now, will test when complete. On Mon, Oct 20, 2008 at 11:20 PM, Evan Dandrea [EMAIL PROTECTED] wrote: I believe this is fixed in the latest daily-live CDs. Can anyone that was seeing a busybox prompt, please try creating an image using one of the CDs found here: http://cdimage.ubuntu.com/daily-live/ Thanks! ** Changed in: usb-creator (Ubuntu) Importance: Undecided = High Status: New = Incomplete -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Incomplete Bug description: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 278361] Re: Persistence install stopped working
Rebuilt Flash using latest usb-creator and daily-live. Persistence seems to be working fine. Changed desktop background sticks as does network connection and install of AbiWord. Flash drive does not constantly blink as with persistent install of liveusb. Install stopped working after trying to start synaptic. Had a warning about root permissions. Will try again and report back. On Mon, Oct 20, 2008 at 11:52 PM, Evan Dandrea [EMAIL PROTECTED] wrote: Can you please check to see if persistence works with usb-creator 0.1.9 and the latest daily 8.10 Desktop CD, found here: http://cdimage.ubuntu.com/daily-live Thanks ** Changed in: usb-creator (Ubuntu) Status: Confirmed = Incomplete -- Persistence install stopped working https://bugs.launchpad.net/bugs/278361 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Incomplete Bug description: Binary package hint: usb-creator Installed usb-creator a few days ago. installing 8.04 ubuntu and xubuntu both got busybox. installing 8.10 alpha 6 got persistence drive, but could not install 8.10 to other drive. installing 8.10 Beta worked well as persistence, used Live USB to install to other drive. This morning tried drive and got grub with blinking curser. Tried on second computer and got error also. Reinstalled usb-creator into both 8.04 and 8.10 beta systems. Tried several times building persistent drives using these using both iso and CD. Got same errors at boot. Installed 8.10 once more as non persistent, this is now working. -- Persistence install stopped working https://bugs.launchpad.net/bugs/278361 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 278367] Re: installer confused by which flash drive is which
*** This bug is a duplicate of bug 8497 *** https://bugs.launchpad.net/bugs/8497 Downloaded the latest daily-live iso. A full install flash drive built using a live usb created using usb-creator now boots up without problem. On Tue, Oct 21, 2008 at 12:00 AM, Evan Dandrea [EMAIL PROTECTED] wrote: *** This bug is a duplicate of bug 8497 *** https://bugs.launchpad.net/bugs/8497 This is fixed in the latest daily-live CDs (http://cdimage.ubuntu.com /daily-live). ** This bug has been marked a duplicate of bug 8497 grub guessed BIOS disk order incorrectly -- installer confused by which flash drive is which https://bugs.launchpad.net/bugs/278367 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: New Bug description: Binary package hint: usb-creator Installed 8.10 Beta to flash using usb-creator. Used this drive to full install 8.10 Beta to second flash drive. Installer directed root to the persistent flash in menu.lst and not the flash I was now trying to build. Editing menu.lst to root (0,2) worked for me but I have fat32, home, root and swap partitions. -- installer confused by which flash drive is which https://bugs.launchpad.net/bugs/278367 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 276822] Re: busybox with (initramfs)
Works for me, usb-creator is looking good. On Mon, Oct 20, 2008 at 11:20 PM, Evan Dandrea [EMAIL PROTECTED] wrote: I believe this is fixed in the latest daily-live CDs. Can anyone that was seeing a busybox prompt, please try creating an image using one of the CDs found here: http://cdimage.ubuntu.com/daily-live/ Thanks! ** Changed in: usb-creator (Ubuntu) Importance: Undecided = High Status: New = Incomplete -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Incomplete Bug description: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 287228] [NEW] installer does not see second flash drive if plugged in after boot
Public bug reported: Binary package hint: usb-creator Using latest usb-creator and 8.10 Daily I installed full Ubuntu to second flash drive. Installer did not see second flash drive when plugged in after system has booted. It sees the second flash drive ok if it is plugged in at the first menu, (Language). It installs to second drive fine. ** Affects: usb-creator (Ubuntu) Importance: Undecided Status: New -- installer does not see second flash drive if plugged in after boot https://bugs.launchpad.net/bugs/287228 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 278361] Re: Persistence install stopped working
I think my problem was trying to install wine with only 128M persistent. With larger casper-rw wine installs ok, and the system still boots. On Tue, Oct 21, 2008 at 10:15 AM, Courtley Cameron [EMAIL PROTECTED]wrote: Rebuilt Flash using latest usb-creator and daily-live. Persistence seems to be working fine. Changed desktop background sticks as does network connection and install of AbiWord. Flash drive does not constantly blink as with persistent install of liveusb. Install stopped working after trying to start synaptic. Had a warning about root permissions. Will try again and report back. On Mon, Oct 20, 2008 at 11:52 PM, Evan Dandrea [EMAIL PROTECTED] wrote: Can you please check to see if persistence works with usb-creator 0.1.9 and the latest daily 8.10 Desktop CD, found here: http://cdimage.ubuntu.com/daily-live Thanks ** Changed in: usb-creator (Ubuntu) Status: Confirmed = Incomplete -- Persistence install stopped working https://bugs.launchpad.net/bugs/278361 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Incomplete Bug description: Binary package hint: usb-creator Installed usb-creator a few days ago. installing 8.04 ubuntu and xubuntu both got busybox. installing 8.10 alpha 6 got persistence drive, but could not install 8.10 to other drive. installing 8.10 Beta worked well as persistence, used Live USB to install to other drive. This morning tried drive and got grub with blinking curser. Tried on second computer and got error also. Reinstalled usb-creator into both 8.04 and 8.10 beta systems. Tried several times building persistent drives using these using both iso and CD. Got same errors at boot. Installed 8.10 once more as non persistent, this is now working. -- Persistence install stopped working https://bugs.launchpad.net/bugs/278361 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 276822] Re: busybox with (initramfs)
Booting from 8.10 Beta and using usb-creator to make 8.04.1 start up disk again get BusyBox, (initramfs). Scrolling was too fast to see much during debug, however the last line before BusyBox was: ( 57.847326) EXT3-fs: Unrecognized mount option mode=755 or missing value. I recall removing mode=755 from scripts/casper allows a flash drive created using liveusb to boot in persistence mode. On Mon, Oct 13, 2008 at 10:22 AM, Evan Dandrea [EMAIL PROTECTED] wrote: Can you both please attach the /casper.log file at the initramfs prompt, following the instructions in https://wiki.ubuntu.com/DebuggingCasper Thanks! ** Changed in: usb-creator (Ubuntu) Assignee: (unassigned) = Evan Dandrea (evand) Status: New = Incomplete -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Incomplete Bug description: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 276822] Re: busybox with (initramfs)
Will give install with 8.04.1 another shot today, with 8.10.1 Beta both Ubuntu and Xubuntu are working fine. On Mon, Oct 13, 2008 at 10:22 AM, Evan Dandrea [EMAIL PROTECTED] wrote: Can you both please attach the /casper.log file at the initramfs prompt, following the instructions in https://wiki.ubuntu.com/DebuggingCasper Thanks! ** Changed in: usb-creator (Ubuntu) Assignee: (unassigned) = Evan Dandrea (evand) Status: New = Incomplete -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a direct subscriber of the bug. Status in usb-creator source package in Ubuntu: Incomplete Bug description: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 280515] [NEW] Flash drive boot - menu.lst errors
Public bug reported: I have installed Xubuntu Beta on flash drive, full install, not CD image. Booting gave error message, no such drive. Menu.lst had root listed as (1,2). After changing root to (0,2) the drive boots. During updates I am asked to modify menu.lst. If I say yes, it is changed back to (1,2). From now on I will just say no. ** Affects: ubuntu Importance: Undecided Status: New -- Flash drive boot - menu.lst errors https://bugs.launchpad.net/bugs/280515 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278361] [NEW] Persistence install stopped working
Public bug reported: Binary package hint: usb-creator Installed usb-creator a few days ago. installing 8.04 ubuntu and xubuntu both got busybox. installing 8.10 alpha 6 got persistence drive, but could not install 8.10 to other drive. installing 8.10 Beta worked well as persistence, used Live USB to install to other drive. This morning tried drive and got grub with blinking curser. Tried on second computer and got error also. Reinstalled usb-creator into both 8.04 and 8.10 beta systems. Tried several times building persistent drives using these using both iso and CD. Got same errors at boot. Installed 8.10 once more as non persistent, this is now working. ** Affects: usb-creator (Ubuntu) Importance: Undecided Status: New -- Persistence install stopped working https://bugs.launchpad.net/bugs/278361 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 278367] [NEW] installer confused by which flash drive is which
Public bug reported: Binary package hint: usb-creator Installed 8.10 Beta to flash using usb-creator. Used this drive to full install 8.10 Beta to second flash drive. Installer directed root to the persistent flash in menu.lst and not the flash I was now trying to build. Editing menu.lst to root (0,2) worked for me but I have fat32, home, root and swap partitions. ** Affects: usb-creator (Ubuntu) Importance: Undecided Status: New -- installer confused by which flash drive is which https://bugs.launchpad.net/bugs/278367 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 276822] [NEW] busybox with (initramfs)
Public bug reported: Binary package hint: usb-creator Loaded onto thumbdrive running Xubuntu 8.04.1. Tried installing from disks: Xubuntu 8.04.1 Ubuntu 8.04.1 Ubuntu-EEE seemed to go ok but ended up in busybox with (initramfs). Installed Xubuntu 8.10 -6 from disk with no problem. But get busybox with (initramfs) when trying to boot on old mother board using Boot CD. Tried installing Xubuntu 8.10 -6 from .iso on desktop, this worked great also ** Affects: usb-creator (Ubuntu) Importance: Undecided Status: New -- busybox with (initramfs) https://bugs.launchpad.net/bugs/276822 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
