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
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,
Forget "quiet", it's whether "fsck.mode=skip" is the last thing on
the kernel command line.
There is no disk check if there is something after
"fsck.mode=skip". I tried "quiet". Then I tried "nomodeset" instead.
I tried putting a blank at the end of the line. That was *not*
enough
I craft my boot device by hand. I'm using files filched from some
Ubuntu distribution (so, GRUB2), lately booting with the ISO file. I've
booted from an external (USB) hard disk, and from thumb drives.
On my external hard drive, I copied vmlinuz and initrd to the ESP
(because on another
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.
--
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
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
Ubuntu 20.04.1 performs the disk check when booted from an ISO.
"fsck.mode=skip" does *not* prevent the disk check.
--
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
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
1. Maybe the bugfix is only addressing Groovy, which has casper 1.447
now.
2. It seems that the bugfix is only an update of the casper manpage
because the integrity check is still there for persistent live systems
unless I add the boot option
fsck.mode=skip
(tested in Lubuntu Groovy).
--
You
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
This bug was fixed in the package casper - 1.447
---
casper (1.447) groovy; urgency=medium
[ Matthieu Clemenceau ]
* Updated cmdline options in casper manpage documentation. LP: #1875548
[ Michael Hudson-Doyle ]
* Add interactive network configuration.
[ Dimitri John
** Tags added: id-5ea8876742d85332d7b138bb
--
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
After testing older versions of Ubuntu, it seems that 'fsck.mode=skip'
is simply ignored, and does not create any problem. So I have included
it in some of the menu entries for persistence and 'live-only to RAM'
created by mkusb version 12.4.7.
--
You received this bug notification because you
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
@ Brian Murray,
That is a good idea. I tested and it works with Focal Fossa :-)
What happens when we use the boot option 'fsck.mode=skip' for older
versions of Ubuntu (for example 18.04 LTS)? Will it cause some error or
simply be ignored?
--
You received this bug notification because you are a
17 matches
Mail list logo
