[gentoo-user] Problems booting my server - ext2 - e2fsck

[gentoo-user] Problems booting my server - ext2 - e2fsck

[KH]

Hi there,

my server was running strait for 8 month now. I did updates regularly
but still used an 2.6.2x kernel. Never switched it of. Now someone from
houskeeping pulled the plug for the vacuum cleaner ...

Anyway the box won't boot anymore. grub starts up. Kernel boots. Then
there is checking root file system (or something like that).The message
is that my ext2 file system can not be read. That I might want to try
the alternativ superblock by running #e2fsck -b 8193 <device>

Well, I put the hdd in an external usb and conected it to my
workstation. As I thought hda3 (is /dev/sde3) is an ext3 filesystem.
Also badblocks and e2fsck did not show any problem with the hdd.

/etc/fstab is corect (i hope), too.

What am I missing? How can I get the server running, again?

Regards

kh

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Alan McKinnon]

On Saturday 24 July 2010 21:57:38 KH wrote:
> Hi there,
> 
> my server was running strait for 8 month now. I did updates regularly
> but still used an 2.6.2x kernel. Never switched it of. Now someone from
> houskeeping pulled the plug for the vacuum cleaner ...
> 
> Anyway the box won't boot anymore. grub starts up. Kernel boots. Then
> there is checking root file system (or something like that).The message
> is that my ext2 file system can not be read. That I might want to try
> the alternativ superblock by running #e2fsck -b 8193 <device>
> 
> Well, I put the hdd in an external usb and conected it to my
> workstation. As I thought hda3 (is /dev/sde3) is an ext3 filesystem.
> Also badblocks and e2fsck did not show any problem with the hdd.
> 
> /etc/fstab is corect (i hope), too.
> 
> What am I missing? How can I get the server running, again?

You said you ran e2fsck and it was OK. What was the command?

Normally with an e2fsck on a journalled fs, the app will replay the journal 
and make a few minor checks. This takes about 4 seconds, not the 40 minutes it 
takes to do a ful ext2 check.

I think you might need to fsck without the journal. I know there's a way to do 
this but a cursory glance at the man page didn't reveal it. Maybe an ext user 
will chip in with the correct method



-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Alan McKinnon]

On Saturday 24 July 2010 21:57:38 KH wrote:
> Hi there,
> 
> my server was running strait for 8 month now. I did updates regularly
> but still used an 2.6.2x kernel. Never switched it of. Now someone from
> houskeeping pulled the plug for the vacuum cleaner ...
> 
> Anyway the box won't boot anymore. grub starts up. Kernel boots. Then
> there is checking root file system (or something like that).The message
> is that my ext2 file system can not be read. That I might want to try
> the alternativ superblock by running #e2fsck -b 8193 <device>
> 
> Well, I put the hdd in an external usb and conected it to my
> workstation. As I thought hda3 (is /dev/sde3) is an ext3 filesystem.
> Also badblocks and e2fsck did not show any problem with the hdd.
> 
> /etc/fstab is corect (i hope), too.
> 
> What am I missing? How can I get the server running, again?

You said you ran e2fsck and it was OK. What was the command?

Normally with an e2fsck on a journalled fs, the app will replay the journal 
and make a few minor checks. This takes about 4 seconds, not the 40 minutes it 
takes to do a ful ext2 check.

I think you might need to fsck without the journal. I know there's a way to do 
this but a cursory glance at the man page didn't reveal it. Maybe an ext user 
will chip in with the correct method



-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[James Wall]

On 7/24/2010 3:25 PM, Alan McKinnon wrote:
> On Saturday 24 July 2010 21:57:38 KH wrote:
>> Hi there,
>>
>> my server was running strait for 8 month now. I did updates regularly
>> but still used an 2.6.2x kernel. Never switched it of. Now someone from
>> houskeeping pulled the plug for the vacuum cleaner ...
>>
>> Anyway the box won't boot anymore. grub starts up. Kernel boots. Then
>> there is checking root file system (or something like that).The message
>> is that my ext2 file system can not be read. That I might want to try
>> the alternativ superblock by running #e2fsck -b 8193<device>
>>
>> Well, I put the hdd in an external usb and conected it to my
>> workstation. As I thought hda3 (is /dev/sde3) is an ext3 filesystem.
>> Also badblocks and e2fsck did not show any problem with the hdd.
>>
>> /etc/fstab is corect (i hope), too.
>>
>> What am I missing? How can I get the server running, again?
>
> You said you ran e2fsck and it was OK. What was the command?
>
> Normally with an e2fsck on a journalled fs, the app will replay the journal
> and make a few minor checks. This takes about 4 seconds, not the 40 minutes it
> takes to do a ful ext2 check.
>
> I think you might need to fsck without the journal. I know there's a way to do
> this but a cursory glance at the man page didn't reveal it. Maybe an ext user
> will chip in with the correct method
>
>
>

Run e2fsck -f /dev/hda3 to force check a partition. I have had to do 
that when my kids yanked all the drives out of a server that I was 
setting up. :-)
--
No trees were harmed in the sending of this message. However, a large 
number of electrons were terribly inconvenienced.

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Robert Bridge]

On Sat, Jul 24, 2010 at 9:21 PM, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
> I think you might need to fsck without the journal. I know there's a way to do
> this but a cursory glance at the man page didn't reveal it. Maybe an ext user
> will chip in with the correct method

"e2fsck -f" should run the full system check after replaying the journal.

RobbieAB

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[KH]

Am 24.07.2010 22:21, schrieb Alan McKinnon:
> On Saturday 24 July 2010 21:57:38 KH wrote:
>> Hi there,
[...]
>> Anyway the box won't boot anymore. grub starts up. Kernel boots. Then
>> there is checking root file system (or something like that).The message
>> is that my ext2 file system can not be read. That I might want to try
>> the alternativ superblock by running #e2fsck -b 8193 <device>
>>
>> Well, I put the hdd in an external usb and conected it to my
>> workstation. As I thought hda3 (is /dev/sde3) is an ext3 filesystem.
>> Also badblocks and e2fsck did not show any problem with the hdd.
>>
>> /etc/fstab is corect (i hope), too.
>>
>> What am I missing? How can I get the server running, again?
> 
> You said you ran e2fsck and it was OK. What was the command?
> 
> Normally with an e2fsck on a journalled fs, the app will replay the journal 
> and make a few minor checks. This takes about 4 seconds, not the 40 minutes it 
> takes to do a ful ext2 check.
> 
> I think you might need to fsck without the journal. I know there's a way to do 
> this but a cursory glance at the man page didn't reveal it. Maybe an ext user 
> will chip in with the correct method
> 
> 
> 

Hi,

I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3
/dev/sde3 . Yes, it only took some seconds.

Regards
kh

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[KH]

Am 24.07.2010 23:46, schrieb James Wall:
> On 7/24/2010 3:25 PM, Alan McKinnon wrote:
>>
>> I think you might need to fsck without the journal. I know there's a
>> way to do
>> this but a cursory glance at the man page didn't reveal it. Maybe an
>> ext user
>> will chip in with the correct method
> 
> Run e2fsck -f /dev/hda3 to force check a partition. I have had to do
> that when my kids yanked all the drives out of a server that I was
> setting up. :-)

Hi again,

# e2fsck -fv /dev/sde3

e2fsck 1.41.11 (14-Mar-2010)
Durchgang 1: Prüfe Inodes, Blocks, und Größen
Durchgang 2: Prüfe Verzeichnis Struktur
Durchgang 3: Prüfe Verzeichnis Verknüpfungen
Durchgang 4: Überprüfe die Referenzzähler
Durchgang 5: Überprüfe Gruppe Zusammenfassung

  356415 inodes used (36.63%)
   10396 non-contiguous files (2.9%)
     236 non-contiguous directories (0.1%)
         # von Inodes mit ind/dind/tind Blöcken: 7917/121/0
 2191858 blocks used (56.32%)
       0 bad blocks
       1 large file

  315130 regular files
   31986 directories
    1051 character device files
    4089 block device files
       1 fifo
    2397 links
    4147 symbolic links (4027 fast symbolic links)
       2 sockets
--------
  358803 files


Well this does not look bad, does it?

Regards kh

> No trees were harmed in the sending of this message. However, a large
> number of electrons were terribly inconvenienced.

cool sig!

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Alan McKinnon]

On Sunday 25 July 2010 06:57:43 KH wrote:
> > You said you ran e2fsck and it was OK. What was the command?
> >
> > 
> >
> > Normally with an e2fsck on a journalled fs, the app will replay the
> > journal  and make a few minor checks. This takes about 4 seconds, not
> > the 40 minutes it takes to do a ful ext2 check.
> >
> > 
> >
> > I think you might need to fsck without the journal. I know there's a way
> > to do  this but a cursory glance at the man page didn't reveal it. Maybe
> > an ext user will chip in with the correct method
> >
> > 
> > 
> > 
> 
> Hi,
> 
> I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3
> /dev/sde3 . Yes, it only took some seconds.

It's been a long time since I used ext3 so some of this might be wrong.

An fsck that takes a few seconds is using the journal, which might not uncover 
deeper corruption. You should try disabling the journal (I couldn't find the 
way to do that though), but this will also work:

Boot of a LiveCD, mount your root partition somewhere using type "ext2" and 
fsck it. This will invalidate the journal but that's OK, it gets recreated on 
the next proper boot. Let the fsck finish - it will take a while on a large 
fs.

When done, reboot as normal and see if the machine boots up properly.


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Dale]

Alan McKinnon wrote:
> On Sunday 25 July 2010 06:57:43 KH wrote:
>    
>>> You said you ran e2fsck and it was OK. What was the command?
>>>
>>>
>>>
>>> Normally with an e2fsck on a journalled fs, the app will replay the
>>> journal  and make a few minor checks. This takes about 4 seconds, not
>>> the 40 minutes it takes to do a ful ext2 check.
>>>
>>>
>>>
>>> I think you might need to fsck without the journal. I know there's a way
>>> to do  this but a cursory glance at the man page didn't reveal it. Maybe
>>> an ext user will chip in with the correct method
>>>
>>>
>>>
>>>
>>>        
>> Hi,
>>
>> I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3
>> /dev/sde3 . Yes, it only took some seconds.
>>      
> It's been a long time since I used ext3 so some of this might be wrong.
>
> An fsck that takes a few seconds is using the journal, which might not uncover
> deeper corruption. You should try disabling the journal (I couldn't find the
> way to do that though), but this will also work:
>
> Boot of a LiveCD, mount your root partition somewhere using type "ext2" and
> fsck it. This will invalidate the journal but that's OK, it gets recreated on
> the next proper boot. Let the fsck finish - it will take a while on a large
> fs.
>
> When done, reboot as normal and see if the machine boots up properly.
>
>
>    

And I would stand guard to make sure housekeeping doesn't come around.  
;-)  Cutting power during all this wold not be good.

Dale

:-)  :-)

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 2370 bytes --]

On Sunday 25 July 2010 09:18:33 Dale wrote:
> Alan McKinnon wrote:
> > On Sunday 25 July 2010 06:57:43 KH wrote:
> >>> You said you ran e2fsck and it was OK. What was the command?
> >>> 
> >>> 
> >>> 
> >>> Normally with an e2fsck on a journalled fs, the app will replay the
> >>> journal  and make a few minor checks. This takes about 4 seconds, not
> >>> the 40 minutes it takes to do a ful ext2 check.
> >>> 
> >>> 
> >>> 
> >>> I think you might need to fsck without the journal. I know there's a
> >>> way to do  this but a cursory glance at the man page didn't reveal it.
> >>> Maybe an ext user will chip in with the correct method
> >> 
> >> Hi,
> >> 
> >> I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3
> >> /dev/sde3 . Yes, it only took some seconds.
> > 
> > It's been a long time since I used ext3 so some of this might be wrong.
> > 
> > An fsck that takes a few seconds is using the journal, which might not
> > uncover deeper corruption. You should try disabling the journal (I
> > couldn't find the way to do that though), but this will also work:
> > 
> > Boot of a LiveCD, mount your root partition somewhere using type "ext2"
> > and fsck it. This will invalidate the journal but that's OK, it gets
> > recreated on the next proper boot. Let the fsck finish - it will take a
> > while on a large fs.
> > 
> > When done, reboot as normal and see if the machine boots up properly.
> 
> And I would stand guard to make sure housekeeping doesn't come around.
> ;-)  Cutting power during all this wold not be good.

KH, I think that this may not be related to a fs error as such.

Yes, pulling the plug may have caused fs corruption.  However, more likely is 
that pulling the plug did not allow you to do something that you should have 
done after you finished upgrading to grub-0.97-r9.  The latest installation of 
grub asks you to reinstall in the MBR and point its root to wherever your 
/boot is.  GRUB's fs and its drivers may have changed and therefore the old 
boot loader code is looking for files that no longer exist.

So you'll probably be alright again if you boot with a fresh systemrescue 
LiveCD and run grub and then root (hd....) and setup (hd0) before you quit and 
reboot.

If that doesn't work then you most likely have a fs problem.

HTH.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[covici]

Dale <rdalek1967@gmail.com> wrote:

> Alan McKinnon wrote:
> > On Sunday 25 July 2010 06:57:43 KH wrote:
> >    
> >>> You said you ran e2fsck and it was OK. What was the command?
> >>>
> >>>
> >>>
> >>> Normally with an e2fsck on a journalled fs, the app will replay the
> >>> journal  and make a few minor checks. This takes about 4 seconds, not
> >>> the 40 minutes it takes to do a ful ext2 check.
> >>>
> >>>
> >>>
> >>> I think you might need to fsck without the journal. I know there's a way
> >>> to do  this but a cursory glance at the man page didn't reveal it. Maybe
> >>> an ext user will chip in with the correct method
> >>>
> >>>
> >>>
> >>>
> >>>        
> >> Hi,
> >>
> >> I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3
> >> /dev/sde3 . Yes, it only took some seconds.
> >>      
> > It's been a long time since I used ext3 so some of this might be wrong.
> >
> > An fsck that takes a few seconds is using the journal, which might not uncover
> > deeper corruption. You should try disabling the journal (I couldn't find the
> > way to do that though), but this will also work:
> >
> > Boot of a LiveCD, mount your root partition somewhere using type "ext2" and
> > fsck it. This will invalidate the journal but that's OK, it gets recreated on
> > the next proper boot. Let the fsck finish - it will take a while on a large
> > fs.
> >
> > When done, reboot as normal and see if the machine boots up properly.
> >
> >
> >    
> 
> And I would stand guard to make sure housekeeping doesn't come around.
> ;-)  Cutting power during all this wold not be good.

You don't need to invalidate the journal or mount ext2, just use -f if
memory serves, be sure the partition is unmounted and that will force a
full check.

-- 
Your life is like a penny.  You're going to lose it.  The question is:
How do
you spend it?

         John Covici
         covici@ccs.covici.com

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Alan McKinnon]

On Sunday 25 July 2010 10:18:33 Dale wrote:
> Alan McKinnon wrote:

[snip]

> > When done, reboot as normal and see if the machine boots up properly.
> 
> And I would stand guard to make sure housekeeping doesn't come around.
> ;-)  Cutting power during all this wold not be good.

Here in Africa we use pythons for that.

Real genuine live 10 foot snakes. In a terrarium of course.

Trust me, it takes about 30 seconds after the first housekeeping person sees 
it until none of them goes anywhere near your stuff.

:-)



-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Alan McKinnon]

On Sunday 25 July 2010 17:24:46 covici@ccs.covici.com wrote:
> > > When done, reboot as normal and see if the machine boots up properly.
> > >
> > >    
> >
> > 
> >
> > And I would stand guard to make sure housekeeping doesn't come around.
> > ;-)  Cutting power during all this wold not be good.
> 
> You don't need to invalidate the journal or mount ext2, just use -f if
> memory serves, be sure the partition is unmounted and that will force a
> full check.


Yes, -f does seem to be the right option. It's been ages since I used ext3 and 
I have no real way to do a test, so I played safe. And the man page could be a 
little more descriptive too, -f left me with more questions than answers.


-- 
alan dot mckinnon at gmail dot com

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Bill Kenworthy]

On Sun, 2010-07-25 at 22:08 +0200, Alan McKinnon wrote:
> On Sunday 25 July 2010 10:18:33 Dale wrote:
> > Alan McKinnon wrote:
> 
> [snip]
> 
> > > When done, reboot as normal and see if the machine boots up properly.
> > 
> > And I would stand guard to make sure housekeeping doesn't come around.
> > ;-)  Cutting power during all this wold not be good.
> 
> Here in Africa we use pythons for that.
> 
> Real genuine live 10 foot snakes. In a terrarium of course.
> 
> Trust me, it takes about 30 seconds after the first housekeeping person sees 
> it until none of them goes anywhere near your stuff.
> 
> :-)
> 
I like the idea of pythons, as they swallow the prey whole its much less
messy than the redback spiders suggested for use here in West Oz ...
someone would have to clean up the bodies in the morning.

