On Tue, Nov 01, 2011 at 04:56:17PM -0500, Bruce Dubbs wrote:
> Ken Moffat wrote:
> >  This is embarrassing, but I guess I can live with that if someone
> > is abie to help diagnose the problem :)
> > 
> >  Built LFS-6.8 on a desktop, updated all the desktop packages,
> > decided it was a 'good enough' version to use to update my server.
> > The server's old system runs 2.6.32.43, so I changed --enable-kernel
> > to 2.6.32 (my desktops had something newer).  A comment by Bruce
> > later made me wonder if udev-166 might be too new for 2.6.32.
> 
> I don't know what's happening, but the first thing I'd try is 
> --enable-kernel=2.6.25 in glibc.
> 
 I was happily using --enable-kernel=2.6.36 on the desktop
(using /dev/sda* partitions).  In any case, the comment was re trying
to run on 2.6.32, and the problem persists running 3.0.4.

> >  After weeks sorting out what to build for the server, and how, and
> > how much I actually want to be working when it boots, I've now got it
> > booting.  Looks good, except that nothing other than '/' is mounted
> > - no /home, nor other separate partitions.  At first I thought it
> > was a problem with LABEL= in /etc/fstab, then I realised the devices
> > are not apparent in /dev.
> 
> Is the kernel finding the device?  That is:
> 
> [    2.708862] sd 0:0:0:0: [sda] 625142448 512-byte logical blocks: (320 
> GB/298 GiB)
> [    2.709345] sd 0:0:0:0: [sda] Write Protect is off
> [    2.709593] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
> [    2.709636] sd 0:0:0:0: [sda] Write cache: enabled, read cache: 
> enabled, doesn't support DPO or FUA
> 
> Um, I see from your 2nd post that it is.
> ...
> 
> [    2.890770]  sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 
> sda10 sda11 sda12 sda13 sda14 sda15 sda16 sda17 >
> 
> But I don't see this.
> 
 Copying by hand:
Nov  1 19:08:47 milliways kernel:  sda: sda1 sda2 < sda5 sda6 sda7 sda8 sda9 >

(it's on the line after 'sd 1:0:0:0 (sdb) Attached SCSI disk')

> >  This was using the same 2.6.32.43 config as on the old system (but,
> > a newer toolchain).  On a hunch, I decided to try linux-3.0.4 which
> > I had handy - same config, then make oldconfig and accept all the
> > defaults.  Booting that made no difference, so I'm back in the old
> > system again.
> > 
> >  What the log shows is that the disks show up, but for some reason
> > /dev/sd* (and /dev/md0) do not appear although /dev/sr0 was present.
> > 
> >  Highlights of the log (first few lines from 3.0.4, kernel finding
> > the disks and starting mdadm, error messages from smartd because the
> > devices don't exist) attached.
> > 
> >  I built udev-166 using the unchanged script that I used for the
> > desktop - it worked there, so I think it has been built correctly.
> > Certainly, I can't see any error messages in its build log.
> 
> If you were using LFS7, you could look at /run/var/bootlog (tmpfs) or 
> /var/log/boot.log (on disk).
 I'll just have to forego that pleasure for the moment ;-)
> 
> Are you using RAID?  I don't have much experience with SW raid.  When I 
> do use raid, I do it with HW and then treat it as a normal non-raid device.
> 
>    -- Bruce
 Yes, RAID-1 with mdadm.

ĸen
-- 
das eine Mal als Tragödie, das andere Mal als Farce
-- 
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page

Reply via email to