[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Disk Errors on 2nd Disk in Dual-Boot Debian/Solaris System

Hi Ivan,
Thanks for your comments. Please see responses below
On Thu, Jan 20, 2011 at 5:49 PM, Ivan Jager <aij+debian@mrph.org> wrote:
On Thu, Jan 20, 2011 at 05:03:40PM -0500, RR scribbled:
> On Thu, Jan 20, 2011 at 4:47 PM, brian m. carlson <
> sandals@crustytoothpaste.net> wrote:
> > You need to fix /etc/fstab so that your /boot partition is properly
> > referenced.  Otherwise, when you upgrade your kernel, the data will be
> > written in the wrong place and you won't be able to use the new kernel.
> > If you can boot Debian, then your /etc/silo.conf probably contains the
> > correct location of your /boot partition, so you should use that.
> >
> Right, so that's what I figured as it's complaining about it not being an
> ext2 FS, which it obviously isn't, so we're ok there.

No, you still need to fix that.

> w.r.t to silo.conf, it's really bizarre. As per your instructions, once In
> debian, I went into /etc and found the following:
> DebSparcx64:/etc# ls -l silo.conf
> lrwxrwxrwx 1 root root 17 2010-12-26 05:49 silo.conf -> ../boot/silo.conf
> But we already know that my /boot is empty. So where the hell is silo.conf??
> and when I mount my Solaris Disk i.e. /dev/sdb1 on to /mnt within Debian, I
> still can't find either the bootloader for Debian OR silo.conf. I'm really
> confused!

Remember how you were having errors mounting /boot? Of course you
can't find things in /boot if it's not mounted. And why would you
be looking for it on the Solaris disk? Did you forget you swapped
the two disks?
I did, and I didn't, see comment below as to what I mean :(

Now, remember how you said you swapped disk1 and disk2 "for
convenience"? I don't really see how it is more convenient if it
didn't work. If your /boot used to be /dev/sdb1 it would now be
/dev/sda1, so if you want to keep the disks in this configuration
you should probably update /etc/fstab to reflect that.
Alternately you could put the disks back in the order they were
when you installed the system.

OMG Ivan, you're so smart!! (and I don't mean that sarcastically :) So I didn't forget that I swapped the disks when I was "talking" about it! But I did forget about it, since it didn't occur to me that sdb1 is now sda1 and when my fstab says,
/dev/sdb1       /boot           ext2    defaults        0       2
it REALLY is saying that it's on the disk which WAS Disk2 coz it's not auto-magiclaly gonna edit itself when I go swapping disks!!. So after your comment, I did this
mount /dev/sda1 /boot....and guess what???
DebSparcx64-01:/# cd /boot
DebSparcx64-01:/boot# ls -ltr
total 10192
-rw-r--r-- 1 root root     512 2008-08-24 19:26 ultra.b
-rw-r--r-- 1 root root   71858 2008-08-24 19:26 silotftp.b
-rw-r--r-- 1 root root    7720 2008-08-24 19:26 isofs.b
-rw-r--r-- 1 root root     692 2008-08-24 19:26 ieee32.b
-rw-r--r-- 1 root root    1024 2008-08-24 19:26 generic.b
-rw-r--r-- 1 root root     512 2008-08-24 19:26 first.b
-rw-r--r-- 1 root root    1024 2008-08-24 19:26 fd.b
-rw-r--r-- 1 root root   56992 2010-11-21 19:43 config-2.6.26-2-sparc64-smp
-rw-r--r-- 1 root root 1807389 2010-11-21 22:05 vmlinuz-2.6.26-2-sparc64-smp
-rw-r--r-- 1 root root 1137070 2010-11-21 22:05 System.map-2.6.26-2-sparc64-smp
drwxr-xr-x 2 root root   12288 2010-12-26 05:13 lost+found
lrwxrwxrwx 1 root root      28 2010-12-26 05:16 vmlinuz -> vmlinuz-2.6.26-2-sparc64-smp
-rw-r--r-- 1 root root 7203342 2010-12-26 05:16 initrd.img-2.6.26-2-sparc64-smp
lrwxrwxrwx 1 root root      31 2010-12-26 05:16 initrd.img -> initrd.img-2.6.26-2-sparc64-smp
-rw-r--r-- 1 root root     193 2010-12-26 05:49 silo.conf
-rw-r--r-- 1 root root   74240 2010-12-26 05:49 second.b
-rw-r--r-- 1 root root    7680 2010-12-26 05:49 old.b
lrwxrwxrwx 1 root root       1 2010-12-26 05:49 etc -> .
lrwxrwxrwx 1 root root       1 2010-12-26 05:49 boot -> .
Ok, I will now edit fstab so it mounts /boot properly. I just don't understand how the system was booting up properly though. It must have something to do with the debian installer writing something at a level lower than the OS and Disk partitions???
I don't know how Solaris will deal with it, but I wouldn't be too
suprised if you need to update something in your Solaris install
too. Have you tried booting it since you swapped the disks?

Last of all, what is this "Debian x64" thing you installed?
haha, umm it's like the 64-bit Sparc port of Debian lenny: http://www.debian.org/ports/sparc/
Thank You SO Much!! Now if you could read the other posts and help me figure out the missing parition disk space that would be awesome :)

Reply to: