machine stops at GRUB screen during boot process
in [General Linux]
|
Prev: NYC LOCAL: Tuesday 27 April 2010 NYLUG: Squeak Hack Fest
Next: Fancast compared to Hulu plus my not so quick look at a bunch of the Linux OS
From: Rahul on 29 Apr 2010 17:58 Robert Heller <heller(a)deepsoft.com> wrote in news:RMednVLRfbO- bETWnZ2dnUVZ_r6dnZ2d(a)posted.localnet: > Once the kernel starts, the kernel will (at some point) load the > aic79xx driver (probably from the initrd), which will probe the PCI bus > and see the external RAID card. So long as the /boot is mounted using > a LABEL= option in /etc/fstab (the root file system is mounted from a I am also getting the feeling that mounting any device without the LABEL= option was asking for trouble. Right now I have only the /boot device mounted that way but I intend to use a LABEL for /home and everything else that I might mount! Incidently for the stuff that's on LVM is the "/dev/VolGroup00/LogVol00 /" syntax safe from mismatchs? Or can something that shows up as a LogVol00 get reassigned at bootime as well if some other devices were to be added? -- Rahul
From: Dave U. Random on 29 Apr 2010 18:22 "R" =3D=3D Rahul <nos...(a)nospam.invalid>: R> I got the machine running again. Sort of a hack though for now. If it = helps=20 R> anyone someday: R>=20 R> 1. Removed the external RAID array. R> 2. Boot machine. Now it sees only sda and can boot from /dev/sda1.=20 R> 3. Now connect the external RAID array. It still is not seen in /dev R> 4. rmmod aic79xx R> 5. modproble aic79xx R>=20 R> Now I can see the external RAID array as /dev/sdb1 which is easily mou= nted=20 R> to /home Why don't you blacklist the aic79xx module, so that it doesn't get loaded automatically? You can then execute appropriate commands at some later point of the booting process (eg. from /etc/rc.local) to a) load the module and b) mount the /home partition.
From: Bit Twister on 29 Apr 2010 18:33 On Thu, 29 Apr 2010 21:58:01 +0000 (UTC), Rahul wrote: > I am also getting the feeling that mounting any device without the LABEL= > option was asking for trouble. Right now I have only the /boot device > mounted that way but I intend to use a LABEL for /home and everything else > that I might mount! Yep, I set mine up to run labels. Running with /dev/xxxx can have fstab problems when dinking around with partition/mount order. UUID is pretty static until you reformat and forget to set old UUID. :-( Now if grub was able to use labels instead of (hd1,4) we could be setting pretty. $ grep label /boot/grub/menu.lst kernel (hd1,4)/boot/vmlinuz BOOT_IMAGE=beta1 root=LABEL=alpha vga=794 $ grep alpha /etc/fstab LABEL=alpha / ext3 relatime 1 1 $ grep swap /etc/fstab LABEL=swap swap swap defaults 0 0
From: Dave U. Random on 29 Apr 2010 18:42 "R" =3D=3D Rahul <nos...(a)nospam.invalid>: R> But I can only do this if my external RAID array is disconnected. R> If I connect it the grub order seems to get messed up again. Thinking out of the box here: have you tried using LILO instead?
From: Robert Heller on 29 Apr 2010 18:48
At Thu, 29 Apr 2010 21:58:01 +0000 (UTC) Rahul <nospam(a)nospam.invalid> wrote: > > Robert Heller <heller(a)deepsoft.com> wrote in news:RMednVLRfbO- > bETWnZ2dnUVZ_r6dnZ2d(a)posted.localnet: > > > Once the kernel starts, the kernel will (at some point) load the > > aic79xx driver (probably from the initrd), which will probe the PCI bus > > and see the external RAID card. So long as the /boot is mounted using > > a LABEL= option in /etc/fstab (the root file system is mounted from a > > I am also getting the feeling that mounting any device without the LABEL= > option was asking for trouble. Right now I have only the /boot device Yes. Partitularly for SCSI devices which might get 'moved around'. Note this in a way also applied to USB mass storage devices and also hot-plugged SATA disks. Unless you have precise control of the exact order of these devices are (un-)plugged, their /dev/sd<mumble> names will not be predictable. > mounted that way but I intend to use a LABEL for /home and everything else > that I might mount! Yes, a good idea. > > Incidently for the stuff that's on LVM is the "/dev/VolGroup00/LogVol00 /" > syntax safe from mismatchs? Or can something that shows up as a LogVol00 > get reassigned at bootime as well if some other devices were to be added? You don't have to worry about the LVM volumns 'moving around' because of device discovery order -- the volumn group works like a e[234]fs LABEL. You should be using LABEL= for all file systems on 'bare' on bare partititions (eg /dev/sd<mumble>1 for /boot). (You *can* use LABEL= for file systems on LVM volumns, but you don't *have* to.) -- Robert Heller -- 978-544-6933 Deepwoods Software -- Download the Model Railroad System http://www.deepsoft.com/ -- Binaries for Linux and MS-Windows heller(a)deepsoft.com -- http://www.deepsoft.com/ModelRailroadSystem/ |