LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Bodhi
User Name
Password
Bodhi This forum is for the discussion of Bodhi Linux.

Notices


Reply
  Search this Thread
Old 07-06-2020, 02:50 PM   #1
sheemon
LQ Newbie
 
Registered: Jul 2020
Location: Deep South, USA
Distribution: Ubuntu,Bodhi, if usable
Posts: 3

Rep: Reputation: Disabled
bodhi-5.1.0-64-hwe on Inspiron 13 7573 Install to External SSD (USB) grub2 Error ?


First, Apologies Dept: I have very little Forum Exposure experience.
Very poor eyesight limits my searching ability. Nothing was found after a day.of searching.

Here it is;

The machine is as stated in the subject line : The internal store consists of 1TB SSD with Kubuntu 20.04 installed and current.
It installed eventlessly, but not without some setup struggle as noted below. I wanted to try a [more] correct E desktop.
I downloaded all three .iso files, and started by installing the "hwe" version.
I always install with custom partitioning. My experience here was very similar to the Kubuntu one, with the partitioning inconsistencies
Solved in a similar way; I used fdisk (or parted) to rewrite the MBR first. Otherwise, the installer would not cooperate), then struggled through the partitioning in the installer. I then suffered through some installer crashes (irrelevant here, but should be addressed). Eventually I had a smooth install experience, It seemed errors free and reportedly it was correct.
A prompt notified me there are some more tests to run (?), but suggested
re-boot. Re-boot it was.
I removed the thumb drive, left the USB drive connected, and let it re-boot.
A beautiful splash screen later, I was greeted with a Grub2 prompt.

Curiosity makes me ask "What have I done to deserve this
[grub screen]?"
But, foremost on my mind is "What do I do next?".
I very much want this installation to succeed.

Aside from these difficulties [which are to be expected], I really like the look and feel of this UI, and I have been a great fan of The Rasterman since his childhood. This project is very much a worthy one, I am eager to participate/support in any way I can, but it has to be rebooted first.

Any help will be very appreciated.

Sincerely,
Sheemon
 
Old 07-08-2020, 12:47 AM   #2
cordx
Member
 
Registered: Oct 2018
Location: texas
Distribution: bodhi 5.1.0
Posts: 696

Rep: Reputation: 158Reputation: 158
Quote:
Originally Posted by sheemon View Post
But, foremost on my mind is "What do I do next?".
I very much want this installation to succeed.
hopefully this link will help you be able to boot your system from the grub prompt: https://www.linux.com/training-tutor...-grub-2-linux/

there are other points to address in your post obviously, but that might get you started moving in the right direction.
 
Old 07-08-2020, 01:36 AM   #3
cordx
Member
 
Registered: Oct 2018
Location: texas
Distribution: bodhi 5.1.0
Posts: 696

Rep: Reputation: 158Reputation: 158
Quote:
Originally Posted by sheemon View Post
The machine is as stated in the subject line
make and model can be helpful to a degree, but a quick web search for just "Inspiron 13 7573" doesn't yield any definitive page from dell with one single set of hardware options. mostly what i found were review sites that suggest one of the possible components could be an nvidia gpu. some linux distributions are better than others at installing to systems with those.

i just recently bought a system with one and the install was more involved than any of the previous half dozen or so i had done on a system with just intel parts.

Quote:
Originally Posted by sheemon View Post
I then suffered through some installer crashes (irrelevant here, but should be addressed).
the installer crashed on my new system about a handful of times before i tried to continue without adding third party software or drivers. again, here is where knowing your exact hardware may provide some helpful hints.

it may be of interest to know that bodhi and kubuntu use the same installer called ubiquity.

Quote:
Originally Posted by sheemon View Post
A prompt notified me there are some more tests to run (?)
this is the installer saying it is done, but giving you an option to continue testing or using the system from a live usb if you want to. there are no other tests necessary.

Quote:
Originally Posted by sheemon View Post
Curiosity makes me ask "What have I done to deserve this

[grub screen]?"
there are all kinds of factors that go into a successful install (hardware is a big one). hopefully you can get booted from the grub prompt or get some help on how to do some things differently if you want to try again

Last edited by cordx; 07-08-2020 at 01:37 AM.
 
Old 07-08-2020, 09:56 PM   #4
sheemon
LQ Newbie
 
