[ARMedslack] Problem with Linux 2.6.36.3 packages
Hi Linux 2.6.36.3 works fine on my OpenRD client but on the SheevaPlug with a USB hard drive (/sev/sda), the MD raid module is binding to /dev/sda and preventing it from being used directly. I'm not sure why this is yet - I'm looking into it. -- Stuart Winter Slackware ARM: www.armedslack.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Problem with Linux 2.6.36.3 packages
> Linux 2.6.36.3 works fine on my OpenRD client but on the SheevaPlug with a > USB hard drive (/sev/sda), the MD raid module is binding to /dev/sda and > preventing it from being used directly. > > I'm not sure why this is yet - I'm looking into it. It's actually mdadm being naughty. I've reverted it to the previous version and I'll upload the rebuilt installer within the next day or so. I'm surprised nobody's noticed this problem before though. -- Stuart Winter Slackware ARM: www.armedslack.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Problem with Linux 2.6.36.3 packages
> It's actually mdadm being naughty. > I've reverted it to the previous version and I'll upload the rebuilt > installer within the next day or so. > > I'm surprised nobody's noticed this problem before though. After dd /dev/zero the whole disc, repartitioning and re-creating the filesystems, putting mdadm-2.6 back into the installer and installing; I now find that mdadm-3 works just fine with Linux 2.6.36.3 on the same system. I've no idea whatsoever what's gone on there, but it seems everything works now. -- Stuart Winter Slackware ARM: www.armedslack.org ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Problem with Linux 2.6.36.3 packages
On 01/21/2011 08:25 AM, Stuart Winter wrote: It's actually mdadm being naughty. I've reverted it to the previous version and I'll upload the rebuilt installer within the next day or so. I'm surprised nobody's noticed this problem before though. After dd /dev/zero the whole disc, repartitioning and re-creating the filesystems, putting mdadm-2.6 back into the installer and installing; I now find that mdadm-3 works just fine with Linux 2.6.36.3 on the same system. I've no idea whatsoever what's gone on there, but it seems everything works now. shouldnt have to DD the whole disk as zero just the first few blocks.. e what i tried at least for a few other problems... -- === Never ask a geek why, just nod your head and slowly back away.=== ++==+ | John O'Donnell| | | (Sr. Systems Engineer,|http://juanisan.homeip.net| | Net Admin, Programmer, etc.) | E-Mail: unixjohn1...@gmail.com | ++==+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Problem with Linux 2.6.36.3 packages
> shouldnt have to DD the whole disk as zero just the first few blocks.. e > what i tried at least for a few other problems... I know - but mdadm was still taking /dev/sda even *without* partitions. I'm guessing somehow, somewhere, there was some residue from when the disc may have been in a raid configuration somewhere on another system from where the disc originated (I have a collection of old discs from a variety of places where I used to be a sysadmin). *shrug* ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Problem with Linux 2.6.36.3 packages
On 01/21/2011 08:48 AM, Stuart Winter wrote: shouldnt have to DD the whole disk as zero just the first few blocks.. e what i tried at least for a few other problems... I know - but mdadm was still taking /dev/sda even *without* partitions. I'm guessing somehow, somewhere, there was some residue from when the disc may have been in a raid configuration somewhere on another system from where the disc originated (I have a collection of old discs from a variety of places where I used to be a sysadmin). *shrug* You should write to the mdadm writers as that is really weird . I would hav zeroed and started from there. There are asking for failure! -- === Never ask a geek why, just nod your head and slowly back away.=== ++==+ | John O'Donnell| | | (Sr. Systems Engineer,|http://juanisan.homeip.net| | Net Admin, Programmer, etc.) | E-Mail: unixjohn1...@gmail.com | ++==+ No man is useless who has a friend, and if we are loved we are indispensable. -- Robert Louis Stevenson ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
Re: [ARMedslack] Problem with Linux 2.6.36.3 packages
> > *shrug* > You should write to the mdadm writers as that is really weird . I would hav > zeroed and started from there. There are asking for failure! That was the plan - reinstall and get a working system by putting mdadm-2.6 into the installer, boot into the new OS and start working out why 3.x was behaving as it was; but after the fresh installation onto the new partitions, the problem's gone away -- so I can't replicate anymore. I've just reinstalled whilst having 3.x in the installer again, and the problem no longer exists. ___ ARMedslack mailing list ARMedslack@lists.armedslack.org http://lists.armedslack.org/mailman/listinfo/armedslack
