Only One Promise
In my unsuccessful effort to get two Promise SATA150 cards working, I choose to try it with only one card. All works well with one card. No reply from the driver maintainer, must be a busy man, that or he is ignoring me.
In my unsuccessful effort to get two Promise SATA150 cards working, I choose to try it with only one card. All works well with one card. No reply from the driver maintainer, must be a busy man, that or he is ignoring me.
余艾蕾 signed us up for Netflix, with a new baby it seemed a good way to watch movies. Actually we have been really behind with our movie watching for quite a while now. One of the first movies we got was Les Triplettes de Belleville. A wonderful dream sequence of the French Mafia trying to get the excitement of les Tour de France in North America. Unless you are adverse to cartoons, it comes highly recommended.
My Promise SATA150™ TX4 cards came in yesterday. After getting them both working in a system I started using them with Debian’s kernel, it got an ata8: DMA timeout error and froze. I upgraded to the 2.6.9-rc1 kernel, not it gets ata4: command timeout errors and freezes. I popped off an email to the maintainer, hopefully he will have an idea.
I have generally had good luck with Promise products. Today I had an order put in for two Promise TX4 cards. These are potential replacements for my RocketRAID 1820 cards. If they work I might be getting twentytwo more of them.
On June fourth I resolved my HighPoint RocketRAID 1820 issues, or so I thought. The drives on the RocketRAID 1820 cards have been getting little use until yesterday when I tried copying some data on them. Linux, probably because of the proprietary driver, started returning errors:
SCSI error : <0 0 4 0> return code = 0x25050000 end_request: I/O error, dev sde, sector 614175 Abort called pid: 5357 target: 4 lun: 0 reason 0 Abort called pid: 5358 target: 4 lun: 0 reason 0 Abort called pid: 5359 target: 4 lun: 0 reason 0 Abort called pid: 5360 target: 4 lun: 0 reason 0 Abort called pid: 5361 target: 4 lun: 0 reason 0 Abort called pid: 5362 target: 4 lun: 0 reason 0 Abort called pid: 5363 target: 4 lun: 0 reason 0 Abort called pid: 5364 target: 4 lun: 0 reason 0 RR182x: Bus Reset: host=0, channel=0 target=4
I can’t get the systems to consistently do it.
Powered by WordPress