Unable to install linux

Unable to install ubuntu desktop

I am installing ubuntu 10.10. I have changed the ubuntu iso image and version also, but still i am facing the same issue. System Specification: Dell Optiplex — 380 Ram : 1 GB
Processor : Dual Core @ 3.20 GHz
Harddisk : 250 GB I am not seeing any option to disable SMP in Bios.

Please provide information about the version that you are trying to install and preferably add that to the tags as well.

1 Answer 1

I suspect this is on older hardware with broken SMP, or on newer hardware that the kernel in the installer doesn’t quite work with. In the case of the SMP, try to change the SMP version in BIOS, or disabling it outright.

I have had problems with some motherboards on older kernels. You can try to boot with the kernel flag noacpi and/or noapic.

If you provide us with information about the hardware you’re trying to install on, it may give us better clues as to what’s going on.

I have upgraded the bios version and the upgradation was successful. But still i am facing the same problem. What may be the issue?

There is a detailed explanation, as well as description of the options I listed above and a few others at ubuntuforums.org/showthread.php?t=1613132

I also found a few others with server hardware giving them problems. They recommend disabling C-States in the BIOS, which may be called something else, but is related to power-saving modes of the CPU itself. You can read more about this and other possible kernel boot options at bugzilla.redhat.com/show_bug.cgi?id=548198

I have tried all the possible ways. Will it be some hardware issue? I have tried changing my harddrive and ram but stil the problem persists. How to debug the issue?

Источник

Unable to install Ubuntu 20.04 with pre-existing software RAID with 2 disks

This leaves me no option to successfully install Ubuntu on my system. I have tried following possible solution but it did not work:

1. Used mdadm to load RAID configuration in Ubuntu 20.04 live environment and then started the Ubuntu 20.04 installer which then successfully detected all the existing logical LVM on top of the software RAID. I am able to install Ubuntu 20.04 but on reboot RAID configuration is not loaded automatically.

If I can somehow select the boot disk with Ubuntu 20.04 Server installer, I think then I can install server and then use APT to install desktop environment.

I would appreciate any possible help to understand how to select boot disk with Ubuntu 20.04 server installer or make the Ubuntu 20.04 Desktop installer detect the existing software RAID.

1 Answer 1

Installing Ubunto Desktop 20.04.1

After some digging I got a bit more insight I want to share:

Removing the software raid by removing the harddisks allows to install Ubunto via the installer without a glitch. The ubunto installer does not work with software raids, while the installed ubunto system does. Then reconnect the harddisks of the software raid, and boot a live system (like parted magic). Copy the files to places on the raid and update all configuration files that connect to partitions.

1. Remove the harddisks that make up the raid.
2. Do not add a harddisk — but NVMe SSD, otherwise the BIOS will attempt to reorganise the missing the software raid. I added an NVMe SSD installed Ubunto there. Just add anything you can install ubunto on. Make sure the root partition is not btrfs (I used ext4), as this will facilitate to copy the root partition to a software-raid partition. Using btrfs will add subvolumes that are cumbersome to copy (especially when using this filesystem for the root partition).
3. Install Ubunto 20.04.1 from an USB stick. Make sure to use a /home partition during the install, located on the NVMe SSD Do not use BTRFS for the root partition.
4. After the installation is complete start ubunto and install mdadm apt-get install mdadm
5. After that, shut down the ubunto system and reconnect the harddrives that made up the software raid.
6. Start Ubunto and edit /etc/fstab reconnect /home to the software raid partition
7. Option: move ubunto partitions to the software raid The best option is that you boot using a live system that is not the installed ubunto version. 7.1 copy the content of all ubunto partitions to partitions (ideally of equal size) on the software raid 7.2 edit /etc/fstab and connect all partitions to the ones on the software raid 7.3 Use efibootmgr to update (or create) the BIOS entry to start the ubunto system from the raid (use UUIDs which you query with the command blkid)

Eventually it worked. I can run multiple linux distributions including ubunto on the software raid. It is kind of sad that ubunto does not support software raids, which do improve system stability and especially the ability to recover from HDD or SDD failures. The solution with the software raids allowed me to run several systems for more than 7 years with minimal changes.

Now some speculation as to what went wrong: I gave up looking for the source code of the installer and the grub version that comes with it. I could reproduce the error given by the installer: cannot stat /cow which is most likely a simple parsing error in grube-probe, which is called from grub-install.

Grub2 used by OpenSuse Leap 15.2 does not have this kind of problem.

This is a description of how to go about installing Ubunto Server.

Comment: I have not tried the solution above but based on my experience it will work most likely. I did not try that as it involved the destruction of the existing raid, which I did not want (unless absolutely necessary — and it turned out that it was not necessary at all)

Источник

Linux installer keeps freezing, unable to install any Linux

