Skip to contentSkip to conversation

Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

DISCUSSION Walt H 2 participants 22 messages Dec 20, 2003 – Dec 24, 2003 Kbuild

lore
Share & tools
lore

Walt H

author
#0 lore raw

Hello,

Is the Promise raid configured as a raid0 stripe? If so, can you see in the boot messages if, when the ataraid driver detects the drives it is only detecting one of the drives? Have you recently added or replaced one of the drives?

If the ataraid driver only detects one of the drives in a raid0 array, you might try this patch:

--- /usr/src/temp/linux-2.4.21/drivers/ide/raid/pdcraid.c 2003-06-13
07:51:34.000000000 -0700
+++ pdcraid.c 2003-07-18 06:54:25.000000000 -0700
@@ -361,7 +361,8 @@

        if (ideinfo->sect==0)
                return 0;
-       lba = (ideinfo->capacity / (ideinfo->head*ideinfo->sect));
+/*     lba = (ideinfo->capacity / (ideinfo->head*ideinfo->sect));
        lba = lba * (ideinfo->head*ideinfo->sect);
-       lba = lba - ideinfo->sect;
+       lba = lba - ideinfo->sect; */
+       lba = ideinfo->capacity - ideinfo->sect;
        return lba;

I diffed it against 2.4.21 but it should still apply. HTH,

-Walt

#1 lore raw

Hi,

Oh I forgot to say that i'm running RAID1 and it detects both drives perfectly (I'm passing the IDE addresses to the kernel at boot time from the lilo conf, see previous post). The system was reinstalled yesterday with two brand new 80GB Western Digital disks (WD800JB-00DUA3). The thing is, I have succesfully installed the TX2000 card with the native ATARAID drivers before using two 30GB Maxtor (something) disks and kernel 2.4-20 - 2.4.23. I wonder why I can't get it up and running now. It will only work with the pre compiled kernel shipped with Debian 3.0 (2.4.18-bf2.4). I have tried all sorts of kernel settings. Since I have got it to work before I think should be able to do it again.

Please advise.

/Nicke

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 20 december 2003 20:45
To: [email protected]; linux-kernel
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Hello,

Is the Promise raid configured as a raid0 stripe? If so, can you see in the boot messages if, when the ataraid driver detects the drives it is only detecting one of the drives? Have you recently added or replaced one of the drives?

If the ataraid driver only detects one of the drives in a raid0 array, you might try this patch:

--- /usr/src/temp/linux-2.4.21/drivers/ide/raid/pdcraid.c 2003-06-13
07:51:34.000000000 -0700
+++ pdcraid.c 2003-07-18 06:54:25.000000000 -0700
@@ -361,7 +361,8 @@

        if (ideinfo->sect==0)
                return 0;
-       lba = (ideinfo->capacity / (ideinfo->head*ideinfo->sect));
+/*     lba = (ideinfo->capacity / (ideinfo->head*ideinfo->sect));
        lba = lba * (ideinfo->head*ideinfo->sect);
-       lba = lba - ideinfo->sect;
+       lba = lba - ideinfo->sect; */
+       lba = ideinfo->capacity - ideinfo->sect;
        return lba;

I diffed it against 2.4.21 but it should still apply. HTH,

-Walt

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

author
#2 lore raw
Quoted 13 lines · Nicklas Bondesson

Hi,

Oh I forgot to say that i'm running RAID1 and it detects both drives perfectly (I'm passing the IDE addresses to the kernel at boot time from the lilo conf, see previous post). The system was reinstalled yesterday with two brand new 80GB Western Digital disks (WD800JB-00DUA3). The thing is, I have succesfully installed the TX2000 card with the native ATARAID drivers before using two 30GB Maxtor (something) disks and kernel 2.4-20 - 2.4.23. I wonder why I can't get it up and running now. It will only work with the pre compiled kernel shipped with Debian 3.0 (2.4.18-bf2.4). I have tried all sorts of kernel settings. Since I have got it to work before I think should be able to do it again.

Quoted 3 lines

Please advise.

/Nicke

