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!
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I just installed Ubuntu and once it rebooted I got this screen.
Booting ‘ubtuntu, kernel 2.6.15-23-386’
Root (hd0,1)
Filesystem type is ext2fs, partition type 0x83
Kernel /vmlinuz-2.16.15-23-386 root=/dev/i2o/hda4 ro quiet splash
[Linux-bzImage, setup=0x1c00, size=0x15774d]
Initrd initrd.img-2.6.15-23-386
[Linux-initrd@0x1f86c000, 0x67384 bytes]
Savedefault
Boot
Uncompressing Linux… Ok, booting the kernel
ALERT1 /dev/i2o/hda4 does not exist. Dropping to a shell!
BusyBox v1.01 (Debian 1:1.01-4ubuntu3) Built-in Shell (ash)
Enter ’help’ for a list of build-in commands.
/bin/sh: can’t access tty: job control turned off
#
For some reason grub is looking at my scsi raid as /dev/i2o/hda4 but during the install it saw it as sdb.
Because I am running scsi raid I wanted to run XFS, but I know GRUB and XFS do not get along to well, so during the partitioning I created a small partition for just /boot, and formatted it as EXT3. I then created 768 for swap and did the rest of the drive for XFS (the very beginning of my drive is NTFS for windows XP, grub boots that just fine.
I grabbed my knoppix disk and checked qtparted and saw that for some reason the NTFS partition is active.
Disk /dev/sda: 164.6 GB, 164696555520 bytes
255 heads, 63 sectors/track, 20023 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sda1 * 1 20022 160826683+ 7 HPFS/NTFS
Disk /dev/sdb: 73.4 GB, 73407660032 bytes
255 heads, 63 sectors/track, 8924 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/sdb1 * 1 6374 51199123+ 7 HPFS/NTFS
/dev/sdb2 6375 6405 249007+ 83 Linux
/dev/sdb3 6406 6498 747022+ 82 Linux swap / Solaris
/dev/sdb4 6499 8924 19486845 83 Linux
When I install Ubuntu I did not have my sata drive in, but When I have my sata disk plugged in Grub will only boot into windows. It freezes if I a choose any of the linux options (I gave it plenty of time, at least 15-20 minutes) I tried the press numlock and the light didn't come on, I pulled the sata hard drive because grub couldn't write to the MBR if it was installed. Is there anyone to manual write LILO? Where would I start?
There is nothing in the fdisk output that tells us that we are using raid---except the sda, sdb IDs. What happens if you modify the grub config file (/boot/grub/menu.lst) to point to the Linux partition the same way that fdisk is seeing it?
ie change from this:
Root (hd0,1)
Filesystem type is ext2fs, partition type 0x83
Kernel /vmlinuz-2.16.15-23-386 root=/dev/i2o/hda4 ro quiet splash
To this:
Root (hd1,1)
Filesystem type is ext2fs, partition type 0x83
Kernel /vmlinuz-2.16.15-23-386 root=/dev/sdb2 ro quiet splash
In these lines, you'll note that grubspeak for drive and partition #s start at 0--everywhere else, they start at "a" or "1"
Regardless of this suggestion, don't confuse the issue by bringing in your SATA drive, lilo, etc.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.