I tried both Ubuntu 18 and Linux Mint 19, both freeze and cannot install a Linux. Apparently, there is an Ubuntu 18 installed somewhere(despite not booting into any OS) and it keeps notifying me that my disk is full (not true, but it shows me some 7gb root partition on smth). Booting from live USB. EDIT: It’s a bit of a long story but I will do my best as a beginner to explain everything. I had Ubuntu 17 and decided to upgrade it to 18 via the command line command, after the update there was a weird bug which I couldn’t fix despite looking for days on the internet. This weird bug was that after pressing enter on the login screen, ubuntu 18.04 would freeze completely. So I tried reinstalling it, which failed since it kept freezing at different times (booting from liveUSB). I restarted so many times (in hope of the installer to work) that the previous os got corrupted. That’s when I decided to switch to a different Linux distribution: Linux Mint. The same thing happened, except now I got a different message: low disk space 0bytes remaining .(note: I don’t have an OS, so I fully boot from live USB). So I installed windows, to delete partitions, but it was weird since I have an SSD of 256GB and only 238GB of maximum capacity was shown. Anyway, after this, I tried Linux installation 2 times, without and with liveUSB, but it failed with the same “no space” remaining message. Now I don’t have an OS, and booting from liveUSB (currently containing mint).

$ df -hT Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 1.9G 0 1.9G 0% /dev tmpfs tmpfs 383M 1.5M 382M 1% /run /dev/sdb1 vfat 116G 1.9G 114G 2% /cdrom /dev/loop0 squashfs 1.8G 1.8G 0 100% /rofs /cow overlay 1.9G 1.8G 149M 93% / tmpfs tmpfs 1.9G 24M 1.9G 2% /dev/shm tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock tmpfs tmpfs 1.9G 0 1.9G 0% /sys/fs/cgroup tmpfs tmpfs 1.9G 4.0K 1.9G 1% /tmp tmpfs tmpfs 383M 44K 383M 1% /run/user/999 tmpfs tmpfs 383M 0 383M 0% /run/user/0 $ fdisk -l Disk /dev/loop0: 1.7 GiB, 1859526656 bytes, 3631888 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk /dev/sda: 238.5 GiB, 256060514304 bytes, 500118192 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 7146433C-9F18-4CD5-A424-7F6665C88C41 Device Start End Sectors Size Type /dev/sda1 2048 1050623 1048576 512M EFI System /dev/sda2 1050624 500117503 499066880 238G Linux filesystem Disk /dev/sdb: 115.5 GiB, 124017180672 bytes, 242221056 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: dos Disk identifier: 0x029c3084 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 2048 242221055 242219008 115.5G c W95 FAT32 (LBA) 

Источник

Thread: unable to install anything in ubuntu 18.04

First Cup of Ubuntu

unable to install anything in ubuntu 18.04

whenever I try to install any software I get a same error message.

I have installed Ubuntu on my 32 Gib SanDisk pendrive, (not in live or persistance mode) I used a live cd to boot and (disconnected my internal hard drive) install ubuntu (and bootloader also) on my penDrive.

Everything works fine, I can make new files and save them, next time when i boot again all the previous files, bookmarks, settings etc are there. System is behaving very much same as if a had a normal install on my hard drive. Except this:

I can browse internet using Mozilla Firefox, I use college proxy settings to connect to internet (provided proxy in settings > networks > networks proxy > apply system wide)
but i can not install any program through terminal nor from Ubuntu Software Center.

mac@macUbuntu:~$ sudo apt-get install vlc Reading package lists. Done Building dependency tree Reading state information. Done E: Unable to locate package vlc

mac@macUbuntu:~$ sudo apt-get update Ign:1 cdrom://Ubuntu 18.04.1 LTS _Bionic Beaver_ - Release amd64 (20180725) bionic InRelease Err:2 cdrom://Ubuntu 18.04.1 LTS _Bionic Beaver_ - Release amd64 (20180725) bionic Release Please use apt-cdrom to make this CD-ROM recognized by APT. apt-get update cannot be used to add new CD-ROMs Err:3 http://archive.ubuntu.com/ubuntu bionic InRelease Could not connect to archive.ubuntu.com:80 (91.189.88.161). - connect (111: Connection refused) Could not connect to archive.ubuntu.com:80 (91.189.88.152). - connect (111: Connection refused) Could not connect to archive.ubuntu.com:80 (91.189.88.162). - connect (111: Connection refused) Could not connect to archive.ubuntu.com:80 (91.189.88.149). - connect (111: Connection refused) Err:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease Unable to connect to archive.ubuntu.com:http: Err:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease Unable to connect to archive.ubuntu.com:http: Err:6 http://archive.ubuntu.com/ubuntu bionic-security InRelease Unable to connect to archive.ubuntu.com:http: Reading package lists. Done E: The repository 'cdrom://Ubuntu 18.04.1 LTS _Bionic Beaver_ - Release amd64 (20180725) bionic Release' does not have a Release file. N: Updating from such a repository can't be done securely, and is therefore disabled by default. N: See apt-secure(8) manpage for repository creation and user configuration details.

Источник