Finally my problem is solved.
The problem was that I had to reinstall grub in the MBR of the first
disk, *telling it that /boot was in a different partition*. I booted
from a LiveCD (I was using GParted's one, as it booted faster than the rescue
option of Debian's LiveCD, and I had to boot quite a
On Sat, Sep 15, 2007 at 10:39:35AM +0200, Hans Hofker wrote:
> >
> I think the 'root' command should specify the partition where the boot
> directory is located, so it should be (hd1,0) rather than (hd1,1).
> Furthermore, the kernels are not located on the hdd2-partition, so they
> are not in (
Victor Munoz wrote:
Currently, my /etc/fstab is:
/dev/hdd2 / ext3 defaults,errors=remount-ro 0 1
/dev/hdd1 /boot ext3 defaults,errors=remount-ro 0 2
/dev/hdd3 none swap sw 0 0
proc /proc proc defaults 0 0
/dev/hda /media/cdrom udf,iso9660 user,noauto 0 0
/dev/fda /media/floppy auto rw,user,noaut
On Mon, Sep 10, 2007 at 09:50:49AM -0700, Andrew Sackville-West wrote:
> I'm not positive that gparted will move the beginning of a partition,
> but its certainly worth a shot. This is what I'd do:
>
> 1. Backup everything.
> 2. Review 1 several times.
> 3. launch a live-cd (knoppix or somesuch)
On Mon, Sep 10, 2007 at 02:18:18AM -0400, Victor Munoz wrote:
> On Sun, Sep 09, 2007 at 02:12:19PM -0700, Andrew Sackville-West wrote:
> >
> > yup. probably up until now you've always had this problem, but the
> > kernels happened to be written within the first 1024 cylinders and
> > thus caused n
On Sun, Sep 09, 2007 at 02:12:19PM -0700, Andrew Sackville-West wrote:
>
> yup. probably up until now you've always had this problem, but the
> kernels happened to be written within the first 1024 cylinders and
> thus caused no problem. Also, the same with menu.lst, it was probably
> within that b
Mumia W.. wrote:
>
> Yes, create a small (~1GB) /boot partition at the head of the 160GB
> disk. I always had to do that with my old 486 computer because its BIOS
> was restricted by the 1024-cylinder limit.
>
1GB /boot would be a waste of space. I have 4 kernel versions installed
and am using o
On Sun, Sep 09, 2007 at 04:02:35PM -0400, Victor Munoz wrote:
> On Sun, Sep 09, 2007 at 11:00:24AM -0700, Andrew Sackville-West wrote:
> >
> > One thing that might be helpful is what does the BIOS call those
> > drives? In your bios setup screen there will be the usual table of
> > harddrives and
On 09/09/2007 03:02 PM, Victor Munoz wrote:
On Sun, Sep 09, 2007 at 11:00:24AM -0700, Andrew Sackville-West wrote:
[...]
So your suggestion would be to repartition the disk, leaving a small
boot partition at the beginning of the 160G disk?
Anyway, the motherboard is not new.
lspci -v:
00:00
On Sun, Sep 09, 2007 at 11:00:24AM -0700, Andrew Sackville-West wrote:
>
> One thing that might be helpful is what does the BIOS call those
> drives? In your bios setup screen there will be the usual table of
> harddrives and their positions on the motherboard, as the bios sees
> them. Can you pro
On Sun, Sep 09, 2007 at 06:46:14PM +0100, Wackojacko wrote:
> >
> Not necessarily. Grub uses /boot/grub/device.map to identify which HDD
> maps to which (hd?). It might be useful to see the OP's device.map
> file, but grub could just ignore hda and hdb as they are not HDD.
>
I did post it in
On Sun, Sep 09, 2007 at 01:15:58PM -0400, Wayne Topa wrote:
> >
> > Well, it was not me anyway :-). grub decided it was time to get
> > confused last week, after months of normalVoperation.
>
>
> title Debian GNU/Linux, kernel 2.6.22-2-686
> --- > root(hd1,0)
> > kern
On Sun, Sep 09, 2007 at 01:15:58PM -0400, Wayne Topa wrote:
> Victor Munoz([EMAIL PROTECTED]) is reported to have said:
> > On Sat, Sep 08, 2007 at 10:53:20PM -0400, Wayne Topa wrote:
> It might be just me, as I have never seen/heard of a system set up
> that way. I have always put my HD's on th
On Sat, Sep 08, 2007 at 09:32:03PM -0400, Victor Munoz wrote:
> On Sat, Sep 08, 2007 at 09:07:39PM -0400, Victor Munoz wrote:
> >
> > Disk /dev/hdd: 160.0 GB, 160041885696 bytes
> > 255 heads, 63 sectors/track, 19457 cylinders
> > Units = cylinders of 16065 * 512 = 8225280 bytes
> > Disk identifie
Wayne Topa wrote:
title Debian GNU/Linux, kernel 2.6.22-2-686
--- > root(hd1,0)
> kernel /boot/vmlinuz-2.6.22-2-686 root=/dev/hdd1 ro
initrd /boot/initrd.img-2.6.22-2-686
savedefault
Grub did the 2 --> Lines? The root line says hdb and the kernel
Victor Munoz([EMAIL PROTECTED]) is reported to have said:
> On Sat, Sep 08, 2007 at 10:53:20PM -0400, Wayne Topa wrote:
> > It's late and I'm tired but something looks wrong to me.
> > Do you have 4 hard drives or is this one (1) HD with
> >
> > You say /dev/hdd [(hd1,0)]
> >
> > But to me /dev
On Sun, Sep 09, 2007 at 07:05:39AM -0500, Mumia W.. wrote:
>
> Hello Victor. I would try reinstalling the failing kernels; if you do
> this, copy the kernel .deb files out of /var/cache/apt/archives first,
> because those kernels are probably no longer available on the Debian
> mirrors.
I tried
On 09/08/2007 11:40 PM, Victor Munoz wrote:
[...]
Well, it was not me anyway :-). grub decided it was time to get
confused last week, after months of normal operation.
Victor
Hello Victor. I would try reinstalling the failing kernels; if you do
this, copy the kernel .deb files out of /var
On Sat, Sep 08, 2007 at 10:53:20PM -0400, Wayne Topa wrote:
> It's late and I'm tired but something looks wrong to me.
> Do you have 4 hard drives or is this one (1) HD with
>
> You say /dev/hdd [(hd1,0)]
>
> But to me /dev/hda -> (hd0,0)
> /hdb -> (hd1,0)
> /hdc ->
Victor Munoz([EMAIL PROTECTED]) is reported to have said:
> Hello. It's been about a week that I've been unable to boot normally.
> Every time I get the grub prompt, and then I have to go through the
> sequence of commands "root/kernel/initrd/boot". I understand that this
> may occur due to some de
On Sat, Sep 08, 2007 at 09:07:39PM -0400, Victor Munoz wrote:
>
> Disk /dev/hdd: 160.0 GB, 160041885696 bytes
> 255 heads, 63 sectors/track, 19457 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
> Disk identifier: 0x00014f58
>
>Device Boot Start End Blocks Id
On Sat, Sep 08, 2007 at 05:45:03PM -0700, Andrew Sackville-West wrote:
>
> can you manually load the menu.lst?
>
> grub> configfile (hd1,0)/grub/menu.list
>
> should get you a menu. Its at least easier than type all the root,
> kernel etc lines.
Thanks for the tip, didn't know the command, but n
On Sat, Sep 08, 2007 at 07:45:36PM -0400, Victor Munoz wrote:
> Hello. It's been about a week that I've been unable to boot normally.
> Every time I get the grub prompt, and then I have to go through the
> sequence of commands "root/kernel/initrd/boot". I understand that this
> may occur due to som
Hello. It's been about a week that I've been unable to boot normally.
Every time I get the grub prompt, and then I have to go through the
sequence of commands "root/kernel/initrd/boot". I understand that this
may occur due to some defective file, but I can't see anything
abnormal in menu.lst, devic
24 matches
Mail list logo
