[Bug 2098551] Re: kubunto installation crash while in pendrive ubunto live session. installation supposed to wipe SSD drive with a previous windows 10 installation. trying to migrate from windows to linux.
Gaspar Caon
2098551 at bugs.launchpad.net
Sat Jun 14 13:35:06 UTC 2025
Thanks, though not much time later, I was able to install Ubuntu 24.04
instead of Kubuntu.
The problem I was facing involved RAID. I was able to fix it after some
browsing in internet forums. Follows my chat with Deepseek from this
point onwards, and how we diagnosed the issue. This might help other
users as well.
=====================
I've read in internet forums this error have to do with RAID and
multiple drives. They say to edit the kernel command line and add the
option "nodmraid". What does this really mean?
You're absolutely correct! The |nodmraid| kernel option is often
suggested to address issues related to RAID (Redundant Array of
Independent Disks) configurations, especially when the installer
mistakenly detects RAID setups or encounters problems with multiple
drives. Let me explain what this means and how to apply it.
*What is |nodmraid|?*
*
|nodmraid| is a *kernel boot parameter* that disables the detection
and management of *fake RAID* (also known as BIOS RAID or Intel
Rapid Storage Technology RAID).
*
Fake RAID is a software-based RAID implementation that relies on the
motherboard's BIOS or a driver to manage the RAID array.
*
If your system has no RAID configuration but the installer
mistakenly detects one, |nodmraid| can prevent the installer from
trying to interact with non-existent RAID arrays.
------------------------------------------------------------------------
*Why Use |nodmraid|?*
*
The |ubi-partman| error you encountered might be caused by the
installer detecting RAID metadata on your drives, even if you’re not
using RAID.
*
Adding |nodmraid| to the kernel command line ensures that the
installer ignores any RAID-related configurations and treats your
drives as regular standalone disks.
------------------------------------------------------------------------
*How to Add |nodmraid| to the Kernel Command Line*
1. *During Boot (Temporary Solution)*
*
When booting from the USB drive:
1.
At the GRUB menu (the bootloader screen), highlight the *"Try or
Install Kubuntu"* option.
2.
Press |e| to edit the boot parameters.
3.
Find the line starting with |linux| or |linuxefi|.
4.
Add |nodmraid| to the end of the line (after |quiet splash| or
similar parameters).
5.
Press |Ctrl+X| or |F10| to boot with the modified parameters.
*
This change is temporary and only applies to the current boot
session.
------------------------------------------------------------------------
2. *Permanent Solution (Editing the Bootloader Configuration)*
*
If you want to make the change permanent for the live session or
installation:
1.
Boot into the live session.
2.
Open a terminal and edit the GRUB configuration file:
bash
#
sudo nano /etc/default/grub
#
Find the line starting with |GRUB_CMDLINE_LINUX_DEFAULT|.
#
Add |nodmraid| to the end of the line (inside the quotes). For example:
bash
#
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash nodmraid"
#
Save the file and exit (|Ctrl+O|, |Enter|, |Ctrl+X|).
#
Update GRUB:
bash
*
6.
sudo update-grub
7.
Reboot the system and try the installation again.
------------------------------------------------------------------------
*When to Use |nodmraid|*
*
Use |nodmraid| if:
o
You’re not using RAID.
o
The installer is failing due to RAID-related issues.
o
You suspect the installer is detecting RAID metadata on your
drives.
------------------------------------------------------------------------
*Additional Notes*
*
If you’re using *actual hardware RAID*, do not use |nodmraid|, as it
will disable RAID functionality.
*
If |nodmraid| doesn’t resolve the issue, you may also try adding
other kernel parameters like |nomodeset| (to disable GPU drivers) or
|acpi=off| (to disable ACPI, which can sometimes cause issues).
------------------------------------------------------------------------
*Next Steps*
1.
Add |nodmraid| to the kernel command line (as described above).
2.
Restart the installer (|ubiquity|) and proceed with the
installation.
3.
If the issue persists, let me know, and we can explore further
troubleshooting steps.
Let me know how it goes! 😊
I managed to boot with no problems after adding "nodmraid" option in the
booting options. Ubuntu install wizard appears to be working. While
configuring my account, it's asking if I want to use "Active Directory",
but I don't know what this means.
Great to hear that adding |nodmraid| resolved the booting issue! Now,
let’s clarify what *Active Directory* is and whether you need to use it
during the Ubuntu installation.
------------------------------------------------------------------------
*What is Active Directory?*
*
*Active Directory (AD)* is a directory service developed by
Microsoft, primarily used in Windows environments.
*
It allows centralized management of users, computers, and other
resources in a network.
*
For example, in a corporate or organizational setting, Active
Directory can be used to:
o
Manage user accounts and permissions.
o
Enforce security policies.
o
Provide single sign-on (SSO) for accessing network resources.
------------------------------------------------------------------------
*Do You Need Active Directory?*
*
*For most home users or individual setups*, you *do not need* to use
Active Directory.
*
You would only use Active Directory if:
o
You’re part of a corporate or organizational network that uses
AD.
o
You want to integrate your Ubuntu system into an existing
Windows domain.
------------------------------------------------------------------------
*What to Do During Installation*
*
Since you’re setting up Ubuntu for personal use, you can *safely
skip the Active Directory option*.
*
Simply leave the field blank and proceed with creating your local
user account.
------------------------------------------------------------------------
*Creating a Local User Account*
*
During the installation, you’ll be asked to:
1.
Enter your *name*.
2.
Choose a *username* (this will be your login name).
3.
Set a *password*.
4.
Optionally, enable *automatic login* or require a password to
log in.
*
This will create a *local user account* on your Ubuntu system, which
is sufficient for personal use.
------------------------------------------------------------------------
*What If You Need Active Directory Later?*
*
If you later decide to join an Active Directory domain, you can do
so after installation:
1.
Install the necessary packages:
bash
#
sudo apt install realmd sssd sssd-tools libnss-sss libpam-sss adcli
samba-common-bin
#
Discover the domain:
bash
#
sudo realm discover your-domain.com
#
Join the domain:
bash
*
3.
sudo realmjoin your-domain.com-U your-admin-username
4.
Configure SSSD (System Security Services Daemon) for
authentication.
------------------------------------------------------------------------
*Summary*
*
*Skip the Active Directory option* during installation unless you’re
part of a network that uses it.
*
Create a *local user account* for personal use.
*
You can always join an Active Directory domain later if needed.
Let me know if you have any other questions or run into any issues! 😊
So far, so good, installation is on the way. Thanks
-------------------------
On 14/06/2025 03:39, Amber Sullivan wrote:
> I faced a similar issue during installation from a live Ubuntu session.
> In my case, running ubiquity helped refresh the graphics, but the
> installer behavior was still inconsistent. If you're still having
> trouble or want a step-by-step guide on handling installation problems
> or working with tools like DeepSeek, you might find this helpful:
> https://deepseeksguides.com/. It offers clear, beginner-friendly
> instructions for navigating such issues.
>
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/2098551
Title:
kubunto installation crash while in pendrive ubunto live session.
installation supposed to wipe SSD drive with a previous windows 10
installation. trying to migrate from windows to linux.
Status in ubiquity package in Ubuntu:
New
Bug description:
Kubuntu installation crash while in a Ubuntu pendrive live session.
Installation supposed to wipe SSD drive with a previous windows 10
installation for a fresh install of Kubuntu.
Expected Ubuntu installation, but ran into the "How do you want to
install Ubuntu?" issue during the install wizard. Nothing else is
offered in this dialog. IA Deepseek suggested running ubiquity to
"refresh" graphics. Running ubiquity though led to Kubuntu
installation, I accepted.
More info:
No LSB modules are available.
Description: Ubuntu 24.04.1 LTS
Release: 24.04
N: Unable to locate package pkgname
Requested files attached, ignore the "syslog" description. It's
"files.zip" with both files
ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: ubiquity 24.04.5
ProcVersionSignature: Ubuntu 6.8.0-41.41-generic 6.8.12
Uname: Linux 6.8.0-41-generic x86_64
NonfreeKernelModules: zfs
ApportVersion: 2.28.1-0ubuntu3.1
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.498
CloudArchitecture: x86_64
CloudID: nocloud
CloudName: unknown
CloudPlatform: nocloud
CloudSubPlatform: seed-dir (/var/lib/cloud/seed/nocloud)
CurrentDesktop: ubuntu:GNOME
Date: Sat Feb 15 01:19:38 2025
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz --- quiet splash
LiveMediaBuild: Ubuntu 24.04.1 LTS "Noble Numbat" - Release amd64 (20240827.1)
ProcEnviron:
LANG=C.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
TERM=xterm-256color
XDG_RUNTIME_DIR=<set>
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/2098551/+subscriptions
More information about the foundations-bugs
mailing list