Must be a coincidence, didnt update the MBR after installing grub and
failed to boot this morning - though the signs are more like disk
failure - even the live CD isnt helping :(

Another job for tonight when I get home.

BillK

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[William Kenworthy]

On Mon, 2010-07-26 at 09:05 +0800, Bill Kenworthy wrote:
> On Sun, 2010-07-25 at 22:08 +0200, Alan McKinnon wrote:
> > On Sunday 25 July 2010 10:18:33 Dale wrote:
> > > Alan McKinnon wrote:
> > 
> > [snip]
> > 
> > > > When done, reboot as normal and see if the machine boots up properly.
> > > 
> > > And I would stand guard to make sure housekeeping doesn't come around.
> > > ;-)  Cutting power during all this wold not be good.
> > 
> > Here in Africa we use pythons for that.
> > 
> > Real genuine live 10 foot snakes. In a terrarium of course.
> > 
> > Trust me, it takes about 30 seconds after the first housekeeping person sees 
> > it until none of them goes anywhere near your stuff.
> > 
> > :-)
> > 
> I like the idea of pythons, as they swallow the prey whole its much less
> messy than the redback spiders suggested for use here in West Oz ...
> someone would have to clean up the bodies in the morning.
> 
> Must be a coincidence, didnt update the MBR after installing grub and
> failed to boot this morning - though the signs are more like disk
> failure - even the live CD isnt helping :(
> 
> Another job for tonight when I get home.
> 
> BillK
> 

Fixed it - was grub after all - it renumbered my drives (0 and 1
swapped :(

Complicated because this was one of the early sata boards with a fake
raid chip to handle the sata while the old IDE drives were on the normal
bus.

Further complicated by the bios and raidchip changing drive assignments
depending on which drive/cd/floppy you booted from (i.e., what grub sees
as the drive numbers changes when the real OS is booted).  I forgot what
hoops I had to jump through to get this going originally.

Might be time for a new setup - amd athlon 2500+ are not so cool these
days :)

BillK

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Mick]

On 26 July 2010 11:54, William Kenworthy <billk@iinet.net.au> wrote:

> Fixed it - was grub after all - it renumbered my drives (0 and 1
> swapped :(
>
> Complicated because this was one of the early sata boards with a fake
> raid chip to handle the sata while the old IDE drives were on the normal
> bus.
>
> Further complicated by the bios and raidchip changing drive assignments
> depending on which drive/cd/floppy you booted from (i.e., what grub sees
> as the drive numbers changes when the real OS is booted).  I forgot what
> hoops I had to jump through to get this going originally.
>
> Might be time for a new setup - amd athlon 2500+ are not so cool these
> days :)

Glad you got it working!  Another gotcha is when you disable the
deprecated CONFIG_IDE in the kernel and you don't update your
grub.conf and /etc/fstab to rename /dev/hda's into /dev/sda's.
-- 
Regards,
Mick

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Peter Humphrey]

On Monday 26 July 2010 12:02:56 Mick wrote:

> Another gotcha is when you disable the deprecated CONFIG_IDE in the
> kernel and you don't update your grub.conf and /etc/fstab to rename
> /dev/hda's into /dev/sda's.

Drifting off topic somewhat, when I upgraded udev on my firewall box last 
week I was told I shouldn't have CONFIG_IDE set, so I recompiled the 
kernel without it and lo! a kernel panic during boot. And yes, I had 
changed hdas to sdas.

So udev is wrong in saying CONFIG_IDE should not be set - on that old P4 
box it has to be to get ICH4 drivers.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Dale]

William Kenworthy wrote:
> Might be time for a new setup - amd athlon 2500+ are not so cool these
> days :)
>
> BillK
>
>    

Mine still works well.  Just have to blow out the dust every month or so.

Dale

:-)  :-)

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Mick]

On 26 July 2010 15:11, Peter Humphrey <peter@humphrey.ukfsn.org> wrote:
> On Monday 26 July 2010 12:02:56 Mick wrote:
>
>> Another gotcha is when you disable the deprecated CONFIG_IDE in the
>> kernel and you don't update your grub.conf and /etc/fstab to rename
>> /dev/hda's into /dev/sda's.
>
> Drifting off topic somewhat, when I upgraded udev on my firewall box last
> week I was told I shouldn't have CONFIG_IDE set, so I recompiled the
> kernel without it and lo! a kernel panic during boot. And yes, I had
> changed hdas to sdas.
>
> So udev is wrong in saying CONFIG_IDE should not be set - on that old P4
> box it has to be to get ICH4 drivers.

Hmm, did you try ATA_PIIX, or PATA_MPIIX, or PATA_SCH?

Also, make sure you enable BLK_DEV_SR, for some reason I could get a
box to boot without it.  The box in question is an ancient PIII
Coppermine!
-- 
Regards,
Mick

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Peter Humphrey]

On Monday 26 July 2010 16:13:19 Mick wrote:
> On 26 July 2010 15:11, Peter Humphrey <peter@humphrey.ukfsn.org> 
wrote:
> > So udev is wrong in saying CONFIG_IDE should not be set - on that
> > old P4 box it has to be to get ICH4 drivers.
> 
> Hmm, did you try ATA_PIIX, or PATA_MPIIX, or PATA_SCH?

I've just tried it again now, to make sure, and the answer's "yes". I 
set all of those, and I tried adding PATA_OLDPIIX to see if it helped. 
It didn't, and neither did the others, so I'll have to go back to 
CONFIG_IDE.

> Also, make sure you enable BLK_DEV_SR, for some reason I could get a
> box to boot without it.  The box in question is an ancient PIII
> Coppermine!

Hmm. Not surprisingly, that didn't help either.

Thanks anyway.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Alex Schuster]

Peter Humphrey writes:

> On Monday 26 July 2010 16:13:19 Mick wrote:
> > On 26 July 2010 15:11, Peter Humphrey <peter@humphrey.ukfsn.org>
> > wrote:
> > > So udev is wrong in saying CONFIG_IDE should not be set - on that
> > > old P4 box it has to be to get ICH4 drivers.
> > 
> > Hmm, did you try ATA_PIIX, or PATA_MPIIX, or PATA_SCH?
> 
> I've just tried it again now, to make sure, and the answer's "yes". I
> set all of those, and I tried adding PATA_OLDPIIX to see if it helped.
> It didn't, and neither did the others, so I'll have to go back to
> CONFIG_IDE.

Isn't there also some other SCSI stuff (which does not get selected 
automatically), necessary to make the new ATA drivers actually work?

	Wonko

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 1183 bytes --]

On Monday 26 July 2010 19:04:16 Alex Schuster wrote:
> Peter Humphrey writes:
> > On Monday 26 July 2010 16:13:19 Mick wrote:
> > > On 26 July 2010 15:11, Peter Humphrey <peter@humphrey.ukfsn.org>
> > > 
> > > wrote:
> > > > So udev is wrong in saying CONFIG_IDE should not be set - on that
> > > > old P4 box it has to be to get ICH4 drivers.
> > > 
> > > Hmm, did you try ATA_PIIX, or PATA_MPIIX, or PATA_SCH?
> > 
> > I've just tried it again now, to make sure, and the answer's "yes". I
> > set all of those, and I tried adding PATA_OLDPIIX to see if it helped.
> > It didn't, and neither did the others, so I'll have to go back to
> > CONFIG_IDE.
> 
> Isn't there also some other SCSI stuff (which does not get selected
> automatically), necessary to make the new ATA drivers actually work?

You mean:

Device Drivers  ---> 
 Generic Driver Options  --->
  <*> Serial ATA and Parallel ATA drivers  --->
    [*] ATA SFF support

    Symbol: ATA [=y] 
    Prompt: Serial ATA and Parallel ATA drivers

I also have a P4 but I haven't yet switched off the deprecated drivers.  Will 
have a go later in the week and see what gives.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Peter Humphrey]

