Re: Promise ATA100 controller and 160G disks
I have FBSD -STABLE running on a Promise Fasttrak 100 TX2 (latest BIOS) with 2 160GB HDDs as RAID1 and it is running fine. Greetz, Frank Hi, does anyone know if the Promise ATA100 controller PCI card supports 160 G disks on -STABLE? Thanks, --Stijn -- Nostalgia ain't what it used to be. ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise ATA100 controller and 160G disks
On Wed, May 26, 2004 at 11:15:02AM +0200, Frank Mueller wrote: I have FBSD -STABLE running on a Promise Fasttrak 100 TX2 (latest BIOS) with 2 160GB HDDs as RAID1 and it is running fine. OK, but I have the older non-raid just ATA100 controller version, which is why I suspect it might not work. To be more precies, my cards (I have 3 in the machine) identify as atapci0: Promise ATA100 controller port 0x7800-0x783f,0x7400-0x7403,0x7000-0x7007,0x6c00-0x6c03,0x6800-0x6807 mem 0xe100-0xe101 irq 5 at device 8.0 on pci1 atapci1: Promise ATA100 controller port 0x8c00-0x8c3f,0x8800-0x8803,0x8400-0x8407,0x8000-0x8003,0x7c00-0x7c07 mem 0xe102-0xe103 irq 10 at device 9.0 on pci1 atapci2: Promise ATA100 controller port 0xa000-0xa03f,0x9c00-0x9c03,0x9800-0x9807,0x9400-0x9403,0x9000-0x9007 mem 0xe104-0xe105 irq 11 at device 10.0 on pci1 Unfortunately I don't have any other model numbers right now, but based on the Promise website I think it is an Ultra100 (non-TX2 version). Anyway, I should have done some more research myself before asking this question because the Ultra100 does have support with an updated BIOS (I missed this the first time apparently): http://www.promise.com/support/download/download2_eng.asp?productId=18category=biosos=100 Thanks for the response though, it caused me to search the Promise site again :) --Stijn -- Help Wanted: Telepath. You know where to apply. pgp0YLeX4DEn5.pgp Description: PGP signature
Re: Promise ATA100 controller and 160G disks
It shouldn't be an problem as long as you upgrade the BIOS in the atacontroller. I'm using an Promise Fasttrak 100 (without TX2) on two 200Gb drives. With the newest bios the controller can use drives over 120GB. Heikki Soerum, Norway. On Wed, 26 May 2004 11:53:24 +0200 Stijn Hoop [EMAIL PROTECTED] wrote: On Wed, May 26, 2004 at 11:15:02AM +0200, Frank Mueller wrote: I have FBSD -STABLE running on a Promise Fasttrak 100 TX2 (latest BIOS) with 2 160GB HDDs as RAID1 and it is running fine. OK, but I have the older non-raid just ATA100 controller version, which is why I suspect it might not work. To be more precies, my cards (I have 3 in the machine) identify as atapci0: Promise ATA100 controller port 0x7800-0x783f,0x7400-0x7403,0x7000-0x7007,0x6c00-0x6c03,0x6800-0x6807 mem 0xe100-0xe101 irq 5 at device 8.0 on pci1 atapci1: Promise ATA100 controller port 0x8c00-0x8c3f,0x8800-0x8803,0x8400-0x8407,0x8000-0x8003,0x7c00-0x7c07 mem 0xe102-0xe103 irq 10 at device 9.0 on pci1 atapci2: Promise ATA100 controller port 0xa000-0xa03f,0x9c00-0x9c03,0x9800-0x9807,0x9400-0x9403,0x9000-0x9007 mem 0xe104-0xe105 irq 11 at device 10.0 on pci1 Unfortunately I don't have any other model numbers right now, but based on the Promise website I think it is an Ultra100 (non-TX2 version). Anyway, I should have done some more research myself before asking this question because the Ultra100 does have support with an updated BIOS (I missed this the first time apparently): http://www.promise.com/support/download/download2_eng.asp?productId=18 category=biosos=100 Thanks for the response though, it caused me to search the Promise site again :) --Stijn -- Help Wanted: Telepath. You know where to apply. -- Throughout history it has been the inaction of those who could have acted, the indifference of those who should have known better, the silence of the voice of justice when it mattered most, that has made it possible for evil to triumph. - Haile Selassie ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise ATA100 controller and 160G disks
Stijn Hoop wrote: Hi, does anyone know if the Promise ATA100 controller PCI card supports 160 G disks on -STABLE? I'm not 100% sure that the Promise controller is the problem here: http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/046070.html Earlier this week, I thought I'd solved the problem: I partitioned the drive in a different computer, and it seemed to be OK in one of the machines where it previously wouldn't work. I then partitioned a second drive and sent them both off with the client to be installed in the server at the colo site. Apon installation, the system hung (as described in the email) ... I don't know what the hell is going on at this point, and it's incredibly frustrating because I'm not even sure how to proceed with fixing it. I guess my point is that it might be worthwhile to try to isolate whether the problem is with the Promise controller, or with 160G drives. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: Promise ATA100 controller and 160G disks
On Wed, May 26, 2004 at 09:28:09AM -0400, Bill Moran wrote: Stijn Hoop wrote: does anyone know if the Promise ATA100 controller PCI card supports 160 G disks on -STABLE? I'm not 100% sure that the Promise controller is the problem here: http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/046070.html Hmm, not good. However, I have misworded my question I guess -- I wanted to know whether those drives _could_ work in that configuration; I did not want to buy non-working drives (I'd have gone for 120G if they didn't work, however I'm reasonably sure now that it'll work). Based on your problems I'll stay away from buying a Samsung drive right now, even though it might not be the real problem. Thanks for the feedback. Earlier this week, I thought I'd solved the problem: I partitioned the drive in a different computer, and it seemed to be OK in one of the machines where it previously wouldn't work. I then partitioned a second drive and sent them both off with the client to be installed in the server at the colo site. Apon installation, the system hung (as described in the email) ... I don't know what the hell is going on at this point, and it's incredibly frustrating because I'm not even sure how to proceed with fixing it. We had a Linux machine here a few weeks ago that wouldn't boot; turned out the memory had gone faulty but we only discovered that after running memtest86 for over 24 hours (having passed lots of tests it suddenly reported failures). It wasn't a case of overheating because it consistently failed to boot; it just took memtest lots and lots of repeats to get the problem to show. Anyway I don't know if it's related to your problem but my point is that you never suspect the right component in the case of hardware failures :( --Stijn -- Nostalgia ain't what it used to be. pgpYsx53jXC99.pgp Description: PGP signature
Re: Promise ATA100 controller and 160G disks
Stijn Hoop wrote: On Wed, May 26, 2004 at 09:28:09AM -0400, Bill Moran wrote: Stijn Hoop wrote: does anyone know if the Promise ATA100 controller PCI card supports 160 G disks on -STABLE? I'm not 100% sure that the Promise controller is the problem here: http://lists.freebsd.org/pipermail/freebsd-questions/2004-May/046070.html Hmm, not good. However, I have misworded my question I guess -- I wanted to know whether those drives _could_ work in that configuration; I did not want to buy non-working drives (I'd have gone for 120G if they didn't work, however I'm reasonably sure now that it'll work). Based on your problems I'll stay away from buying a Samsung drive right now, even though it might not be the real problem. Thanks for the feedback. Don't know if that's the problem or not, but I guess it's as good as I can do with advice right now. I'm pretty damn frustrated with the current problem, myself. Earlier this week, I thought I'd solved the problem: I partitioned the drive in a different computer, and it seemed to be OK in one of the machines where it previously wouldn't work. I then partitioned a second drive and sent them both off with the client to be installed in the server at the colo site. Apon installation, the system hung (as described in the email) ... I don't know what the hell is going on at this point, and it's incredibly frustrating because I'm not even sure how to proceed with fixing it. We had a Linux machine here a few weeks ago that wouldn't boot; turned out the memory had gone faulty but we only discovered that after running memtest86 for over 24 hours (having passed lots of tests it suddenly reported failures). It wasn't a case of overheating because it consistently failed to boot; it just took memtest lots and lots of repeats to get the problem to show. Anyway I don't know if it's related to your problem but my point is that you never suspect the right component in the case of hardware failures :( Good point. If I were fixing the correct problem, it still wouldn't be a problem. I still think it's related to the HDDs though, as the machine had 60+ days uptime without the drives, then wouldn't boot with them, and is now back up and running without them. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
