Thanks for your help John. We have a weird setup so I think it was our Cisco switches on the blade center that were messed up. I'm all up and running now. Just curious though, have you ever noticed this error on your HS20s?

May 20 14:58:22 vm1 kernel: sdb : READ CAPACITY failed. May 20 14:58:22 vm1 kernel: sdb : status = 1, message = 00, host = 0, driver = 08 May 20 14:58:22 vm1 kernel: Current sd00:00: sense key Not Ready May 20 14:58:22 vm1 kernel: Additional sense indicates Medium not present May 20 14:58:22 vm1 kernel: sdb : block size assumed to be 512 bytes, disk size 1GB. May 20 14:58:22 vm1 kernel: sdb: Write Protect is on May 20 14:58:22 vm1 kernel: sdb: I/O error: dev 08:10, sector 0 May 20 14:58:22 vm1 kernel: I/O error: dev 08:10, sector 0 May 20 14:58:22 vm1 kernel: unable to read partition table May 20 14:58:22 vm1 kernel: I/O error: dev 08:10, sector 0

It's like it's detecting some drive that doesn't exist...and this it spits that error out over and over. Any ideas?

John Burk wrote:

It is a bug in U4/CentOS3.4. Try this rpm. If it doesn't work or is the wrong arch, install the src rpm and rebuild it. If you need a different version (this is the latest and is working with my CentOS3.4 install on my HS20's)

Or if the rpm's get striped by the mail server, try here:

http://www.broadcom.com/drivers/driver-sla.php?driver=570x-Linux

John Burk

Sr. Technical Director Mainframe Entertainment

604.628.1019

Brendon Colby wrote:

...

Greetings:

I know it's been mentioned before that the tg3 driver in CentOS 3.4 is buggy. I had to revert to 3.4 today from 4 (fresh install) and now I have no link and thus no network. I'm wondering if this is caused by this bug and what the work-around is.

Thanks.

Brendon Colby _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos

---

---

CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos