Sponsored Content
Top Forums UNIX for Advanced & Expert Users The system will not keep sda as my boot drive Post 302568277 by hytron on Thursday 27th of October 2011 12:26:52 AM
Old 10-27-2011
The system will not keep sda as my boot drive

Hi everyone!

A very frustrating night!!! I installed a new linux server on my system that has IDE drives and SATA drives. At the time of installation I only had IDE drive plugged in and that is where I install the linux. Everything works fine until I shut the system down and plug in my SATA backup drive. During boot, kernel panic appears and the system will not boot! My backup drive appears to be sda now!!!! And of course since my fstab has sda1 listed as the root partition it fails. I know you can assign certain drives using udev, but this happens before the system even boots.

The real question is, and I have been trying to find it all over the net and I am very surprised that nobody has even asked, and that is:

How can I keep my sda to be ALWAYS that IDE drive? Just like in the good old days when hda was always hda and as long as it is connected to the first IDE controller and it is the first drive it will always be hda and nothing else. This sda, sdb issue is really very frustrating, or I am missing something here?

Please help!!!!
 

10 More Discussions You Might Find Interesting

1. Solaris

Cloned drive won't boot ?

Solaris system version 6 I cloned the drive using the DD command. Using the format command and examining the partitions, all looks the same as the original drive. Problem: When I attach the cloned drive as the master, and only drive in system, it will not boot. Error messages: ... (9 Replies)
Discussion started by: HikerLT
9 Replies

2. Ubuntu

Boot Floppy made in external drive

there is probably another post about this, i just can't find it on unix.com or google. basically, i am trying to make a boot floppy via CLI/terminal. the problem is that i use an external drive. when i do the first couple of steps, i get rejected. when i do the mounting and unmounting, all the... (4 Replies)
Discussion started by: Texasone
4 Replies

3. Solaris

Solaris 10 and zfs on boot drive

Has anyone installed Solaris 10 10/08 and enabled zfs on the boot drive? We're considering enabling zfs boot on some upcoming production machines and I was curious if anyone here has experiences they wish to share. (1 Reply)
Discussion started by: dangral
1 Replies

4. Solaris

Boot options - DVD drive read error

I was wondering if there was a way to boot from openboot from the dvd drive. I was thinking about imaging the dvd to a blank drive and going about it that way. I just need to do a flash install. (5 Replies)
Discussion started by: adelsin
5 Replies

5. Solaris

Boot Solaris off of an old external hard drive

Hi Folks, First a little background, I am working on a ship that operates in the Indian Ocean and Persian/Arabian gulf area. We had a Sunblade 2000 that finally died. The Video board burned up and I guess damaged the mother board. So we ordered 2 rebuilt 2000s one as a spare. Due to mounting... (1 Reply)
Discussion started by: Sean.kelly
1 Replies

6. Homework & Coursework Questions

Changing Drive to be /Boot

Posted in wrong area, post can be deleted, my appologies. (0 Replies)
Discussion started by: derbarbarian
0 Replies

7. Solaris

Help Mirroring Boot drive

How do I mirror the boot drive, which I believe is /dev/dsk/c1t0d0s0. Filesystem size used avail capacity Mounted on /dev/dsk/c1t0d0s0 16G 457M 15G 3% / /devices 0K 0K 0K 0% /devices ctfs 0K 0K 0K ... (7 Replies)
Discussion started by: Kjons76
7 Replies

8. Hardware

[Solved] Boot Lockup After Drive Swap

Hey All, Im using Fedora 2.6 (which is cannot be changed for compatibility reasons). I cloned a drive from a different server and when i added this drive to a new box, during startup it hangs on "Configuring Kernel Parameters:" Is there any way to bypass this process and still boot... (0 Replies)
Discussion started by: robfwauk
0 Replies

9. UNIX for Dummies Questions & Answers

boot option Available partitions 0b00 1048575 sr0 driver:sr 0800 488386584 sda driver:sd

Help, suspect hacked via serial or electric! any ideas on error "Pid:1, comm:swapper Tainted:G W 2.6.35-22 generic #33 -unbutu device = "(null)" or unknown-blocklist(8.1) please append a correct "root"boot option Available partitions 0b00 1048575 sr0 driver:sr 0800 488386584 sda driver:sd. Thanks... (3 Replies)
Discussion started by: kryclear
3 Replies

10. Solaris

Hard Drive Copy results in differences on boot

I have an old Pentium 4 PC running Solaris 9. The system has two 40gig IDE hard drives. I removed the drives and, using a hard disk duplicating device, "cloned" both drives. I installed the new drives in the PC. The system boots but I get a message that X-Term will not run on the console. If I... (4 Replies)
Discussion started by: ddogarmyman
4 Replies
HD(4)							     Linux Programmer's Manual							     HD(4)

NAME
hd - MFM/IDE hard disk devices DESCRIPTION
The hd* devices are block devices to access MFM/IDE hard disk drives in raw mode. The master drive on the primary IDE controller (major device number 3) is hda; the slave drive is hdb. The master drive of the second controller (major device number 22) is hdc and the slave hdd. General IDE block device names have the form hdX, or hdXP, where X is a letter denoting the physical drive, and P is a number denoting the partition on that physical drive. The first form, hdX, is used to address the whole drive. Partition numbers are assigned in the order the partitions are discovered, and only nonempty, nonextended partitions get a number. However, partition numbers 1-4 are given to the four partitions described in the MBR (the "primary" partitions), regardless of whether they are unused or extended. Thus, the first logi- cal partition will be hdX5. Both DOS-type partitioning and BSD-disklabel partitioning are supported. You can have at most 63 partitions on an IDE disk. For example, /dev/hda refers to all of the first IDE drive in the system; and /dev/hdb3 refers to the third DOS "primary" partition on the second one. They are typically created by: mknod -m 660 /dev/hda b 3 0 mknod -m 660 /dev/hda1 b 3 1 mknod -m 660 /dev/hda2 b 3 2 ... mknod -m 660 /dev/hda8 b 3 8 mknod -m 660 /dev/hdb b 3 64 mknod -m 660 /dev/hdb1 b 3 65 mknod -m 660 /dev/hdb2 b 3 66 ... mknod -m 660 /dev/hdb8 b 3 72 chown root:disk /dev/hd* FILES
/dev/hd* SEE ALSO
chown(1), mknod(1), sd(4), mount(8) COLOPHON
This page is part of release 3.27 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 1992-12-17 HD(4)
All times are GMT -4. The time now is 10:31 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy