LinuxQuestions.org
Review your favorite Linux distribution.
Home Forums Tutorials Articles Register
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices


Reply
  Search this Thread
Old 02-06-2024, 02:37 PM   #1
Targa9
LQ Newbie
 
Registered: Feb 2024
Posts: 6

Rep: Reputation: 0
Question operation system not found after fresh install


I have an old Dell laptop I bought back in 2011 which I wasn't using (I'm now using a newer laptop.)
It has and I7 CPU, with 8 GB of memory and two 750 GB drives. It's an XPS Dell.
I wanted to try Linux so I downloaded Ubuntu and installed it on the old laptop. I chose the option to delete everything on the hard drive. After the installation the error message: "operation system not found" came up. I tried reinstalling (also with option to delete contents of hard drive so I wouldn't have two installations of Ubuntu.) Same result.
I then downloaded "Mint" and installed it with the same result. (I also chose erase the drive during this install so I wouldn’t have two different versions of Linux.)

I've tried numerous "fixes" but none worked.

I tried these:
set prefix=(hd0,msdos1)/boot/grub
set root=(hd0,msdos1)
insmod normal

insmod linux
linux /vmlinuz root=/hd0/msdos1
initrd /initrd.img
boot

Never got past the "vmlinuz" because it couldn't find it.

I'd appreciate any help getting this booted. I'd love to dump Windows!

Last edited by Targa9; 02-06-2024 at 04:36 PM.
 
Old 02-06-2024, 04:36 PM   #2
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 5,859
Blog Entries: 1

Rep: Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074
Your description is rather sketchy, making it hard to tell what transpired after boot failed. What lead you to choose the "fixes" you tried?

Is Windows still installed on one of the two disks? If yes, it may be instructive to remove that disk and try booting Linux.

Using F12 at POST time, do you get a menu that offers a selection of more than one OS to boot or disk to boot from?

"operating system not found" IIRC may be a result of a Windows bootloader not finding anything it recognizes to boot, rather than the BIOS not finding anything, suggesting your installations may not have been replacing Windows MBR code on the Linux disk.

Does the BIOS have a mode choice between Windows, and Other OS or not Windows? If yes, set it to Other.

This could be an instance of mismatch between installation type and BIOS settings. Do you know whether this old laptop has a UEFI BIOS? If it does, I suggest to leave CSM (legacy MBR support) mode disabled, then install one more time, being sure the installer does indeed boot in UEFI mode and partition using GPT, and do this installation with only one disk installed.
 
1 members found this post helpful.
Old 02-06-2024, 05:04 PM   #3
Targa9
LQ Newbie
 
Registered: Feb 2024
Posts: 6

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by mrmazda View Post
Your description is rather sketchy, making it hard to tell what transpired after boot failed. What lead you to choose the "fixes" you tried?

Is Windows still installed on one of the two disks? If yes, it may be instructive to remove that disk and try booting Linux.

Using F12 at POST time, do you get a menu that offers a selection of more than one OS to boot or disk to boot from?

"operating system not found" IIRC may be a result of a Windows bootloader not finding anything it recognizes to boot, rather than the BIOS not finding anything, suggesting your installations may not have been replacing Windows MBR code on the Linux disk.

Does the BIOS have a mode choice between Windows, and Other OS or not Windows? If yes, set it to Other.

This could be an instance of mismatch between installation type and BIOS settings. Do you know whether this old laptop has a UEFI BIOS? If it does, I suggest to leave CSM (legacy MBR support) mode disabled, then install one more time, being sure the installer does indeed boot in UEFI mode and partition using GPT, and do this installation with only one disk installed.
Thanks for the reply. The drive was "erased" during the Linux installations so it's only Linux, specifically Mint right now. I don't think the BIOS is UEFI.

I will attach 4 photos of the BIOS. The first two are the same page because there's more information when you "scroll" down.
Attached Thumbnails
Click image for larger version

Name:	IMG_4148.JPG
Views:	17
Size:	108.4 KB
ID:	42526   Click image for larger version

Name:	IMG_4149.JPG
Views:	12
Size:	103.5 KB
ID:	42527   Click image for larger version

Name:	IMG_4150.JPG
Views:	15
Size:	101.8 KB
ID:	42528   Click image for larger version

Name:	IMG_4151.JPG
Views:	12
Size:	99.5 KB
ID:	42529  
 
Old 02-06-2024, 06:10 PM   #4
mrmazda
LQ Guru
 
Registered: Aug 2016
Location: SE USA
Distribution: openSUSE 24/7; Debian, Knoppix, Mageia, Fedora, others
Posts: 5,859
Blog Entries: 1

Rep: Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074Reputation: 2074
I don't think it's UEFI, not least because every UEFI BIOS I've encountered has a GUI mode interface, which yours is not, but where it would be apparent is in the boot section that you didn't image.
 
Old 02-06-2024, 06:49 PM   #5
syg00
LQ Veteran
 
Registered: Aug 2003
Location: Australia
Distribution: Lots ...
Posts: 21,147

Rep: Reputation: 4124Reputation: 4124Reputation: 4124Reputation: 4124Reputation: 4124Reputation: 4124Reputation: 4124Reputation: 4124Reputation: 4124Reputation: 4124Reputation: 4124
It's BIOS.
I went and chiselled the dusk off a slightly older model with a A13 BIOS level. I was worried it might be a BIOS message that it couldn't find a M$oft boot record, but I have grub2 as my loader, so it shouldn't be that.
Given it's MBR, not gpt, you might need an insmod for part_msdos - and I'm guessing the kernel will be at /boot/vmlinuz
 
Old 02-06-2024, 06:56 PM   #6
Targa9
LQ Newbie
 
Registered: Feb 2024
Posts: 6

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by mrmazda View Post
I don't think it's UEFI, not least because every UEFI BIOS I've encountered has a GUI mode interface, which yours is not, but where it would be apparent is in the boot section that you didn't image.
Thanks again.
I'll post the BIOS Boot Page here.
Attached Thumbnails
Click image for larger version

Name:	IMG_4154 Bios Boot page.JPG
Views:	13
Size:	56.9 KB
ID:	42530  
 
Old 02-06-2024, 07:13 PM   #7
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,375

Rep: Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593
boot the live usb, open a terminal and post the output of
Code:
sudo parted -l
 
Old 02-06-2024, 07:28 PM   #8
Targa9
LQ Newbie
 
Registered: Feb 2024
Posts: 6

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by colorpurple21859 View Post
boot the live usb, open a terminal and post the output of
Code:
sudo parted -l
Thanks again. I tried that but I think I should be at a different folder or directory. Anyway, I'll post a screen shot.
Attached Thumbnails
Click image for larger version

Name:	IMG_4156 Sudo parted-1.JPG
Views:	16
Size:	82.7 KB
ID:	42531  
 
Old 02-06-2024, 07:54 PM   #9
colorpurple21859
LQ Veteran
 
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,375

Rep: Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593Reputation: 1593
That is a lower case L not a one.
 
Old 02-06-2024, 08:26 PM   #10
Targa9
LQ Newbie
 
Registered: Feb 2024
Posts: 6

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by syg00 View Post
It's BIOS.
I went and chiselled the dusk off a slightly older model with a A13 BIOS level. I was worried it might be a BIOS message that it couldn't find a M$oft boot record, but I have grub2 as my loader, so it shouldn't be that.
Given it's MBR, not gpt, you might need an insmod for part_msdos - and I'm guessing the kernel will be at /boot/vmlinuz
Thanks for the reply. When Windows still ran on MSDOS, I got pretty familiar and comfortable with the DOS commands I used regularly. With Linux, I am completely a Noobie! So much so that I don't even know what to do with "/boot/vmlinuz" or when, where or how to use it.
 
Old 02-07-2024, 02:28 PM   #11
yancek
LQ Guru
 
Registered: Apr 2008
Distribution: Slackware, Ubuntu, PCLinux,
Posts: 10,553

Rep: Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498Reputation: 2498
When you install Ubuntu or Mint with the typical Desktop GUI install, there will be an option for bootloader installation at the bottom of the main window. If you are using the Erase Disk option leave the default. After the install, you did change the boot order in the BIOS from the USB or DVD you used to install to the drive on which you installed.

You're not providing much useful information. You could start with the parted command suggested to LIST the devices and partitions. You could also boot the install DVD/USB of Mint/Ubuntu and go to the site at the link below and download and run the boot repair software. If you do, use the 2nd option described on the page and the Create BootINfo Summary option and post the link you get when it finishes here.
 
Old 02-07-2024, 02:32 PM   #12
rclark
Member
 
Registered: Jul 2008
Location: Montana USA
Distribution: KUbuntu, Fedora (KDE), PI OS
Posts: 493

Rep: Reputation: 182Reputation: 182
I ran into this when I installed KUbuntu 23.10 in a older laptop. Had to change an option in BIOS from Legacy to UEFI and then it booted just fine from the 'just installed' KUbuntu.
 
Old 02-07-2024, 02:33 PM   #13
Targa9
LQ Newbie
 
Registered: Feb 2024
Posts: 6

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by yancek View Post
When you install Ubuntu or Mint with the typical Desktop GUI install, there will be an option for bootloader installation at the bottom of the main window. If you are using the Erase Disk option leave the default. After the install, you did change the boot order in the BIOS from the USB or DVD you used to install to the drive on which you installed.

You're not providing much useful information. You could start with the parted command suggested to LIST the devices and partitions. You could also boot the install DVD/USB of Mint/Ubuntu and go to the site at the link below and download and run the boot repair software. If you do, use the 2nd option described on the page and the Create BootINfo Summary option and post the link you get when it finishes here.
Thank you and thanks to all who replied. I found the solution on another forum and here's the solution that worked:

It was suggested I either install LM20.3 and then upgrade to LM21 or follow this guide:
https://foxclone.org/guides.html

I went with the foxclone guide and it worked. I did discover a "klink" that I worked around: When it got to clicking "change" to edit the partition, after hitting OK, on the next pop up window, INSTEAD of hitting continue (which hung forever), I hit GO BACK so I could make sure the Format box was checked, and chose the "Device for boot loader installation", (even though it had defaulted to the correct location anyway. Then I could click on "INSTALL" whereas it was previously grayed out.
 
  


Reply



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] No package 'x11' found No package 'xext' found No package 'xdamage' found No package 'xfixes' found No package 'x11-xcb' found Jigsaw Linux From Scratch 14 02-23-2021 08:35 PM
Installing Arch Linux: Operation System not found archmcd Linux - Laptop and Netbook 7 12-04-2014 07:07 AM
SIOCSIFFLAGS: Operation not permitted SIOCSIFFLAGS: Operation not permitted sushan1982 Linux - Wireless Networking 1 01-01-2012 08:04 PM
Directory not found; -xzvf not found; Makefile not found RealGomer Linux - Software 4 09-20-2010 10:02 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie

All times are GMT -5. The time now is 12:33 PM.

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