On Monday 26 July 2010 21:46:40 Mick wrote:
> On Monday 26 July 2010 19:04:16 Alex Schuster wrote:
> > Isn't there also some other SCSI stuff (which does not get selected
> > automatically), necessary to make the new ATA drivers actually
> > work?
> 
> You mean:
> 
> Device Drivers  --->
>  Generic Driver Options  --->
>   <*> Serial ATA and Parallel ATA drivers  --->
>     [*] ATA SFF support
> 
>     Symbol: ATA [=y]
>     Prompt: Serial ATA and Parallel ATA drivers

I did  have that selected, of course.

> I also have a P4 but I haven't yet switched off the deprecated
> drivers.  Will have a go later in the week and see what gives.

I'll be interested to hear how you get on.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[KH]

Am 25.07.2010 15:57, schrieb Mick:
> On Sunday 25 July 2010 09:18:33 Dale wrote:
>> Alan McKinnon wrote:
>>> On Sunday 25 July 2010 06:57:43 KH wrote:
>>>>> You said you ran e2fsck and it was OK. What was the command?
>>>>>
>>>>>
>>>>>
>>>>> Normally with an e2fsck on a journalled fs, the app will replay the
>>>>> journal  and make a few minor checks. This takes about 4 seconds, not
>>>>> the 40 minutes it takes to do a ful ext2 check.
>>>>>
>>>>>
>>>>>
>>>>> I think you might need to fsck without the journal. I know there's a
>>>>> way to do  this but a cursory glance at the man page didn't reveal it.
>>>>> Maybe an ext user will chip in with the correct method
>>>>
>>>> Hi,
>>>>
>>>> I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3
>>>> /dev/sde3 . Yes, it only took some seconds.
>>>
>>> It's been a long time since I used ext3 so some of this might be wrong.
>>>
>>> An fsck that takes a few seconds is using the journal, which might not
>>> uncover deeper corruption. You should try disabling the journal (I
>>> couldn't find the way to do that though), but this will also work:
>>>
>>> Boot of a LiveCD, mount your root partition somewhere using type "ext2"
>>> and fsck it. This will invalidate the journal but that's OK, it gets
>>> recreated on the next proper boot. Let the fsck finish - it will take a
>>> while on a large fs.
>>>
>>> When done, reboot as normal and see if the machine boots up properly.
>>
>> And I would stand guard to make sure housekeeping doesn't come around.
>> ;-)  Cutting power during all this wold not be good.
> 
> KH, I think that this may not be related to a fs error as such.
> 
> Yes, pulling the plug may have caused fs corruption.  However, more likely is 
> that pulling the plug did not allow you to do something that you should have 
> done after you finished upgrading to grub-0.97-r9.  The latest installation of 
> grub asks you to reinstall in the MBR and point its root to wherever your 
> /boot is.  GRUB's fs and its drivers may have changed and therefore the old 
> boot loader code is looking for files that no longer exist.
> 
> So you'll probably be alright again if you boot with a fresh systemrescue 
> LiveCD and run grub and then root (hd....) and setup (hd0) before you quit and 
> reboot.
> 
> If that doesn't work then you most likely have a fs problem.
> 
> HTH.

Hi,

I installed grub by connecting the hdd to my workstation. This did not
change anything.
Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
boots fine now. I can use it but ... There is no /dev/hd* . Running
mount /boot I get the answer /dev/hda1 does not exist. Also there is no
/dev/sd*

Any ideas?

Regards kh

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Mick]

On 28 July 2010 09:50, KH <gentoo-user@konstantinhansen.de> wrote:

> I installed grub by connecting the hdd to my workstation. This did not
> change anything.
> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
> boots fine now. I can use it but ... There is no /dev/hd* . Running
> mount /boot I get the answer /dev/hda1 does not exist. Also there is no
> /dev/sd*
>
> Any ideas?

KH, if you have changed the kernel to use libATA (i.e. the newer
SATA/PATA options) then you need to update your fstab from /dev/hdaX
to /dev/sdaX and change your grub.conf accordingly.

PS.  When you install GRUB use tab completion to see what's available
and make sure you install it in the correct drive/partition.

PPS.  Peter, I installed the kernel option for [*] ATA SFF support and
corresponding chipset (ICH) for my P4 and it now boots fine.  So I
suggest that you use lshw to find which chipset you must activate
under ATA SFF (unless you have one of the more modern <*>   AHCI SATA
support controllers like I have on my i7 Dell).
-- 
Regards,
Mick

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Bill Longman]

On 07/28/2010 01:50 AM, KH wrote:
> Am 25.07.2010 15:57, schrieb Mick:
>> On Sunday 25 July 2010 09:18:33 Dale wrote:
>>> Alan McKinnon wrote:
>>>> On Sunday 25 July 2010 06:57:43 KH wrote:
>>>>>> You said you ran e2fsck and it was OK. What was the command?
>>>>>>
>>>>>>
>>>>>>
>>>>>> Normally with an e2fsck on a journalled fs, the app will replay the
>>>>>> journal  and make a few minor checks. This takes about 4 seconds, not
>>>>>> the 40 minutes it takes to do a ful ext2 check.
>>>>>>
>>>>>>
>>>>>>
>>>>>> I think you might need to fsck without the journal. I know there's a
>>>>>> way to do  this but a cursory glance at the man page didn't reveal it.
>>>>>> Maybe an ext user will chip in with the correct method
>>>>>
>>>>> Hi,
>>>>>
>>>>> I ran on the two partitions e2fsck /dev/sde3 as well as fsck.ext3
>>>>> /dev/sde3 . Yes, it only took some seconds.
>>>>
>>>> It's been a long time since I used ext3 so some of this might be wrong.
>>>>
>>>> An fsck that takes a few seconds is using the journal, which might not
>>>> uncover deeper corruption. You should try disabling the journal (I
>>>> couldn't find the way to do that though), but this will also work:
>>>>
>>>> Boot of a LiveCD, mount your root partition somewhere using type "ext2"
>>>> and fsck it. This will invalidate the journal but that's OK, it gets
>>>> recreated on the next proper boot. Let the fsck finish - it will take a
>>>> while on a large fs.
>>>>
>>>> When done, reboot as normal and see if the machine boots up properly.
>>>
>>> And I would stand guard to make sure housekeeping doesn't come around.
>>> ;-)  Cutting power during all this wold not be good.
>>
>> KH, I think that this may not be related to a fs error as such.
>>
>> Yes, pulling the plug may have caused fs corruption.  However, more likely is 
>> that pulling the plug did not allow you to do something that you should have 
>> done after you finished upgrading to grub-0.97-r9.  The latest installation of 
>> grub asks you to reinstall in the MBR and point its root to wherever your 
>> /boot is.  GRUB's fs and its drivers may have changed and therefore the old 
>> boot loader code is looking for files that no longer exist.
>>
>> So you'll probably be alright again if you boot with a fresh systemrescue 
>> LiveCD and run grub and then root (hd....) and setup (hd0) before you quit and 
>> reboot.
>>
>> If that doesn't work then you most likely have a fs problem.
>>
>> HTH.
> 
> Hi,
> 
> I installed grub by connecting the hdd to my workstation. This did not
> change anything.
> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
> boots fine now. I can use it but ... There is no /dev/hd* . Running
> mount /boot I get the answer /dev/hda1 does not exist. Also there is no
> /dev/sd*
> 
> Any ideas?

Konstantin, please post what your kernel has for IDE support. If you
have /proc/config.gz, then please post the results from "zgrep IDE
/proc/config.gz" so we can get an idea of why you have no /dev/hd*
devices. We will also need to know what kind of disk controller your
server really has. Are they IDE or SATA controllers?

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Bill Longman]

On 07/28/2010 06:42 AM, Mick wrote:
> On 28 July 2010 09:50, KH <gentoo-user@konstantinhansen.de> wrote:
> 
>> I installed grub by connecting the hdd to my workstation. This did not
>> change anything.
>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>> boots fine now. I can use it but ... There is no /dev/hd* . Running
>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no
>> /dev/sd*
>>
>> Any ideas?
> 
> KH, if you have changed the kernel to use libATA (i.e. the newer
> SATA/PATA options) then you need to update your fstab from /dev/hdaX
> to /dev/sdaX and change your grub.conf accordingly.

But he doesn't even have those devices, so this will not do him any good
until we know how the kernel is configured (or not) and get the devices
back.

Konstantin, I'm assuming, from your original post, that you have not
changed your kernel in any way over the last few months. You said that
it was running fine for eight months but now after rebooting, you're in
trouble. Are you *sure* you haven't made any changes to the kernel? I'm
also assuming that you know that the kernel drivers for your disk
controllers should not be built as modules but built into the kernel so
that you don't need to go through creating an initramfs and hoping for
your devices to get populated.

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Mick]

On 28 July 2010 14:53, Bill Longman <bill.longman@gmail.com> wrote:
> On 07/28/2010 06:42 AM, Mick wrote:
>> On 28 July 2010 09:50, KH <gentoo-user@konstantinhansen.de> wrote:
>>
>>> I installed grub by connecting the hdd to my workstation. This did not
>>> change anything.
>>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>>> boots fine now. I can use it but ... There is no /dev/hd* . Running
>>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no
>>> /dev/sd*
>>>
>>> Any ideas?
>>
>> KH, if you have changed the kernel to use libATA (i.e. the newer
>> SATA/PATA options) then you need to update your fstab from /dev/hdaX
>> to /dev/sdaX and change your grub.conf accordingly.
>
> But he doesn't even have those devices, so this will not do him any good
> until we know how the kernel is configured (or not) and get the devices
> back.

I am not sure that he does not have those devices ... I don't know if
the error message is returned from grub or from the OS.

It could be that the kernel stanza is wrongly pointing to /dev/hda,
and, or fstab is not correct.
-- 
Regards,
Mick

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Bill Longman]

On 07/28/2010 07:04 AM, Mick wrote:
> On 28 July 2010 14:53, Bill Longman <bill.longman@gmail.com> wrote:
>> On 07/28/2010 06:42 AM, Mick wrote:
>>> On 28 July 2010 09:50, KH <gentoo-user@konstantinhansen.de> wrote:
>>>
>>>> I installed grub by connecting the hdd to my workstation. This did not
>>>> change anything.
>>>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>>>> boots fine now. I can use it but ... There is no /dev/hd* . Running
>>>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no
>>>> /dev/sd*
>>>>
>>>> Any ideas?
>>>
>>> KH, if you have changed the kernel to use libATA (i.e. the newer
>>> SATA/PATA options) then you need to update your fstab from /dev/hdaX
>>> to /dev/sdaX and change your grub.conf accordingly.
>>
>> But he doesn't even have those devices, so this will not do him any good
>> until we know how the kernel is configured (or not) and get the devices
>> back.
> 
> I am not sure that he does not have those devices ... I don't know if
> the error message is returned from grub or from the OS.
> 
> It could be that the kernel stanza is wrongly pointing to /dev/hda,
> and, or fstab is not correct.

He says the "pc boots fine now" and he "can use it" and he goes on to
say that he has "no /dev/hd*" or "/dev/sd*" devices, so I have to
believe he's got a running system. Not having any /dev/hd* files would
support the error trying to mount /boot. Trying to fix /etc/fstab first
is not the way to attack his problem given the information we have now.

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Mick]

On 28 July 2010 15:27, Bill Longman <bill.longman@gmail.com> wrote:
> On 07/28/2010 07:04 AM, Mick wrote:
>> On 28 July 2010 14:53, Bill Longman <bill.longman@gmail.com> wrote:
>>> On 07/28/2010 06:42 AM, Mick wrote:
>>>> On 28 July 2010 09:50, KH <gentoo-user@konstantinhansen.de> wrote:
>>>>
>>>>> I installed grub by connecting the hdd to my workstation. This did not
>>>>> change anything.
>>>>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>>>>> boots fine now. I can use it but ... There is no /dev/hd* . Running
>>>>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no
>>>>> /dev/sd*
>>>>>
>>>>> Any ideas?
>>>>
>>>> KH, if you have changed the kernel to use libATA (i.e. the newer
>>>> SATA/PATA options) then you need to update your fstab from /dev/hdaX
>>>> to /dev/sdaX and change your grub.conf accordingly.
>>>
>>> But he doesn't even have those devices, so this will not do him any good
>>> until we know how the kernel is configured (or not) and get the devices
>>> back.
>>
>> I am not sure that he does not have those devices ... I don't know if
>> the error message is returned from grub or from the OS.
>>
>> It could be that the kernel stanza is wrongly pointing to /dev/hda,
>> and, or fstab is not correct.
>
> He says the "pc boots fine now" and he "can use it" and he goes on to
> say that he has "no /dev/hd*" or "/dev/sd*" devices, so I have to
> believe he's got a running system.

Hmm ... he'll have to be able to hang his OS off some fs or other if
it is indeed working.  Unless he's running some clever ramdisk, then I
would not reach the conclusion that he has a working OS.

> Not having any /dev/hd* files would
> support the error trying to mount /boot. Trying to fix /etc/fstab first
> is not the way to attack his problem given the information we have now.

Perhaps he passed the correct path to his grub and the boot sequence
fails when it tries to find the devices listed in fstab, so the OS
never completes booting.

Either way, hopefully the OP will shed some light to this rather than
us assuming more or less what might actually be the case.
-- 
Regards,
Mick

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[KH]

Am 28.07.2010 15:45, schrieb Bill Longman:
> On 07/28/2010 01:50 AM, KH wrote:
>>
>> Hi,
>>
>> I installed grub by connecting the hdd to my workstation. This did not
>> change anything.
>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>> boots fine now. I can use it but ... There is no /dev/hd* . Running
>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no
>> /dev/sd*
>>
>> Any ideas?
> 
> Konstantin, please post what your kernel has for IDE support. If you
> have /proc/config.gz, then please post the results from "zgrep IDE
> /proc/config.gz" so we can get an idea of why you have no /dev/hd*
> devices. We will also need to know what kind of disk controller your
> server really has. Are they IDE or SATA controllers?
> 

Hi Bill,

Now I am running 2.6.30-r8 but 2.6.34-r1 is ready but not jet copied to
/boot. btw it is a p3 coppermine.

This is the output from zgrep IDE /proc/config.gz .


CONFIG_HAVE_IDE=y
CONFIG_IDE=y
# Please see Documentation/ide/ide.txt for help/info on IDE drives
CONFIG_IDE_XFER_MODE=y
CONFIG_IDE_TIMINGS=y
CONFIG_IDE_ATAPI=y
# CONFIG_BLK_DEV_IDE_SATA is not set
CONFIG_IDE_GD=y
CONFIG_IDE_GD_ATA=y
CONFIG_IDE_GD_ATAPI=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
# CONFIG_BLK_DEV_IDETAPE is not set
CONFIG_BLK_DEV_IDEACPI=y
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_PROC_FS=y
# IDE chipset support/bugfixes
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_IDEPNP is not set
CONFIG_BLK_DEV_IDEDMA_SFF=y
# PCI IDE chipsets support
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_PCIBUS_ORDER=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_VIDEO_DEV is not set
# CONFIG_VIDEO_MEDIA is not set
# CONFIG_VIDEO_OUTPUT_CONTROL is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set

I just tried /etc/init.de/udev resart . I am getting errors not to use
the script with baselayout-1 . The box is very slow now. Will reboot and
see what baselayout is on it.

Regards kh

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[KH]

Am 28.07.2010 16:04, schrieb Mick:
> On 28 July 2010 14:53, Bill Longman <bill.longman@gmail.com> wrote:
>> On 07/28/2010 06:42 AM, Mick wrote:
>>> On 28 July 2010 09:50, KH <gentoo-user@konstantinhansen.de> wrote:
>>>
>>>> I installed grub by connecting the hdd to my workstation. This did not
>>>> change anything.
>>>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>>>> boots fine now. I can use it but ... There is no /dev/hd* . Running
>>>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no
>>>> /dev/sd*
>>>>
>>>> Any ideas?
>>>
>>> KH, if you have changed the kernel to use libATA (i.e. the newer
>>> SATA/PATA options) then you need to update your fstab from /dev/hdaX
>>> to /dev/sdaX and change your grub.conf accordingly.
>>
>> But he doesn't even have those devices, so this will not do him any good
>> until we know how the kernel is configured (or not) and get the devices
>> back.
> 
> I am not sure that he does not have those devices ... I don't know if
> the error message is returned from grub or from the OS.
> 
> It could be that the kernel stanza is wrongly pointing to /dev/hda,
> and, or fstab is not correct.

Hi Mick,

but typing ls /dev/hd* or ls /dev/sd* should show up something.
Shouldn't it? df -h shows /dev/hda3 is mounted on /
For me this is strange.

kh

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[KH]

