Re: Kernel recompile has left /boot empty
From: Matt Bostock (matt_at_mattbostock.com)
Date: 03/15/04
- Next message: David: "Re: Firewall restrictions on Debian Linux"
- Previous message: J.O. Aho: "Re: Kernel recompile has left /boot empty"
- In reply to: Brian Reiahle: "Re: Kernel recompile has left /boot empty"
- Next in thread: Brian Reiahle: "Re: Kernel recompile has left /boot empty"
- Reply: Brian Reiahle: "Re: Kernel recompile has left /boot empty"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Mon, 15 Mar 2004 15:09:48 -0000
See below...
Matt
-- Banging your head against a wall uses 150 calories an hour. "Brian Reiahle" <reply@the.newsgroup> wrote in message news:_U95c.119$th6.2468@nnrp1.ozemail.com.au... > > so /boot is a separate partition, yes? I'm not really sure now. Sorry for my ignorance... please see the end of my post, I've included /etc/fstab and mount's output. > shouldn't there also be a boot/lost+found directory there if /boot > mounted successfully. ext2/3 file systems usually (always?) have a > directory called lost+found in there file system root. > > # du boot -h > 12k boot/lost+found > 5.1M boot There's a lost+found in the file system root, i.e. /lost+found, but it doesn't contain the word 'boot' in its name. > Matt Bostock also wrote in another post: > > > PS Please note that when I rebooted the system after testing the new > > kernel, the boot dir was normal again. It's only when I'm running the > > new kernel that I have the problem. > > > > Matt "Brian Reiahle" <reply@the.newsgroup> wrote in message news:_U95c.119$th6.2468@nnrp1.ozemail.com.au... > it's possible for a real file to be in /boot (on the / partition) and > then mount another partition over top of it thus hiding what was there. > > mounting /boot can fail for a number of reasons and is the only thing I > can think of that would explain it ... unless you happen to be > duel-booting with another unix-like os and got a wrong partition > somewhere? but a mount failure sounds the most likely at the moment. > > what dose mount say? /dev/hda3 on / type ext3 (rw,usrquota,grpquota) none on /proc type proc (rw) none on /dev/pts type devpts (rw,gid=5,mode=620) none on /dev/shm type tmpfs (rw) That doesn't look right to me... anyone else? I have 2 80GB drives. /etc/fstab contains: LABEL=/ / ext3 defaults,usrquota,grpquota 1 1 LABEL=/boot /boot ext3 defaults 1 2 none /dev/pts devpts gid=5,mode=620 0 0 none /proc proc defaults 0 0 none /dev/shm tmpfs defaults 0 0 /dev/hda2 swap swap defaults 0 0 /dev/hdb1 /backup ext3 defaults 0 0 I tried running 'mount boot' and got the following: mount: fs type ext3 not supported by kernel Is that my problem? Did I not enable something I should have done in the kernel recompile config? Thanks again, Matt --- No viruses found in this message. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.622 / Virus Database: 400 - Release Date: 13/3/04
- Next message: David: "Re: Firewall restrictions on Debian Linux"
- Previous message: J.O. Aho: "Re: Kernel recompile has left /boot empty"
- In reply to: Brian Reiahle: "Re: Kernel recompile has left /boot empty"
- Next in thread: Brian Reiahle: "Re: Kernel recompile has left /boot empty"
- Reply: Brian Reiahle: "Re: Kernel recompile has left /boot empty"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|