Registered: Jul 2020
Location: Deep South, USA
Distribution: Ubuntu,Bodhi, if usable
Posts: 3

Original Poster
Rep: Reputation: Disabled
Thanks and Update

So many thanks to the people who took the time and answered my illformed question.
For my own benefit, I am happy. For that of others, here is how I see things:

I am not trying to compete in the review sphere, but some context is necessary to understand what I found.

1. Bodhi 5.1.0 is a wonderful distribution. Very worthy of the effort.
All Open Source software are kits; Some assembly Required :-)
2. There are three distinct distributions of Bodhi (5.1.0), excluding the "Legacy" version, the fourth.
3. The main problem I encountered is in the installation process,
which is common to all of the editions.

The main error, IMHO, is as follows:
When one uses the "something else" option to slice and dice the storage device into several filesystems,
the resulting installation either omits the grub.cfg file, or puts in the system a wrong one.
As a result grub(1) fails to find a kernel [during bootstrapping] and drops into its shell mode.
Some replies suggested further reading on the subject and perhaps even a path to recovery. I chose not
to pursue it, as I found a workaround. See below.
I really would love to hear from the creators of Bodhi; The real solution is to "fix" the problem, not
work around it. This can take time, so here it is:

GOAL: Create a partition table on the drive where all the space is called for (assigned to filesystems, NOT swap.) All but ONE partition of the size, number, and location where you want the Bodhi to be installed.
RATIONALE: Bodhi 5.1.0 installs correctly [only] when it does a single filesystem installation.
Further, it will not work correctly if it does not create the partition by itself.
By creating a drive, where all space but what you want Bodhi to live, Bodhi will find this "free space"
and happily install itself in that space.

The traditional way to do it is quite obvious:
1. Boot into "Live ISO"
2. Open a shell
3. As root ('sudo fu' simply runs 'fu' as root), edit the partitions table
4. Launch the installer
5. Use the 'co-existence' option to install Bodhi
6. If necessary, migrate the filesystems to their partitions
7. Live happily ever after

If running the 'text mode' partitions editor is making you nervous, consider one of the following:

1. Find a GUI based partitions editor. Install and run it on the "Live ISO"
2. Use the Bodhi installer as a partitions editor;
a. Start 'The Thumb' Bodhi
b. Edit your drives and partitions - CAREFULLY!
You can still WIPE OUT your system.
The screen will be in pretty grey and green colors, but the storage will be gone!
c. Abort the installation when prompted for time zone
d. Start the installation over.

Any of these procedures will work. Others will too. This workaround appears safe.
The danger lies in human error.

Simon
 
Old 07-10-2020, 10:14 PM   #5
cordx
Member
 
Registered: Oct 2018
Location: texas
Distribution: bodhi 5.1.0
Posts: 696

Rep: Reputation: 158Reputation: 158
Quote:
Originally Posted by sheemon View Post
The main error, IMHO, is as follows:
When one uses the "something else" option to slice and dice the storage device into several filesystems,
the resulting installation either omits the grub.cfg file, or puts in the system a wrong one.
i use the "something else" option almost exclusively when installing bodhi and have done so successfully 9 times out of 10 with the exception being a system with an nvidia gpu. using that option puts the responsibility of where to install the bootloader in the user's hands.

this image is from a legacy virtual machine install, but the options would be similar for uefi. while installing to the disk itself (/dev/vda in this case) is usually the default choice on this screen, there is an option to install to the partition (/dev/vda1) which could result in a situation similar to the one you describe.

Click image for larger version

Name:	shot-2020-07-10_21-49-20.jpg
Views:	3
Size:	40.3 KB
ID:	33625
 
Old 07-11-2020, 04:44 AM   #6
sheemon
LQ Newbie
 
Registered: Jul 2020
Location: Deep South, USA
Distribution: Ubuntu,Bodhi, if usable
Posts: 3

Original Poster
Rep: Reputation: Disabled
Quote:
Originally Posted by cordx View Post
i use the "something else" option almost exclusively when installing bodhi and have done so successfully 9 times out of 10 with the exception being a system with an nvidia gpu. using that option puts the responsibility of where to install the bootloader in the user's hands.

this image is from a legacy virtual machine install, but the options would be similar for uefi. while installing to the disk itself (/dev/vda in this case) is usually the default choice on this screen, there is an option to install to the partition (/dev/vda1) which could result in a situation similar to the one you describe.