Am 28.07.2010 15:53, schrieb Bill Longman:
> On 07/28/2010 06:42 AM, Mick wrote:
>> On 28 July 2010 09:50, KH <gentoo-user@konstantinhansen.de> wrote:
>>
>>> I installed grub by connecting the hdd to my workstation. This did not
>>> change anything.
>>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>>> boots fine now. I can use it but ... There is no /dev/hd* . Running
>>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no
>>> /dev/sd*
>>>
>>> Any ideas?
>>
>> KH, if you have changed the kernel to use libATA (i.e. the newer
>> SATA/PATA options) then you need to update your fstab from /dev/hdaX
>> to /dev/sdaX and change your grub.conf accordingly.
> 
> But he doesn't even have those devices, so this will not do him any good
> until we know how the kernel is configured (or not) and get the devices
> back.
> 
> Konstantin, I'm assuming, from your original post, that you have not
> changed your kernel in any way over the last few months. You said that
> it was running fine for eight months but now after rebooting, you're in
> trouble. Are you *sure* you haven't made any changes to the kernel? I'm
> also assuming that you know that the kernel drivers for your disk
> controllers should not be built as modules but built into the kernel so
> that you don't need to go through creating an initramfs and hoping for
> your devices to get populated.
> 

Hi,

I tried booting 2.6.28 / 2.6.29 / 2.6.30 . The 30 series has not been
running on the box befor. Anyway the result is the same no matter which
kernel I am booting.
I use make oldconfig for uping the kernel.

kh

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Bill Longman]

On 07/28/2010 07:56 AM, KH wrote:
> Am 28.07.2010 15:45, schrieb Bill Longman:
>> On 07/28/2010 01:50 AM, KH wrote:
>>>
>>> Hi,
>>>
>>> I installed grub by connecting the hdd to my workstation. This did not
>>> change anything.
>>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>>> boots fine now. I can use it but ... There is no /dev/hd* . Running
>>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no
>>> /dev/sd*
>>>
>>> Any ideas?
>>
>> Konstantin, please post what your kernel has for IDE support. If you
>> have /proc/config.gz, then please post the results from "zgrep IDE
>> /proc/config.gz" so we can get an idea of why you have no /dev/hd*
>> devices. We will also need to know what kind of disk controller your
>> server really has. Are they IDE or SATA controllers?
>>
> 
> Hi Bill,
> 
> Now I am running 2.6.30-r8 but 2.6.34-r1 is ready but not jet copied to
> /boot. btw it is a p3 coppermine.
> 
> This is the output from zgrep IDE /proc/config.gz .
> 
> 
> CONFIG_HAVE_IDE=y
> CONFIG_IDE=y
> # Please see Documentation/ide/ide.txt for help/info on IDE drives
> CONFIG_IDE_XFER_MODE=y
> CONFIG_IDE_TIMINGS=y
> CONFIG_IDE_ATAPI=y
> # CONFIG_BLK_DEV_IDE_SATA is not set
> CONFIG_IDE_GD=y
> CONFIG_IDE_GD_ATA=y
> CONFIG_IDE_GD_ATAPI=y
> CONFIG_BLK_DEV_IDECD=y
> CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
> # CONFIG_BLK_DEV_IDETAPE is not set
> CONFIG_BLK_DEV_IDEACPI=y
> # CONFIG_IDE_TASK_IOCTL is not set
> CONFIG_IDE_PROC_FS=y
> # IDE chipset support/bugfixes
> CONFIG_IDE_GENERIC=y
> # CONFIG_BLK_DEV_IDEPNP is not set
> CONFIG_BLK_DEV_IDEDMA_SFF=y
> # PCI IDE chipsets support
> CONFIG_BLK_DEV_IDEPCI=y
> CONFIG_IDEPCI_PCIBUS_ORDER=y
> CONFIG_BLK_DEV_IDEDMA_PCI=y
> CONFIG_BLK_DEV_IDEDMA=y
> # CONFIG_VIDEO_DEV is not set
> # CONFIG_VIDEO_MEDIA is not set
> # CONFIG_VIDEO_OUTPUT_CONTROL is not set
> # CONFIG_FB_TRIDENT is not set
> # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set

I would expect to see:

CONFIG_BLK_DEV_PIIX=y

in your configuration given that it's a Coppermine. You might want to
add that in the 2.6.30 and the 2.6.34 kernels, although DEV_GENERIC
should give you what you need, as you are probably using that right now.

Use "make menuconfig" to configure the kernel. Make sure it's "<*>" not
"<M>" for the PIIX controller and then rebuild and install the kernel.

Do you have "lspci" installed? The results from "lspci -v" would be very
helpful right now.

> I just tried /etc/init.de/udev resart . I am getting errors not to use
> the script with baselayout-1 . The box is very slow now. Will reboot and
> see what baselayout is on it.

Yeah, don't worry about this right now.

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Bill Longman]

On 07/28/2010 08:18 AM, KH wrote:
> Am 28.07.2010 16:04, schrieb Mick:
>> On 28 July 2010 14:53, Bill Longman <bill.longman@gmail.com> wrote:
>>> On 07/28/2010 06:42 AM, Mick wrote:
>>>> On 28 July 2010 09:50, KH <gentoo-user@konstantinhansen.de> wrote:
>>>>
>>>>> I installed grub by connecting the hdd to my workstation. This did not
>>>>> change anything.
>>>>> Also I changed /etc/fstab . Now I have 0 0 for every partition. The pc
>>>>> boots fine now. I can use it but ... There is no /dev/hd* . Running
>>>>> mount /boot I get the answer /dev/hda1 does not exist. Also there is no
>>>>> /dev/sd*
>>>>>
>>>>> Any ideas?
>>>>
>>>> KH, if you have changed the kernel to use libATA (i.e. the newer
>>>> SATA/PATA options) then you need to update your fstab from /dev/hdaX
>>>> to /dev/sdaX and change your grub.conf accordingly.
>>>
>>> But he doesn't even have those devices, so this will not do him any good
>>> until we know how the kernel is configured (or not) and get the devices
>>> back.
>>
>> I am not sure that he does not have those devices ... I don't know if
>> the error message is returned from grub or from the OS.
>>
>> It could be that the kernel stanza is wrongly pointing to /dev/hda,
>> and, or fstab is not correct.
> 
> Hi Mick,
> 
> but typing ls /dev/hd* or ls /dev/sd* should show up something.
> Shouldn't it? df -h shows /dev/hda3 is mounted on /
> For me this is strange.

How is /dev mounted right now? What does "udevadm --version" tell you?

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[KH]

[-- Attachment #1: Type: text/plain, Size: 373 bytes --]

Am 28.07.2010 17:30, schrieb Bill Longman:
> On 07/28/2010 08:18 AM, KH wrote:
>>
>> Hi Mick,
>>
>> but typing ls /dev/hd* or ls /dev/sd* should show up something.
>> Shouldn't it? df -h shows /dev/hda3 is mounted on /
>> For me this is strange.
> 
> How is /dev mounted right now? What does "udevadm --version" tell you?
> 

udev is 151 and baselayout is 1.12.13

Regards

[-- Attachment #2: dfh --]
[-- Type: text/plain, Size: 264 bytes --]

Filesystem            Size  Used Avail Use% Mounted on
/dev/hda3              15G  8.2G  5.8G  59% /
udev                   10M   36K   10M   1% /dev
tmpfs                 2.5G     0  2.5G   0% /var/tmp/portage
shm                   187M     0  187M   0% /dev/shm

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[KH]

Am 28.07.2010 17:27, schrieb Bill Longman:
> On 07/28/2010 07:56 AM, KH wrote:
>> Am 28.07.2010 15:45, schrieb Bill Longman:
>>>
>>> Konstantin, please post what your kernel has for IDE support. If you
>>> have /proc/config.gz, then please post the results from "zgrep IDE
>>> /proc/config.gz" so we can get an idea of why you have no /dev/hd*
>>> devices. We will also need to know what kind of disk controller your
>>> server really has. Are they IDE or SATA controllers?
>>>
>>
>> Hi Bill,
>>
>> Now I am running 2.6.30-r8 but 2.6.34-r1 is ready but not jet copied to
>> /boot. btw it is a p3 coppermine.
>>
>> This is the output from zgrep IDE /proc/config.gz .
>>
>>
>> CONFIG_HAVE_IDE=y
>> CONFIG_IDE=y
>> # Please see Documentation/ide/ide.txt for help/info on IDE drives
>> CONFIG_IDE_XFER_MODE=y
>> CONFIG_IDE_TIMINGS=y
>> CONFIG_IDE_ATAPI=y
>> # CONFIG_BLK_DEV_IDE_SATA is not set
>> CONFIG_IDE_GD=y
>> CONFIG_IDE_GD_ATA=y
>> CONFIG_IDE_GD_ATAPI=y
>> CONFIG_BLK_DEV_IDECD=y
>> CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
>> # CONFIG_BLK_DEV_IDETAPE is not set
>> CONFIG_BLK_DEV_IDEACPI=y
>> # CONFIG_IDE_TASK_IOCTL is not set
>> CONFIG_IDE_PROC_FS=y
>> # IDE chipset support/bugfixes
>> CONFIG_IDE_GENERIC=y
>> # CONFIG_BLK_DEV_IDEPNP is not set
>> CONFIG_BLK_DEV_IDEDMA_SFF=y
>> # PCI IDE chipsets support
>> CONFIG_BLK_DEV_IDEPCI=y
>> CONFIG_IDEPCI_PCIBUS_ORDER=y
>> CONFIG_BLK_DEV_IDEDMA_PCI=y
>> CONFIG_BLK_DEV_IDEDMA=y
>> # CONFIG_VIDEO_DEV is not set
>> # CONFIG_VIDEO_MEDIA is not set
>> # CONFIG_VIDEO_OUTPUT_CONTROL is not set
>> # CONFIG_FB_TRIDENT is not set
>> # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
> 
> I would expect to see:
> 
> CONFIG_BLK_DEV_PIIX=y
> 
> in your configuration given that it's a Coppermine. You might want to
> add that in the 2.6.30 and the 2.6.34 kernels, although DEV_GENERIC
> should give you what you need, as you are probably using that right now.
> 
> Use "make menuconfig" to configure the kernel. Make sure it's "<*>" not
> "<M>" for the PIIX controller and then rebuild and install the kernel.
> 
> Do you have "lspci" installed? The results from "lspci -v" would be very
> helpful right now.
> 
>> I just tried /etc/init.de/udev resart . I am getting errors not to use
>> the script with baselayout-1 . The box is very slow now. Will reboot and
>> see what baselayout is on it.
> 
> Yeah, don't worry about this right now.
> 

lspci:

00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and
Memory Controller Hub (rev 02)
        Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard
        Flags: bus master, fast devsel, latency 0
        Memory at f8000000 (32-bit, prefetchable) [size=64M]
        Capabilities: [88] Vendor Specific Information <?>
        Capabilities: [a0] AGP version 2.0
        Kernel driver in use: agpgart-intel

00:01.0 PCI bridge: Intel Corporation 82815 815 Chipset AGP Bridge (rev
02) (prog-if 00 [Normal decode])
        Flags: bus master, 66MHz, fast devsel, latency 64
        Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
        Memory behind bridge: ee000000-efefffff
        Prefetchable memory behind bridge: eff00000-f7ffffff

00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 02) (prog-if
00 [Normal decode])
        Flags: bus master, fast devsel, latency 0
        Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
        I/O behind bridge: 0000d000-0000dfff
        Memory behind bridge: ed800000-edffffff

00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 02)
        Flags: bus master, medium devsel, latency 0

