[Nottingham] io scheduler crash

Chris Hammond christopher.hammond at gmail.com
Tue Dec 14 18:23:46 GMT 2004


Thanks very much for your help, I used genkernel then ripped out what
I didn't think I needed. Which left me with a few  more things than
when I did it myself from scratch. Now it works. I wish I knew what I
was missing before but I really can't be bothered to keep re-compiling
my kernel to find out what it was.

However, on bootup, it won't mount the /boot partition saying it has a
problem with one of the superblocks. Although I can mount it manually
when it has booted. More worryingly, I tried to emerge KDE last night
and when I got up thus morning I found that it had some I/O errors on
hda, it said it was having problems with various sectors and logical
blocks, and locked all access to the hard disk
('reiserfs_read_locked_inode'). Since the hard disk failed and was
replaced just a few weeks ago, is there any chance this is an innocent
error, perhaps something to do with power-management screw-ups? I've
left it compiling KDE again today and there don't seem to have been
any more errors...

Thanks again,

Chris


> Chris,
> 
> I'd try using genkernel first to see if you can build a kernel that you
> can boot from.
> 
> If it works you can always build a more customised kernel to meet your
> needs, basing it on the .config file from genkernel.
> 
> genkernel has, like most programs lots of options, including one to run
> menuconfig to enable the bits that you want. You could try something
> like:
> 
> genkernel all --menuconfig --bootsplash --install --udev \
> --bootloader=grub  --mountboot
> 
> Which will:
> * build all steps
> * run menuconfig
> * install bootsplash support
> * install the kernel once it has been built
> * enable support for udev
> * configure grub.conf for you
> * mount /boot for you
> 
> --
> Regards
> 
> Richard
> 
>



More information about the Nottingham mailing list