Hmmm. I'm pretty sure that the partitions are enumerated the same way in 2.4.23 vs. 2.4.18. There was a change in the way IDE geometry was returned from the kernel that caused a hiccup in the pdcraid driver around 2.4.22 I think? My patch just tells the pdcraid to use an alternate method of finding the RAID superblock on each drive. Not sure what else might be the problem. Do you see the ataraid driver fire up (looking something like this):

ataraid/d0: ataraid/d0p1
Drive 0 is 239372 Mb (33 / 0)
Drive 1 is 239372 Mb (34 / 0)
Raid1 array consists of 2 drives.
Promise Fasttrak(tm) Softwareraid driver for linux version 0.03beta

The only problem I've recently come upon with pdcraid, is when it detects just one of the drives and fails. I didn't think that should happen with raid1 though.

#3 lore raw

Nopes, I get the kernel panic before the driver loads or when it does, however I'm not seeing any ataraid driver message at all. This is really strange I think. The only thing that has changed in my setup are the harddrives. I really need to get this working. Do you have any suggestions what-so-ever what to do? I really appreciate your help on this.

/Nicke

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 21 december 2003 02:01
To: Nicklas Bondesson
Cc: [email protected]
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Quoted 12 lines · Nicklas Bondesson

Hi,

Oh I forgot to say that i'm running RAID1 and it detects both drives perfectly (I'm passing the IDE addresses to the kernel at boot time from the lilo conf, see previous post). The system was reinstalled yesterday with two brand new 80GB Western Digital disks (WD800JB-00DUA3). The thing is, I have succesfully installed the TX2000 card with the native ATARAID drivers before using two 30GB Maxtor (something) disks and kernel 2.4-20 - 2.4.23. I wonder why I can't get it up and running now. It will only work with the pre compiled kernel shipped with Debian 3.0 (2.4.18-bf2.4). I have tried all sorts of kernel settings. Since I have got it to work before I think

should be able to do it again.

Quoted 4 lines

Please advise.

/Nicke

Hmmm. I'm pretty sure that the partitions are enumerated the same way in 2.4.23 vs. 2.4.18. There was a change in the way IDE geometry was returned from the kernel that caused a hiccup in the pdcraid driver around 2.4.22 I think? My patch just tells the pdcraid to use an alternate method of finding the RAID superblock on each drive. Not sure what else might be the problem. Do you see the ataraid driver fire up (looking something like this):

ataraid/d0: ataraid/d0p1
Drive 0 is 239372 Mb (33 / 0)
Drive 1 is 239372 Mb (34 / 0)
Raid1 array consists of 2 drives.
Promise Fasttrak(tm) Softwareraid driver for linux version 0.03beta

The only problem I've recently come upon with pdcraid, is when it detects just one of the drives and fails. I didn't think that should happen with raid1 though.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

author
#4 lore raw
Quoted 8 lines · Nicklas Bondesson

Nopes, I get the kernel panic before the driver loads or when it does, however I'm not seeing any ataraid driver message at all. This is really strange I think. The only thing that has changed in my setup are the harddrives. I really need to get this working. Do you have any suggestions what-so-ever what to do? I really appreciate your help on this.

/Nicke

Well, since you're using raid1, you should be able to pass a root=/dev/hda1 (or whatever your / is located) using the same kernel and at least boot using this kernel. Then maybe you can use dmesg etc.. to see what the driver is actually doing. From your original post, it looks like you're using Lilo, so you'll need to boot using the old kernel first and change the lilo entry.

-Walt

#5 lore raw

I will try to do that now. Do you think this can have anything to do with me actually having a rather large root partition (76GB)? I will try with two 33GB partitions this time (it might have something to do with it - but on the other hand it is working working with the Debian pre-compiled kernel).

Well, let's see what I find out. I'll keep you posted.

/Nicke

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 21 december 2003 17:32
To: Nicklas Bondesson
Cc: [email protected]
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Quoted 5 lines · Nicklas Bondesson

Nopes, I get the kernel panic before the driver loads or when it does, however I'm not seeing any ataraid driver message at all. This is really strange I think. The only thing that has changed in my setup are the harddrives. I really need to get this working. Do you have any suggestions what-so-ever what to do? I really appreciate your help on

this.

Quoted 3 lines

/Nicke

Well, since you're using raid1, you should be able to pass a root=/dev/hda1 (or whatever your / is located) using the same kernel and at least boot using this kernel. Then maybe you can use dmesg etc.. to see what the driver is actually doing. From your original post, it looks like you're using Lilo, so you'll need to boot using the old kernel first and change the lilo entry.

-Walt

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#6 lore raw
In reply to Walt H

Now I'm sucessfully booting my system with the 2.4.23 kernel using only one of the drives (hde). There is not a single line in the logs that says anything about the Promise ATARAID driver is beeing fired up, so my guess is that it doesn't load if no one is calling on it. When I try to boot from the RAID it dies right after the "NET4: Unix domain sockets 1.0/SMP for Linux" message. I think it's when the ATARAID driver is about to fire up. I have no idea at all what to do now. It must have something to do with the hard drives since this is the only thing that has changed. Maybee I'm missing some important kernel setting option or so? (I don't think so, but one never know for sure). Also what have changed in the Promise / ATARAID since 2.4.18?.

/Nicke

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 21 december 2003 17:32
To: Nicklas Bondesson
Cc: [email protected]
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Quoted 5 lines · Nicklas Bondesson

Nopes, I get the kernel panic before the driver loads or when it does, however I'm not seeing any ataraid driver message at all. This is really strange I think. The only thing that has changed in my setup are the harddrives. I really need to get this working. Do you have any suggestions what-so-ever what to do? I really appreciate your help on

this.

Quoted 3 lines

/Nicke

Well, since you're using raid1, you should be able to pass a root=/dev/hda1 (or whatever your / is located) using the same kernel and at least boot using this kernel. Then maybe you can use dmesg etc.. to see what the driver is actually doing. From your original post, it looks like you're using Lilo, so you'll need to boot using the old kernel first and change the lilo entry.

-Walt

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

author
#7 lore raw
Quoted 12 lines · Nicklas Bondesson

Now I'm sucessfully booting my system with the 2.4.23 kernel using only one of the drives (hde). There is not a single line in the logs that says anything about the Promise ATARAID driver is beeing fired up, so my guess is that it doesn't load if no one is calling on it. When I try to boot from the RAID it dies right after the "NET4: Unix domain sockets 1.0/SMP for Linux" message. I think it's when the ATARAID driver is about to fire up. I have no idea at all what to do now. It must have something to do with the hard drives since this is the only thing that has changed. Maybee I'm missing some important kernel setting option or so? (I don't think so, but one never know for sure). Also what have changed in the Promise / ATARAID since 2.4.18?.

Quoted 1 line

/Nicke

Not sure what else to tell you. If the pdcraid driver is compiled into the kernel, you'll get a message about it during boot, even if it can't find all the drives. I no longer use the 2.4 kernel series (or pdcraid), so I'm afraid I'm out of ideas. Maybe somebody else on the list has some other things to try. Sorry.

-Walt

#8 lore raw

Do I have to include anything else than this??

<*> ATA/IDE/MFM/RLL support
IDE, ATA and ATAPI Block devices -->
<*> PROMISE PDC202{68|69|70|71|75|76|77} support (NEW) [*] Special FastTrack Feature

<*> Support for IDE Raid Controllers (EXPERIMENTAL) <*> Support Promise software RAID (Fasttrak(tm)) (EXPERIMENTAL)

/Nicke

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 22 december 2003 02:36
To: Nicklas Bondesson
Cc: [email protected]
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Quoted 5 lines · Nicklas Bondesson

Now I'm sucessfully booting my system with the 2.4.23 kernel using only one of the drives (hde). There is not a single line in the logs that says anything about the Promise ATARAID driver is beeing fired up, so my guess is that it doesn't load if no one is calling on it. When I try to boot from the RAID it dies right after the "NET4: Unix

domain sockets 1.0/SMP for Linux"

Quoted 8 lines

message. I think it's when the ATARAID driver is about to fire up. I have no idea at all what to do now. It must have something to do with the hard drives since this is the only thing that has changed. Maybee I'm missing some important kernel setting option or so? (I don't think so, but one never know for sure). Also what have changed in the Promise / ATARAID since 2.4.18?.

/Nicke

Not sure what else to tell you. If the pdcraid driver is compiled into the kernel, you'll get a message about it during boot, even if it can't find all the drives. I no longer use the 2.4 kernel series (or pdcraid), so I'm afraid I'm out of ideas. Maybe somebody else on the list has some other things to try. Sorry.

-Walt

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

author
#9 lore raw
Quoted 7 lines · Nicklas Bondesson

Do I have to include anything else than this??

<*> ATA/IDE/MFM/RLL support
IDE, ATA and ATAPI Block devices -->
<*> PROMISE PDC202{68|69|70|71|75|76|77} support (NEW) [*] Special FastTrack Feature

Quoted 5 lines

<*> Support for IDE Raid Controllers (EXPERIMENTAL) <*> Support Promise software RAID (Fasttrak(tm)) (EXPERIMENTAL)

/Nicke

I believe that should do it. dmesg doesn't have any info about the ataraid driver being loaded? If it's scrolling out of the kernel buffer, you can try bumping up the size through the kernel config. The option is under the "Kernel Hacking" section and is CONFIG_LOG_BUF_SHIFT. Change it to 17 or 18 to be sure. A reboot with this new kernel should give you a full dmesg afterward, hopefully showing what's wrong with the ataraid stuff.

-Walt

PS. I don't remember when this took place, but there were some changes to the promise drivers in 2.4 around 2.4.21 I think. There should be drivers for both the older Promise and the newer. I remember always choosing both, complete with pdcraid just to be sure.

#10 lore raw

No problem I can see the whole boot log. The ATARAID driver never loads. Could you force it to load somehow?

I get these messages:

PDC20271: IDE controller at PCI slot 00:09.0
PCI: Found IRQ 12 for device 00.09.0
PCI: Sharing IRQ 12 with 00:04.2

PDC20271: not 100% native mode: will probe irqs later

	ide2: BM-DMA at ...
	ide3: BM-DMA at ...

then it finds the disks:

hde: WDC ...
hdg: WDC ...

partition check:
hde: hde1, hde2
hdg: hdg1, hdg2

ide: late registration of driver

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 22 december 2003 16:06
To: Nicklas Bondesson
Cc: [email protected]; [email protected]
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Quoted 7 lines · Nicklas Bondesson

Do I have to include anything else than this??

<*> ATA/IDE/MFM/RLL support
IDE, ATA and ATAPI Block devices -->
<*> PROMISE PDC202{68|69|70|71|75|76|77} support (NEW) [*] Special FastTrack Feature

Quoted 5 lines

<*> Support for IDE Raid Controllers (EXPERIMENTAL) <*> Support Promise software RAID (Fasttrak(tm)) (EXPERIMENTAL)

/Nicke

I believe that should do it. dmesg doesn't have any info about the ataraid driver being loaded? If it's scrolling out of the kernel buffer, you can try bumping up the size through the kernel config. The option is under the "Kernel Hacking" section and is CONFIG_LOG_BUF_SHIFT. Change it to 17 or 18 to be sure.
A reboot with this new kernel should give you a full dmesg afterward, hopefully showing what's wrong with the ataraid stuff.

-Walt

PS. I don't remember when this took place, but there were some changes to the promise drivers in 2.4 around 2.4.21 I think. There should be drivers for both the older Promise and the newer. I remember always choosing both, complete with pdcraid just to be sure.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#11 lore raw
In reply to Walt H

I just downloaded and compiled the 2.4.18 kernel and it works perfectly. It must have something to with any changes from 2.4.18 - 2.4.23. I will try which version up until 2.4.23 that works. I'll keep you posted. Do you know who I should send this "bug" to in order to get it fixed in the next 2.4.x version?

/Nicke

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 22 december 2003 02:36
To: Nicklas Bondesson
Cc: [email protected]
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Quoted 5 lines · Nicklas Bondesson

Now I'm sucessfully booting my system with the 2.4.23 kernel using only one of the drives (hde). There is not a single line in the logs that says anything about the Promise ATARAID driver is beeing fired up, so my guess is that it doesn't load if no one is calling on it. When I try to boot from the RAID it dies right after the "NET4: Unix

domain sockets 1.0/SMP for Linux"

Quoted 8 lines

message. I think it's when the ATARAID driver is about to fire up. I have no idea at all what to do now. It must have something to do with the hard drives since this is the only thing that has changed. Maybee I'm missing some important kernel setting option or so? (I don't think so, but one never know for sure). Also what have changed in the Promise / ATARAID since 2.4.18?.

/Nicke

Not sure what else to tell you. If the pdcraid driver is compiled into the kernel, you'll get a message about it during boot, even if it can't find all the drives. I no longer use the 2.4 kernel series (or pdcraid), so I'm afraid I'm out of ideas. Maybe somebody else on the list has some other things to try. Sorry.

-Walt

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#12 lore raw
In reply to Walt H

Actually the 2.4.18 seems to be the only one working. I'm sure someone out there have the proper fix for this. Who should I talk to in order to get this fixed? I'm willing to help out in any way I can.

/Nicke

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 22 december 2003 02:36
To: Nicklas Bondesson
Cc: [email protected]
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Quoted 5 lines · Nicklas Bondesson

Now I'm sucessfully booting my system with the 2.4.23 kernel using only one of the drives (hde). There is not a single line in the logs that says anything about the Promise ATARAID driver is beeing fired up, so my guess is that it doesn't load if no one is calling on it. When I try to boot from the RAID it dies right after the "NET4: Unix

domain sockets 1.0/SMP for Linux"

Quoted 8 lines

message. I think it's when the ATARAID driver is about to fire up. I have no idea at all what to do now. It must have something to do with the hard drives since this is the only thing that has changed. Maybee I'm missing some important kernel setting option or so? (I don't think so, but one never know for sure). Also what have changed in the Promise / ATARAID since 2.4.18?.

/Nicke

Not sure what else to tell you. If the pdcraid driver is compiled into the kernel, you'll get a message about it during boot, even if it can't find all the drives. I no longer use the 2.4 kernel series (or pdcraid), so I'm afraid I'm out of ideas. Maybe somebody else on the list has some other things to try. Sorry.

-Walt

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

author
#13 lore raw
Quoted 5 lines · Nicklas Bondesson

Actually the 2.4.18 seems to be the only one working. I'm sure someone out there have the proper fix for this. Who should I talk to in order to get this fixed? I'm willing to help out in any way I can.

/Nicke

Well, not really sure. I thought Alan Cox did the original pdcraid.c for linux some time back, but it really hasn't seen many changes. There were two general Linux changes that took place back around 2.4.22 that might affect you. The first, was the addition of the new Promise IDE driver, which you've got configured. The second, has to do with how Linux reports the geometry of a drive. This change affected my setup which is why I wrote the patch for the pdcraid driver. If your system makes it all the way through kernel booting (which it seems to do), but can't mount the filesystem on the raid, it seems to indicate the latter change affecting you also. The only other thing I can think of, is to use my patch (attached) with patch -p1 < pdcraid.patch from your /usr/src/linux and make sure that you've got both Promise drivers compiled in your kernel. Recompile and see what happens. Outside of that, I'm stuck. Good luck,

-Walt

drivers/ide/raid/pdcraid.c renamed from usr/src/temp/linux-2.4.21-xfs/linux/drivers/ide/raid/pdcraid.c +7 -3
@@ -361,7 +361,11 @@
 	if (ideinfo->sect==0)
 		return 0;
-	lba = (ideinfo->capacity / (ideinfo->head*ideinfo->sect));
-	lba = lba * (ideinfo->head*ideinfo->sect);
-	lba = lba - ideinfo->sect;
+	if (ideinfo->head!=255) {
+		lba = (ideinfo->capacity / (ideinfo->head*ideinfo->sect));
+		lba = lba * (ideinfo->head*ideinfo->sect);
+		lba = lba - ideinfo->sect; }
+	else {
+		lba = ideinfo->capacity - ideinfo->sect;
+	}
 
 	return lba;
#14 lore raw

The patch did not work for me, in fact there was no change at all (anything affected to me). The Promise ataraid driver never gets loaded.

/Nicke

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 23 december 2003 03:07
To: Nicklas Bondesson
Cc: [email protected]
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Quoted 5 lines · Nicklas Bondesson

Actually the 2.4.18 seems to be the only one working. I'm sure someone out there have the proper fix for this. Who should I talk to in order to get this fixed? I'm willing to help out in any way I can.

/Nicke

Well, not really sure. I thought Alan Cox did the original pdcraid.c for linux some time back, but it really hasn't seen many changes. There were two general Linux changes that took place back around 2.4.22 that might affect you. The first, was the addition of the new Promise IDE driver, which you've got configured. The second, has to do with how Linux reports the geometry of a drive. This change affected my setup which is why I wrote the patch for the pdcraid driver. If your system makes it all the way through kernel booting (which it seems to do), but can't mount the filesystem on the raid, it seems to indicate the latter change affecting you also. The only other thing I can think of, is to use my patch (attached) with patch -p1 < pdcraid.patch from your /usr/src/linux and make sure that you've got both Promise drivers compiled in your kernel. Recompile and see what happens. Outside of that, I'm stuck. Good luck,

-Walt

author
#15 lore raw
Quoted 4 lines · Nicklas Bondesson

The patch did not work for me, in fact there was no change at all (anything affected to me). The Promise ataraid driver never gets loaded.

/Nicke

Not sure what else to try. I see that you've already posted to the ata-raid list, so I'd hope that somebody else would reply from there. The pdcraid driver has not received much attention lately, so it may very well be broken for your configuration. Promise has released a binary/source combo driver similar to Nvidia's that will still work in 2.4 - you might give that a try. I have a PDC20276 based onboard raid setup, however, I use 2.6 with device mapper to use it. It's a bit of a pain to setup ATM - especially if you want to boot from it, but it can be done. Good luck,

-Walt

#16 lore raw

Finally got it to work!

There must be a bug causing the Promise card / driver not to be fired up (i'm using ab ASUS P2B motheroard). If I issue the "acpi=off" to the kernel at boot it detects the card and fires up the driver. Everything seems to work now. Who should I post this bug to so it can be fixed in coming releases?

/Nicke

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 23 december 2003 04:47
To: Nicklas Bondesson
Cc: [email protected]
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Quoted 4 lines · Nicklas Bondesson

The patch did not work for me, in fact there was no change at all (anything affected to me). The Promise ataraid driver never gets loaded.

/Nicke

Not sure what else to try. I see that you've already posted to the ata-raid list, so I'd hope that somebody else would reply from there. The pdcraid driver has not received much attention lately, so it may very well be broken for your configuration. Promise has released a binary/source combo driver similar to Nvidia's that will still work in 2.4 - you might give that a try. I have a
PDC20276 based onboard raid setup, however, I use 2.6 with device mapper to use it. It's a bit of a pain to setup ATM - especially if you want to boot from it, but it can be done. Good luck,

-Walt

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

#17 lore raw
In reply to Walt H

The fix for me was to disable all "Power Management" in the kernel and re-compile it. Works like a charm now :)

Hope this can help anyone else with the same problem as me. But again, I think someone should take a look at it cos I think this is a bug for sure.

/Nicke

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 23 december 2003 04:47
To: Nicklas Bondesson
Cc: [email protected]
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Quoted 4 lines · Nicklas Bondesson

The patch did not work for me, in fact there was no change at all (anything affected to me). The Promise ataraid driver never gets loaded.

/Nicke

Not sure what else to try. I see that you've already posted to the ata-raid list, so I'd hope that somebody else would reply from there. The pdcraid driver has not received much attention lately, so it may very well be broken for your configuration. Promise has released a binary/source combo driver similar to Nvidia's that will still work in 2.4 - you might give that a try. I have a
PDC20276 based onboard raid setup, however, I use 2.6 with device mapper to use it. It's a bit of a pain to setup ATM - especially if you want to boot from it, but it can be done. Good luck,

-Walt

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

author
#18 lore raw
Quoted 8 lines · Nicklas Bondesson

The fix for me was to disable all "Power Management" in the kernel and re-compile it. Works like a charm now :)

Hope this can help anyone else with the same problem as me. But again, I think someone should take a look at it cos I think this is a bug for sure.

/Nicke

Nicke,

Glad to hear you got it working. Check out http://acpi.sourceforge.net for acpi related information. If you can get it working with acpi=off and it doesn't when you don't pass that flag, I'd say that there's at least something fishy happening with acpi on your machine.

As for getting it running on 2.6 with dm, the only way I know of is to create a custom initrd file by hand. You have to compile the lvm-dm tools statically and create mappings first. Then in the linuxrc script, you need run dmsetup and point it at the config files to create the devices. Until this is handled better it's not really recommended. Good luck,

-Walt

#19 lore raw

Thanks for the info, but yet I had to go with your patch to get it up and running. I think the patch should be included in the official kernel release.

Who should we send this to?

/Nicke

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 23 december 2003 16:06
To: Nicklas Bondesson
Cc: [email protected]; 'Andre Hedrick'
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Quoted 5 lines · Nicklas Bondesson

The fix for me was to disable all "Power Management" in the kernel and re-compile it. Works like a charm now :)

Hope this can help anyone else with the same problem as me. But again, I think someone should take a look at it cos I think this is a bug for

sure.

Quoted 3 lines

/Nicke

Nicke,

Glad to hear you got it working. Check out http://acpi.sourceforge.net for acpi related information. If you can get it working with acpi=off and it doesn't when you don't pass that flag, I'd say that there's at least something fishy happening with acpi on your machine.

As for getting it running on 2.6 with dm, the only way I know of is to create a custom initrd file by hand. You have to compile the lvm-dm tools statically and create mappings first. Then in the linuxrc script, you need run dmsetup and point it at the config files to create the devices. Until this is handled better it's not really recommended. Good luck,

-Walt

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

author
#20 lore raw
Quoted 7 lines · Nicklas Bondesson

Thanks for the info, but yet I had to go with your patch to get it up and running. I think the patch should be included in the official kernel release.

Who should we send this to?

/Nicke

Hi Nicke,

It's been included in messages to ata-raid, however, I never sent it there marked as PATCH. I suppose I should wrap it up, describe it and sent it off the the ata-raid list for completeness. Maybe it'll save somebody else from the process you just went through :)

-Walt

#21 lore raw
In reply to Walt H

I just realised that I need to have the kernel patched with Walt's pdcraid patch in order to get it to work. Conclusion: disable all Power Management options and patch the kernel with Walt's pdcraid patch (attached). That will do it. I think that Walt's patch should be included in the official kernel.

/Nicke

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Walt H
Sent: den 23 december 2003 04:47
To: Nicklas Bondesson
Cc: [email protected]
Subject: Re: Error mounting root fs on 72:01 using Promise FastTrak TX2000 (PDC20271)

Quoted 4 lines · Nicklas Bondesson

The patch did not work for me, in fact there was no change at all (anything affected to me). The Promise ataraid driver never gets loaded.

/Nicke

Not sure what else to try. I see that you've already posted to the ata-raid list, so I'd hope that somebody else would reply from there. The pdcraid driver has not received much attention lately, so it may very well be broken for your configuration. Promise has released a binary/source combo driver similar to Nvidia's that will still work in 2.4 - you might give that a try. I have a
PDC20276 based onboard raid setup, however, I use 2.6 with device mapper to use it. It's a bit of a pain to setup ATM - especially if you want to boot from it, but it can be done. Good luck,

-Walt

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at
http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

drivers/ide/raid/pdcraid.c renamed from usr/src/temp/linux-2.4.21-xfs/linux/drivers/ide/raid/pdcraid.c +7 -3
@@ -361,7 +361,11 @@
 	if (ideinfo->sect==0)
 		return 0;
-	lba = (ideinfo->capacity / (ideinfo->head*ideinfo->sect));
-	lba = lba * (ideinfo->head*ideinfo->sect);
-	lba = lba - ideinfo->sect;
+	if (ideinfo->head!=255) {
+		lba = (ideinfo->capacity / (ideinfo->head*ideinfo->sect));
+		lba = lba * (ideinfo->head*ideinfo->sect);
+		lba = lba - ideinfo->sect; }
+	else {
+		lba = ideinfo->capacity - ideinfo->sect;
+	}
 
 	return lba;