00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller
(rev 02) (prog-if 80 [Master])
        Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard
        Flags: bus master, medium devsel, latency 0
        [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
        [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
        [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
        [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
        I/O ports at b800 [size=16]
        Kernel driver in use: PIIX_IDE

00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1
(rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard
        Flags: bus master, medium devsel, latency 0, IRQ 12
        I/O ports at b400 [size=32]
        Kernel driver in use: uhci_hcd

00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 02)
        Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard
        Flags: medium devsel, IRQ 10
        I/O ports at e800 [size=16]

00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1
(rev 02) (prog-if 00 [UHCI])
        Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard
        Flags: bus master, medium devsel, latency 0, IRQ 6
        I/O ports at b000 [size=32]
        Kernel driver in use: uhci_hcd

01:00.0 VGA compatible controller: nVidia Corporation NV11DDR [GeForce2
MX200] (rev b2) (prog-if 00 [VGA controller])
        Subsystem: ABIT Computer Corp. Device 6106
        Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
        Memory at ee000000 (32-bit, non-prefetchable) [size=16M]
        Memory at f0000000 (32-bit, prefetchable) [size=128M]
        Expansion ROM at efff0000 [disabled] [size=64K]
        Capabilities: [60] Power Management version 2
        Capabilities: [44] AGP version 2.0
        Kernel modules: nvidia

02:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL-8139/8139C/8139C+ (rev 10)
        Subsystem: Allied Telesyn International AT-2500TX/ACPI
        Flags: bus master, medium devsel, latency 32, IRQ 5
        I/O ports at d800 [size=256]
        Memory at ed800000 (32-bit, non-prefetchable) [size=256]
        Capabilities: [50] Power Management version 2
        Kernel driver in use: 8139too


Regards

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Bill Longman]

On 07/28/2010 09:37 AM, KH wrote:
> Am 28.07.2010 17:27, schrieb Bill Longman:
>> On 07/28/2010 07:56 AM, KH wrote:
>>> Am 28.07.2010 15:45, schrieb Bill Longman:
>>>>
>>>> Konstantin, please post what your kernel has for IDE support. If you
>>>> have /proc/config.gz, then please post the results from "zgrep IDE
>>>> /proc/config.gz" so we can get an idea of why you have no /dev/hd*
>>>> devices. We will also need to know what kind of disk controller your
>>>> server really has. Are they IDE or SATA controllers?
>>>>
>>>
>>> Hi Bill,
>>>
>>> Now I am running 2.6.30-r8 but 2.6.34-r1 is ready but not jet copied to
>>> /boot. btw it is a p3 coppermine.
>>>
>>> This is the output from zgrep IDE /proc/config.gz .
>>>
>>>
>>> CONFIG_HAVE_IDE=y
>>> CONFIG_IDE=y
>>> # Please see Documentation/ide/ide.txt for help/info on IDE drives
>>> CONFIG_IDE_XFER_MODE=y
>>> CONFIG_IDE_TIMINGS=y
>>> CONFIG_IDE_ATAPI=y
>>> # CONFIG_BLK_DEV_IDE_SATA is not set
>>> CONFIG_IDE_GD=y
>>> CONFIG_IDE_GD_ATA=y
>>> CONFIG_IDE_GD_ATAPI=y
>>> CONFIG_BLK_DEV_IDECD=y
>>> CONFIG_BLK_DEV_IDECD_VERBOSE_ERRORS=y
>>> # CONFIG_BLK_DEV_IDETAPE is not set
>>> CONFIG_BLK_DEV_IDEACPI=y
>>> # CONFIG_IDE_TASK_IOCTL is not set
>>> CONFIG_IDE_PROC_FS=y
>>> # IDE chipset support/bugfixes
>>> CONFIG_IDE_GENERIC=y
>>> # CONFIG_BLK_DEV_IDEPNP is not set
>>> CONFIG_BLK_DEV_IDEDMA_SFF=y
>>> # PCI IDE chipsets support
>>> CONFIG_BLK_DEV_IDEPCI=y
>>> CONFIG_IDEPCI_PCIBUS_ORDER=y
>>> CONFIG_BLK_DEV_IDEDMA_PCI=y
>>> CONFIG_BLK_DEV_IDEDMA=y
>>> # CONFIG_VIDEO_DEV is not set
>>> # CONFIG_VIDEO_MEDIA is not set
>>> # CONFIG_VIDEO_OUTPUT_CONTROL is not set
>>> # CONFIG_FB_TRIDENT is not set
>>> # CONFIG_PROVIDE_OHCI1394_DMA_INIT is not set
>>
>> I would expect to see:
>>
>> CONFIG_BLK_DEV_PIIX=y
>>
>> in your configuration given that it's a Coppermine. You might want to
>> add that in the 2.6.30 and the 2.6.34 kernels, although DEV_GENERIC
>> should give you what you need, as you are probably using that right now.
>>
>> Use "make menuconfig" to configure the kernel. Make sure it's "<*>" not
>> "<M>" for the PIIX controller and then rebuild and install the kernel.
>>
>> Do you have "lspci" installed? The results from "lspci -v" would be very
>> helpful right now.
>>
>>> I just tried /etc/init.de/udev resart . I am getting errors not to use
>>> the script with baselayout-1 . The box is very slow now. Will reboot and
>>> see what baselayout is on it.
>>
>> Yeah, don't worry about this right now.
>>
> 
> lspci:
> 
> 00:00.0 Host bridge: Intel Corporation 82815 815 Chipset Host Bridge and
> Memory Controller Hub (rev 02)
>         Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard
>         Flags: bus master, fast devsel, latency 0
>         Memory at f8000000 (32-bit, prefetchable) [size=64M]
>         Capabilities: [88] Vendor Specific Information <?>
>         Capabilities: [a0] AGP version 2.0
>         Kernel driver in use: agpgart-intel
> 
> 00:01.0 PCI bridge: Intel Corporation 82815 815 Chipset AGP Bridge (rev
> 02) (prog-if 00 [Normal decode])
>         Flags: bus master, 66MHz, fast devsel, latency 64
>         Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
>         Memory behind bridge: ee000000-efefffff
>         Prefetchable memory behind bridge: eff00000-f7ffffff
> 
> 00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 02) (prog-if
> 00 [Normal decode])
>         Flags: bus master, fast devsel, latency 0
>         Bus: primary=00, secondary=02, subordinate=02, sec-latency=32
>         I/O behind bridge: 0000d000-0000dfff
>         Memory behind bridge: ed800000-edffffff
> 
> 00:1f.0 ISA bridge: Intel Corporation 82801BA ISA Bridge (LPC) (rev 02)
>         Flags: bus master, medium devsel, latency 0
> 
> 00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller
> (rev 02) (prog-if 80 [Master])
>         Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard
>         Flags: bus master, medium devsel, latency 0
>         [virtual] Memory at 000001f0 (32-bit, non-prefetchable) [size=8]
>         [virtual] Memory at 000003f0 (type 3, non-prefetchable) [size=1]
>         [virtual] Memory at 00000170 (32-bit, non-prefetchable) [size=8]
>         [virtual] Memory at 00000370 (type 3, non-prefetchable) [size=1]
>         I/O ports at b800 [size=16]
>         Kernel driver in use: PIIX_IDE
> 
> 00:1f.2 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1
> (rev 02) (prog-if 00 [UHCI])
>         Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard
>         Flags: bus master, medium devsel, latency 0, IRQ 12
>         I/O ports at b400 [size=32]
>         Kernel driver in use: uhci_hcd
> 
> 00:1f.3 SMBus: Intel Corporation 82801BA/BAM SMBus Controller (rev 02)
>         Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard
>         Flags: medium devsel, IRQ 10
>         I/O ports at e800 [size=16]
> 
> 00:1f.4 USB Controller: Intel Corporation 82801BA/BAM USB Controller #1
> (rev 02) (prog-if 00 [UHCI])
>         Subsystem: ASUSTeK Computer Inc. TUSL2-C Mainboard
>         Flags: bus master, medium devsel, latency 0, IRQ 6
>         I/O ports at b000 [size=32]
>         Kernel driver in use: uhci_hcd
> 
> 01:00.0 VGA compatible controller: nVidia Corporation NV11DDR [GeForce2
> MX200] (rev b2) (prog-if 00 [VGA controller])
>         Subsystem: ABIT Computer Corp. Device 6106
>         Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 11
>         Memory at ee000000 (32-bit, non-prefetchable) [size=16M]
>         Memory at f0000000 (32-bit, prefetchable) [size=128M]
>         Expansion ROM at efff0000 [disabled] [size=64K]
>         Capabilities: [60] Power Management version 2
>         Capabilities: [44] AGP version 2.0
>         Kernel modules: nvidia
> 
> 02:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
> RTL-8139/8139C/8139C+ (rev 10)
>         Subsystem: Allied Telesyn International AT-2500TX/ACPI
>         Flags: bus master, medium devsel, latency 32, IRQ 5
>         I/O ports at d800 [size=256]
>         Memory at ed800000 (32-bit, non-prefetchable) [size=256]
>         Capabilities: [50] Power Management version 2
>         Kernel driver in use: 8139too
> 
>

Well this is very strange indeed. If I were you, I would rebuild the
2.6.34 kernel with "make menuconfig".

In the Device Drivers section, (this is for 2.6.34!), turn OFF the
deprecated ATA/ATAPI/MFM/RLL support. That corresponds to CONFIG_IDE in
your .config. Then, turn ON, Serial ATA and Parallel ATA drivers which
corresponds to CONFIG_ATA in your .config. Then, under Serial ATA,
you'll need to turn on ATA SFF and then Intel ESB, ICH, PIIX3, PIIX4
PATA/SATA support.

Rebuild the kernel as normal and give that a try. Indeed, it is not at
all obvious to me how you cannot have /dev/hda devices while having
/dev/hda3 mounted. Unless your /dev filesystem is goofed up and you're
saving a bad copy of it, they should be there. You might want to try
"udevadm info --query=all --name=hda" or various permutations of that to
see what is going on.

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Mick]

[-- Attachment #1: Type: Text/Plain, Size: 608 bytes --]

On Wednesday 28 July 2010 17:35:44 KH wrote:
> Am 28.07.2010 17:30, schrieb Bill Longman:
> > On 07/28/2010 08:18 AM, KH wrote:
> >> Hi Mick,
> >> 
> >> but typing ls /dev/hd* or ls /dev/sd* should show up something.
> >> Shouldn't it? df -h shows /dev/hda3 is mounted on /
> >> For me this is strange.
> > 
> > How is /dev mounted right now? What does "udevadm --version" tell you?
> 
> udev is 151 and baselayout is 1.12.13

Yes this is indeed strange ... short of having some strange access rights or 
umask in your fstab ... is it the same when you ls as root user?

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Bill Longman]

On 07/28/2010 11:54 AM, Mick wrote:
> On Wednesday 28 July 2010 17:35:44 KH wrote:
>> Am 28.07.2010 17:30, schrieb Bill Longman:
>>> On 07/28/2010 08:18 AM, KH wrote:
>>>> Hi Mick,
>>>>
>>>> but typing ls /dev/hd* or ls /dev/sd* should show up something.
>>>> Shouldn't it? df -h shows /dev/hda3 is mounted on /
>>>> For me this is strange.
>>>
>>> How is /dev mounted right now? What does "udevadm --version" tell you?
>>
>> udev is 151 and baselayout is 1.12.13
> 
> Yes this is indeed strange ... short of having some strange access rights or 
> umask in your fstab ... is it the same when you ls as root user?

Are there any red flags in dmesg?

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Peter Humphrey]

On Wednesday 28 July 2010 19:14:05 Bill Longman wrote:

> In the Device Drivers section, (this is for 2.6.34!), turn OFF the
> deprecated ATA/ATAPI/MFM/RLL support. That corresponds to CONFIG_IDE
> in your .config. Then, turn ON, Serial ATA and Parallel ATA drivers
> which corresponds to CONFIG_ATA in your .config. Then, under Serial
> ATA, you'll need to turn on ATA SFF and then Intel ESB, ICH, PIIX3,
> PIIX4 PATA/SATA support.

But bear in mind that setting these does not produce a bootable kernel 
on my P4 box, as I've said in another thread, so it's possible that 
making the suggested changes will introduce more fog rather than 
dispelling it. I'm not sure how likely it is though.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.

Re: [gentoo-user] Problems booting my server - ext2 - e2fsck

[Peter Humphrey]

On Thursday 29 July 2010 12:39:46 I wrote:
> On Wednesday 28 July 2010 19:14:05 Bill Longman wrote:
> > In the Device Drivers section, (this is for 2.6.34!), turn OFF the
> > deprecated ATA/ATAPI/MFM/RLL support. That corresponds to
> > CONFIG_IDE in your .config. Then, turn ON, Serial ATA and Parallel
> > ATA drivers which corresponds to CONFIG_ATA in your .config. Then,
> > under Serial ATA, you'll need to turn on ATA SFF and then Intel
> > ESB, ICH, PIIX3, PIIX4 PATA/SATA support.
> 
> But bear in mind that setting these does not produce a bootable
> kernel on my P4 box, as I've said in another thread, so it's
> possible that making the suggested changes will introduce more fog
> rather than dispelling it. I'm not sure how likely it is though.

For the record, this is now fixed. Eventually (this morning) I found a 
chipset option buried in the kernel config that I'd missed. The IDE disk 
is now /dev/sda and I can forget about /dev/hda and friends altogether.

-- 
Rgds
Peter.          Linux Counter 5290, 1994-04-23.