Attachment 33625
From long, painful experience: One of the most frustrating replies to a failure report is the ubiquitous "it works for me". Especially, when it comes from a developer. This is clearly not the case here!
Nonetheless, it does not solve my problem. Your system(s) installed, mine did not.
From reading, trying, thinking, and trying again, I doubt this is a hardware problem. Let me explain why I think so:

1. The "hardware" aspects of the installation process are handled by grub, and by the Linux kernel (Okay, the drivers in the kernel.) Everything else sees a device either as a file, a byte strweam, or a linear
array of blocks. Even sectors were abstracted in the later CP/M 1.4 days.
2. The problem is distribution specific. I performed the same wild installation procedure with Kubuntu 20.04, without the issues I am raising here. Also note, I tried this procedure with the internal drive, and with a USB connected external one. It is exactly the same issue.
3. I even thought the problem may arise from bad memory, CPU, M/B, what-have-you. I see so many strange phenomena with this release, I started doubting myself (there is a lot to doubt in me :-)

Again and again - I want to get to the bottom of this problem. Someone may benefit from it.
Besides, it is such a beautiful system with so many things so good about it. I want it to succeed.

Finally, my immediate problem is solved. I rebooted successfully, connected my backup drive, and started restoring my dust covered junk. I have little experience in matters of forums and decorum. If I should now go elsewhere, please tell me. Just be gentle :-)

Thanks,
Simon
 
Old 07-11-2020, 06:50 AM   #7
cordx
Member
 
Registered: Oct 2018
Location: texas
Distribution: bodhi 5.1.0
Posts: 696

Rep: Reputation: 158Reputation: 158
Quote:
Originally Posted by sheemon View Post
From long, painful experience: One of the most frustrating replies to a failure report is the ubiquitous "it works for me".
i was honestly trying to help by sharing anecdotes from personal experience like you have been. one of the reasons i answered your first post was because i had ended up at a grub prompt at some point not long after my first bodhi installation and was also unsure of how to finish the boot process.

Quote:
Originally Posted by sheemon View Post
Especially, when it comes from a developer.
i'm not sure where you got that impression. i am a regular, daily bodhi user.

Quote:
Originally Posted by sheemon View Post
This is clearly not the case here!
Nonetheless, it does not solve my problem. Your system(s) installed, mine did not.
after failing the first five times on my most recent system.

Quote:
Originally Posted by sheemon View Post
From reading, trying, thinking, and trying again, I doubt this is a hardware problem. Let me explain why I think so:


1. The "hardware" aspects of the installation process are handled by grub, and by the Linux kernel (Okay, the drivers in the kernel.) Everything else sees a device either as a file, a byte strweam, or a linear
array of blocks. Even sectors were abstracted in the later CP/M 1.4 days.
2. The problem is distribution specific. I performed the same wild installation procedure with Kubuntu 20.04, without the issues I am raising here. Also note, I tried this procedure with the internal drive, and with a USB connected external one. It is exactly the same issue.
3. I even thought the problem may arise from bad memory, CPU, M/B, what-have-you. I see so many strange phenomena with this release, I started doubting myself (there is a lot to doubt in me :-)

Again and again - I want to get to the bottom of this problem. Someone may benefit from it.
Besides, it is such a beautiful system with so many things so good about it. I want it to succeed.

Finally, my immediate problem is solved. I rebooted successfully, connected my backup drive, and started restoring my dust covered junk. I have little experience in matters of forums and decorum. If I should now go elsewhere, please tell me. Just be gentle :-)

Thanks,
Simon
i am glad to hear you solved it
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
[SOLVED] linux-image-generic-hwe-18.04 and linux-generic-hwe-18.04 upgrade failure on Linux Mint 19.3 rjo98 Linux - Distributions 6 04-12-2020 10:15 AM
kernel: RTNL: assertion failed at /build/linux-hwe-vH8Hlo/linux-hwe-4.10.0/net/core/dev.c (2322) genogebot Ubuntu 0 08-03-2017 01:46 AM
[SOLVED] 12.04 Raring HWE update killed installation JZL240I-U Ubuntu 1 08-28-2013 09:28 AM
LXer: Ubuntu: 1936-1: Linux kernel (Raring HWE) vulnerabilities LXer Syndicated Linux News 0 08-22-2013 12:42 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Bodhi

All times are GMT -5. The time now is 09:02 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration