Linux - NewbieThis 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!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
means to put the output somewhere where we can see it as you do.
You can redirect out to a file with something like
fdisk -l > fdisk.txt
If you move the file fdisk.txt to your FAT partition, you can include in it a post here, between CODE tags please.
Using CODE tags preserves the formatting.
This 'redirection' works with most commands. If the file is large, you should put it on a pastebin site and post the URL here so we can find it. Its very important that you do not copy type as we will spend time picking up on your typing errors.
Taken together, the results of fdisk -l and ls /dev/sd[abcd]? show that the ubuntu kernel sees all your partitions but fdisk does not. You are almost certainly using GPT partition tables.
Google suggests that you need grub2 (still experimental) or some other boot loader to boot from a disk with a GPT partition table. Parted (or gparted) is GPT aware. Try looking at yuor partition table with that tool.
Lilo may also work with GPT, as it does not try to read any filesystems, to boot the system it reads a block list into RAM.
I think your install worked but grub cannot boot it.
Thank you for your reply.
Since I am not an expert in computers, I do not know, really, what I should do to restore my system to the state it was before I attempted to install Ubuntu.
I can only boot with the live disk. I cannot reload Windows since Windows performs a reboot during the setup procedure and them I'm back at the beginning.
How can I get rid of the grub error 21 that appears when I reboot without the live disk?
I do not know how to change anything in the bios.
I do not necessarily want to have Linux on my PC, I can work further with Windows. But I made the trial because one told me that Linux was better.
Thank you for your efforts, and patience, but I am really in trouble if I cannot access my Windows-based programs.
Do you have options on your W2K installation CD other than install? With xp and/or vista I believe you have a recovery option. If you have that you can try accessing it and going to a command line and typing the "fixmbr" and/or "fixboot" commands to repair master boot record for windows.
You have a Grub file in your master boot record but no partition with the rest of the Grub bootloader files per your previous output because your installation of Linux was not successful. This is the cause of the Error 21.
You could try googling "SystemRescueCD" and use that to recover data. I haven't used windows for a long time but others here may have some ideas. You might go to the microsoft site and do a search there.
Thank you for your suggestion with to try with a recovery disk.
I managed to fix the Bios with fixboot and fixMBR and could reinstall Windows 2000 and to boot with it. Error 21 disappeared.
I still have one problem. When Windows is loaded, it detects a mass storage device (my usb-harddisk with ubuntu partitions on it) but gives it no name (for example e This means that it does not appear in the root directory of windows explorer and that I cannot access it.
How can I make this harddisk visible so that I can, if necessary, format it as a normal harddisk and use the 160 GB space it has on it?
Can I do this with the live CD of Ubuntu?
Thank you for a solution of this, I hope, ultimate problem.
It is my understanding that windows operating systems do not have the ability to read or write to Linux filesystems and it will be necessary to download some third party software. You should be able to use the Ubuntu Live CD and use GParted (which comes with Ubuntu) to create an ntfs filesystem on that drive so your windows system will be able to see it. You can use GParted to create partitions and filesystems.
Thanks to your suggestion I could with the live CD (with GParted) create a new partition (MSDOS) on my usb-harddrive, and create a ntfs-filesystem.
Windows could thus recognize my lost disk.
I lost all data on this disk but had backups.
I also lost about 10 GB of this disk, GB that with GParted were qualified as allocated. I still have 150 GB.
Thank you very much for your valued help and patience with a newbie in the Linux-experience.
It is a pitty that I could not install Linux successfully, but I can still use the live CD and experience the workings of this system.
Get Knoppix if you want the full Linux experience from CD/DVD. Its slower that a real install, as its on much slower optical media and files are compressed, which needs CPU time to decompress.
None the less, there is a lot of Open Source Software there for you to try.
You probably installed Linux properly but for reasons that we could not establish, you could not get it to boot.