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
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:
>
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
@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
@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
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
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
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
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
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
@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
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:
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
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
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
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
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
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
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
@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
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
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
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
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.
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
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
@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
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
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
@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
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
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.
--
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
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
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'
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
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 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
@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
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
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
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
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
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
@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
@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
?
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 differ
@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
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
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
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.
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
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.
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
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"
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
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
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
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
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
*** 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
*** 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
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.
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
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.
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
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)
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
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
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
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
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.
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
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:
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
*** 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]
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:
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
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
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
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
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
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
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
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
85 matches
Mail list logo
