Advertisement
If you have a new account but are having problems posting or verifying your account, please email us on hello@boards.ie for help. Thanks :)
Hello all! Please ensure that you are posting a new thread or question in the appropriate forum. The Feedback forum is overwhelmed with questions that are having to be moved elsewhere. If you need help to verify your account contact hello@boards.ie
Hi all! We have been experiencing an issue on site where threads have been missing the latest postings. The platform host Vanilla are working on this issue. A workaround that has been used by some is to navigate back from 1 to 10+ pages to re-sync the thread and this will then show the latest posts. Thanks, Mike.
Hi there,
There is an issue with role permissions that is being worked on at the moment.
If you are having trouble with access or permissions on regional forums please post here to get access: https://www.boards.ie/discussion/2058365403/you-do-not-have-permission-for-that#latest

Latest kernel - 2.6.15 - can't see second hard drive

  • 31-01-2006 4:41pm
    #1
    niallb
    Registered Users, Registered Users 2 Posts: 2,747 ✭✭✭


    Hi,
    I've built several kernels from the latest source,
    both vanilla and patched with the mISDN patches.

    While mISDN now builds cleanly against the kernel,
    I'm having weird filesystem problems.

    The new kernels can't see linux partitions on my second drive.
    Originally I thought it was just an ext3 issue,
    but migrated the partitions to ext2
    and the problem remained.
    A vfat partition on the drive is visible.

    Somebody else is having the same problem, but with the drives reversed:
    i.e. visible system drive on hdb, and
    inaccessible linux partitions on hda.

    I've compared the IDE, partition, and filesystem related values in my .config to those
    from one known to be working under 2.6.12 with no glaring differences.

    I'm about to rebuild the same config with a variety of
    different gcc versions, as I think it's likely that I've just
    come across a glitch, and hopefully I'll get one that works.

    Just wondering has anyone else here seen this bug,
    or found a solution?

    NiallB


Comments

  • #2
    tomk
    Registered Users, Registered Users 2 Posts: 1,067 ✭✭✭tomk


    I've had 2.6.15 running on my server for nearly a month, Niall, with no problems. hda has 3 reiserfs partitions, hdb has one ext3, and both have some swap space as well.

    Let me know if you need config files or any other details.


  • #3
    niallb
    Registered Users, Registered Users 2 Posts: 2,747 ✭✭✭niallb


    Hi Tom,
    I'd like to see a copy of your .config - just in case there's some dependency I've set differently.

    I'm most interested in what compiler version you used.
    I rebuilt yeserday using gcc 3.4.3 with no joy.
    I've now got a 3.3 environment ready to go.
    I'll go back to a 2.x if I really have to!

    The mISDN features are important to me.
    For now, I've put the ISDN cards in a seperate box,
    and am using a 2.4 kernel where in kernel ISDN support still worked. My other alternative is to stick hdb into another
    machine and mount it over the network, but with that glaring error in the kernel, I'm reluctant to trust it at all.

    Thanks for the feedback,
    NiallB


  • #4
    tomk
    Registered Users, Registered Users 2 Posts: 1,067 ✭✭✭tomk


    Here's the config - just rebuilt it this morning, actually. I use the -ck patchset, server version - I don't know if that makes any difference to your problem.

    gcc is 4.0.3.

    I've never used ISDN with Linux, so there's nothing I can add on that. If there's anything else I can tell you, let me know.


  • #5
    niallb
    Registered Users, Registered Users 2 Posts: 2,747 ✭✭✭niallb


    Found the problem.
    I'll post it here just in case anyone else gets affected.

    The evms "Enterprise Volume Management System"
    was installed and grabbed all the unmounted partitions
    at boot making them unavailable to the kernel.
    The root partition and the drive it was on had already been claimed by the kernel driver, so I could see those fine.
    I disabled the evms service and the second drive came back online with my own kernel.

    NiallB


Advertisement