** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1784221
Title:
unable to find a medium containing a live file system
Status in linux package in Ubuntu:
Invalid
Bug description:
Hello.
I know that this problem has been the subject of several malfunctions but
this incident occurs in a rather unusual context.
I have a computer equipped with a bios EFI. So I do not use cdrom
drive or usb key to install ubuntu.
I decompress the ISO file and put the content in a partition FA32.
then I choose to boot using the boot file. It works very well for
almost four years see https://forum.ubuntu-
fr.org/viewtopic.php?id=1725191 and https://forum.ubuntu-
fr.org/viewtopic.php?id=1954341
I use this procedure every six months. The last time, it was in January 2018
with the daily version of version 18.04 (
https://forum.ubuntu-fr.org/viewtopic.php?pid=21862486#p21862486 )
As usual I had noted "sudo umount -lv /cdrom "
I did not think to install the 18.4.0 version of April 2018. I do now
with the version 18.04.1 of July 2018.
So I use the torrent technique to download the iso. I still control the
md5sum.
( f430da8fa59d2f5f4262518e3c177246 *ubuntu-18.04.1-desktop-amd64.iso )
I transfer in my partition fat32 (I even put the ESP flag) and I boote
I have the 4 lines of choice
Try ubuntu without installing
Install ubuntu
Oem Install (for manufacturer)
Check disk for deffect
I have to wait about five minutes to get the message mentioned in the title
"unable to find a medium containing a live file system".
It's the same thing when choosing the other three options
The contents of the casper.log file consist of a repeated line 121 times.
"/init: line 7: can't open /dev/sr0: No medium found"
in iniramfs , the command ls -ls give
0 drwxr-xr-x 14 4540 dev
0 drwx------ 2 40 root
8 -rwxr-xr-x 1 6643 init
0 drwxr-xr-x 4 80 usr
0 drwxr-xr-x 11 260 lib
0 drwxr-xr-x 5 100 var
0 drwxr-xr-x 2 2440 bin
0 drwxr-xr-x 12 380 scripts
0 drwxr-xr-x 3 140 conf
0 drwxr-xr-x 2 60 lib64
0 drwxr-xr-x 11 400 etc
0 drwxr-xr-x 6 120 run
0 drwxr-xr-x 2 500 sbin
0 dr-xr-xr-x 13 0 sys
0 dr-xr-xr-x 98 0 proc
4 drwxr-xr-x 3 4096 tmp
0 drwxr-xr-x 2 40 cdrom
0 -rw-r--r-- 1 0 casper.vars
8 -rw-r--r-- 1 6294 casper.log
I restarted with the option debug = vt but I can not understand the false
manipulation that I made. Is this a re-engineering of the software?
I will attach the trace file and the list of files present in the boot
partition of the hard disk
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1784221/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
