|
|
| Line 1: |
Line 1: |
| − | Jan 1 16:15:07 kubuntu ubiquity: umount: /target/cdrom: mountpoint not found
| + | Boot kubuntu in UEFI mode from the BIOS. You achieve this by pressing F2 when the DELL logo shows up and in Boot Option, select UEFI. Secure mode must be disabled. |
| − | Jan 1 16:15:07 kubuntu /plugininstall.py: log-output -t ubiquity umount /target/cdrom
| + | |
| − | Jan 1 16:15:07 kubuntu /plugininstall.py: log-output -t ubiquity mount --bind /cdrom /target/cdrom
| + | |
| − | Jan 1 16:15:07 kubuntu ubiquity: /usr/lib/ubiquity/apt-setup/generators/01setup: 9: /usr/lib/ubiquity/apt-setup/generators/01setup: cannot open /target/etc/apt/sources.li
| + | |
| − | Jan 1 16:15:08 kubuntu in-target: Reading package lists...
| + | |
| − | Jan 1 16:15:08 kubuntu in-target:
| + | |
| − | Jan 1 16:15:08 kubuntu apt-setup: Using CD-ROM mount point /cdrom/
| + | |
| − | Jan 1 16:15:08 kubuntu apt-setup: Identifying...
| + | |
| − | Jan 1 16:15:08 kubuntu apt-setup: [43aa65744ed4d4e6bf51470e9c73a186-2]
| + | |
| − | Jan 1 16:15:08 kubuntu apt-setup: Scanning disc for index files...
| + | |
| − | Jan 1 16:15:08 kubuntu apt-setup: Found 0 package indexes, 0 source indexes, 0 translation indexes and 0 signatures
| + | |
| − | Jan 1 16:15:08 kubuntu apt-setup: E: Unable to locate any package files, perhaps this is not a Debian Disc or the wrong architecture?
| + | |
| − | Jan 1 16:15:08 kubuntu apt-setup: E: No CD-ROM could be auto-detected or found using the default mount point.
| + | |
| − | Jan 1 16:15:08 kubuntu apt-setup: You may try the --cdrom option to set the CD-ROM mount point.
| + | |
| − | Jan 1 16:15:08 kubuntu apt-setup: See 'man apt-cdrom' for more information about the CD-ROM auto-detection and mount point.
| + | |
| − | Jan 1 16:15:11 kubuntu activate-dmraid: No Serial ATA RAID disks detected
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py: log-output -t ubiquity umount /target/cdrom
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py: Exception during installation:
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py: Traceback (most recent call last):
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 1710, in <module>
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py: install.run()
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 60, in wrapper
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py: func(self)
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 184, in run
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py: self.configure_apt()
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py: File "/usr/share/ubiquity/plugininstall.py", line 587, in configure_apt
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py: "AptSetup failed with code %d" % ret)
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py: ubiquity.install_misc.InstallStepError: AptSetup failed with code 141
| + | |
| − | Jan 1 16:15:11 kubuntu /plugininstall.py:
| + | |
| − | Jan 1 16:15:12 kubuntu partman: No matching physical volumes found
| + | |
| − | Jan 1 16:15:12 kubuntu partman: Reading volume groups from cache.
| + | |
| − | Jan 1 16:15:13 kubuntu ubiquity: tune2fs: Bad magic number in super-block while trying to open /dev/nvme0n1
| + | |
| − | Jan 1 16:15:13 kubuntu ubiquity: Found a gpt partition table in /dev/nvme0n1
| + | |
| − | Jan 1 16:15:13 kubuntu partman: Error running 'tune2fs -l /dev/nvme0n1'
| + | |
| − | Jan 1 16:15:13 kubuntu ubiquity: tune2fs: Bad magic number in super-block while trying to open /dev/nvme0n1
| + | |
| − | Jan 1 16:15:13 kubuntu ubiquity: Found a gpt partition table in /dev/nvme0n1
| + | |
| − | Jan 1 16:15:13 kubuntu partman: Error running 'tune2fs -l /dev/nvme0n1'
| + | |
| − | Jan 1 16:15:14 kubuntu ubiquity[2122]: Device free not found in os-prober output
| + | |
| − | Jan 1 16:15:14 kubuntu ubiquity[2122]: Device /dev/nvme0n1p1 not found in os-prober output
| + | |
| − | Jan 1 16:15:14 kubuntu ubiquity[2122]: Device free not found in os-prober output
| + | |
| − | Jan 1 16:15:14 kubuntu ubiquity[2122]: debconffilter_done: ubi-partman (current: ubi-partman)
| + | |
| | | | |
| | My solution is to run [https://sourceforge.net/p/boot-repair/home/Home/ boot-repair] after the installer crashed. | | My solution is to run [https://sourceforge.net/p/boot-repair/home/Home/ boot-repair] after the installer crashed. |
| Line 45: |
Line 5: |
| | sudo add-apt-repository ppa:yannubuntu/boot-repair | | sudo add-apt-repository ppa:yannubuntu/boot-repair |
| | sudo apt-get update | | sudo apt-get update |
| − | sudo apt-get install -y boot-repair && boot-repair | + | sudo apt-get [[Media:Example.ogg]]install -y boot-repair && boot-repair |
| | | | |
| | Boot-repair comes with problems of its own, along the lines of Please enable a repository containing the [...] packages in the software sources of ... Then try again. Generating the report and looking at the error, it shows where the software is looking for sources.list. It is then just a matter of locating it (locate) and symlink, then run again. Following the steps boot-repairs advises you to take successfully installs the boot-loader. | | Boot-repair comes with problems of its own, along the lines of Please enable a repository containing the [...] packages in the software sources of ... Then try again. Generating the report and looking at the error, it shows where the software is looking for sources.list. It is then just a matter of locating it (locate) and symlink, then run again. Following the steps boot-repairs advises you to take successfully installs the boot-loader. |
Boot kubuntu in UEFI mode from the BIOS. You achieve this by pressing F2 when the DELL logo shows up and in Boot Option, select UEFI. Secure mode must be disabled.
sudo add-apt-repository ppa:yannubuntu/boot-repair
sudo apt-get update
sudo apt-get Media:Example.ogginstall -y boot-repair && boot-repair
Boot-repair comes with problems of its own, along the lines of Please enable a repository containing the [...] packages in the software sources of ... Then try again. Generating the report and looking at the error, it shows where the software is looking for sources.list. It is then just a matter of locating it (locate) and symlink, then run again. Following the steps boot-repairs advises you to take successfully installs the boot-loader.