TheR

Member
  • Content Count

    25
  • Joined

  • Last visited

Community Reputation

0 Neutral

About TheR

  • Rank
    Member
  1. Another horror story? It looks I just don't have luck with WD Raptors, model WDC WD3000BLFS-0. I am running iSCSI storage server (Ubuntu 10.04) with 4 of them in Linux RAID10 on LSI on board controller and 4 of them in HW LSI raid controller. I had already upgraded firmware because of the problem with LSI raid controller described here Then there is this problem https://bugzilla.redhat.com/show_bug.cgi?id=512613 which is alive on 10.04 (althow I did't have the guts to try it for a year now). Now after more than 200 days uptime, last night software raid failed on me. <Log> Jun 6 20:24:54 ozssan kernel: [2279698.613730] mptbase: ioc0: LogInfo(0x31110b00): Originator={PL}, Code={Reset}, SubCode(0x0b00) Jun 6 20:24:54 ozssan kernel: [2279698.613918] mptbase: ioc0: LogInfo(0x31110b00): Originator={PL}, Code={Reset}, SubCode(0x0b00) Jun 6 20:24:54 ozssan kernel: [2279698.628061] mptbase: ioc0: LogInfo(0x30050000): Originator={IOP}, Code={Task Terminated}, SubCode(0x0000) Jun 6 20:24:54 ozssan kernel: [2279698.628069] sd 8:0:6:0: [sdd] Unhandled error code Jun 6 20:24:54 ozssan kernel: [2279698.628072] sd 8:0:6:0: [sdd] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Jun 6 20:24:54 ozssan kernel: [2279698.628076] sd 8:0:6:0: [sdd] CDB: Read(10): 28 00 18 ad 55 bf 00 00 08 00 Jun 6 20:24:54 ozssan kernel: [2279698.628085] end_request: I/O error, dev sdd, sector 414012863 Jun 6 20:24:54 ozssan kernel: [2279698.636488] mptbase: ioc0: LogInfo(0x30050000): Originator={IOP}, Code={Task Terminated}, SubCode(0x0000) Jun 6 20:24:54 ozssan kernel: [2279698.636493] mptbase: ioc0: LogInfo(0x30050000): Originator={IOP}, Code={Task Terminated}, SubCode(0x0000) Jun 6 20:24:54 ozssan kernel: [2279698.636498] mptbase: ioc0: LogInfo(0x30050000): Originator={IOP}, Code={Task Terminated}, SubCode(0x0000) Jun 6 20:24:54 ozssan kernel: [2279698.636502] mptbase: ioc0: LogInfo(0x30050000): Originator={IOP}, Code={Task Terminated}, SubCode(0x0000) Jun 6 20:24:54 ozssan kernel: [2279698.636507] mptbase: ioc0: LogInfo(0x30050000): Originator={IOP}, Code={Task Terminated}, SubCode(0x0000) Jun 6 20:24:54 ozssan kernel: [2279698.636511] mptbase: ioc0: LogInfo(0x30050000): Originator={IOP}, Code={Task Terminated}, SubCode(0x0000) Jun 6 20:24:54 ozssan kernel: [2279698.636516] mptbase: ioc0: LogInfo(0x30050000): Originator={IOP}, Code={Task Terminated}, SubCode(0x0000) Jun 6 20:24:54 ozssan kernel: [2279698.636520] mptbase: ioc0: LogInfo(0x30050000): Originator={IOP}, Code={Task Terminated}, SubCode(0x0000) Jun 6 20:24:54 ozssan kernel: [2279698.636525] mptbase: ioc0: LogInfo(0x30050000): Originator={IOP}, Code={Task Terminated}, SubCode(0x0000) Jun 6 20:24:54 ozssan kernel: [2279698.636532] raid10: sdd1: rescheduling sector 828025600 Jun 6 20:24:54 ozssan kernel: [2279698.644896] sd 8:0:6:0: [sdd] Unhandled error code Jun 6 20:24:54 ozssan kernel: [2279698.644898] sd 8:0:6:0: [sdd] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Jun 6 20:24:54 ozssan kernel: [2279698.644902] sd 8:0:6:0: [sdd] CDB: Read(10): 28 00 1c 9b 48 0f 00 00 30 00 Jun 6 20:24:54 ozssan kernel: [2279698.644910] end_request: I/O error, dev sdd, sector 479938575 Jun 6 20:24:54 ozssan kernel: [2279698.653200] raid10: sdd1: rescheduling sector 959876944 Jun 6 20:24:54 ozssan kernel: [2279698.661417] raid10: sdd1: rescheduling sector 959876952 Jun 6 20:24:54 ozssan kernel: [2279698.669461] raid10: sdd1: rescheduling sector 959876960 Jun 6 20:24:54 ozssan kernel: [2279698.677347] raid10: sdd1: rescheduling sector 959876968 Jun 6 20:24:54 ozssan kernel: [2279698.685027] raid10: sdd1: rescheduling sector 959876976 Jun 6 20:24:54 ozssan kernel: [2279698.692536] raid10: sdd1: rescheduling sector 959876984 Jun 6 20:24:54 ozssan kernel: [2279698.692540] sd 8:0:6:0: [sdd] Unhandled error code Jun 6 20:24:54 ozssan kernel: [2279698.692542] sd 8:0:6:0: [sdd] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK Jun 6 20:24:54 ozssan kernel: [2279698.692545] sd 8:0:6:0: [sdd] CDB: Write(10): 2a 00 00 29 7b 37 00 00 08 00 Jun 6 20:24:54 ozssan kernel: [2279698.692550] end_request: I/O error, dev sdd, sector 2718519 Jun 6 20:24:54 ozssan kernel: [2279698.692553] raid10: Disk failure on sdd1, disabling device. Jun 6 20:24:54 ozssan kernel: [2279698.692554] raid10: Operation continuing on 3 devices. </log> And after 8 seconds second disk failed and after another 20 seconds third disk failed too. Same log for all of drives. Pointless to say raid array was down. Interesting point is that 4'th drive didn't fail. But this drive has been replaced two months ago and has been powered up for about 60 days. Is there another ticking bomb in WD drives? by TheR
  2. TheR

    SSD Reliability

    This data kinda scares me. Aren't SSD's suppose to be more reliable than HDD's. And I am very surprised how much Sandforce disks die. Since Sandforce has some technology which should prevent loosing data if flash dies it looks like manufacturing problem or it is all a big bluff. by TheR
  3. It looks like Kingston is a way to go http://geizhals.at/eu/a415027.html by TheR
  4. To answer to myself. It looks like there is very litle ddr3 demand for 4GB non-ECC modules too, since there are hard to find and also 3-4x more expensive than registrerred ones, which are probably on high demand for servers and therefor ''cheap''-er. I hate economy rules. We need 64bit only computers soon by TheR
  5. Here in Europe you can get 4GB registered DIMM for less than 100€ but the same amount of unbuferred DIMM costs almost 400€. Is it "Only Macs are using it, so lets charge them more" or is production too smal or what. BOM should be smaller since you don't need extra buffer chip. On the other side 2GB UDIMMs are sold around 35€ while 4GB RDIMMs are around 45€. by TheR
  6. This is a good information. It looks like will have to wait for (probably) more expensive Xeon version of CPU , because ECC should be essential for 24/7 machine. by TheR
  7. New Intel Corei7 procesors support 6 memory stick, which can be 4GB each for total of 24GB RAM. Which is quite a lot. And indeed some motherboard makers already have products that claim support for 24GB of RAM. Memory is DDR3 ECC, but not registered. I did some research and found that registered memory is mainly neeaded by servers with big amounts of memory, because memory controller would not be able to work with larger amounts of memory. My question is. Might Corei7 have some problems using this large amount of non buffred memory? by TheR
  8. Years back I remember there was quite performance penalty when going from 2 DIMMS to 4 DIMMS RAM configuraction. I don't remember why was it so, but is this still a case with moderen chipsets and DDR2 memory. by TheR
  9. I just want to inform you that driver for EX8350 is included in Ubuntu 7.04. The card was recognized and installed automaticaly and I was able to access 2T partition instantly. It looks like driver is now part of Linux kernel. Festy is based on 2.6.20. by TheR
  10. TheR

    SSD's = Defrag is a thing of the past?

    He, he. SSD is fragmented by default , since it's logic tries to spread writes trough the available space because flash cell can be written only about million times before it dies. by TheR
  11. Can anybody confirm if Promise SuperTrak EX8350 driver is included in Linux Kernel 2.6.18 and above and therefore will be available in upcoming OpenSuse 10.2 Thank you TheR
  12. I am running EX8350 with more or less no problems on SuSE 10.0. More problems is of course when kernel gets updated . Speeds are around 50MB/s on 8 disk RAID 5 array. What I would like to know is which Linux distros do you run EX8350 on. Promise officialy supports only SuSE and RedHat with drivers so far and I am really interested changing to Ubuntu 606. by TheR
  13. SATA works too. Tyan Tomcat MB. I am stil trying to compile the drivers but no result at all. In a Linux kernel newsgroup http://marc.theaimsgroup.com/?l=linux-kern...28988110335&w=2 is a thread saying that drivers will be included in the kernel. But in 2.6.16.1 are still not there. How to compile driver for Suse Linux? by TheR
  14. <quote> #insmod shasta.ko Killed #lsmod Module Size Used by <the command hangs here> The output of dmesg is; CODE shasta: no version for "struct_module" found: kernel tainted. shasta: module not supported by Novell, setting U taint flag. Unable to handle kernel paging request at ffffffff8899bec0 RIP: <ffffffff80159593>{load_module+2851} PGD 103027 PUD 105027 PMD 7d61e067 PTE 0 Oops: 0002 [1] SMP CPU 1 etc....... </quote> Geronimo4711 were you able to resolve your problem and how? by TheR
  15. TheR

    Loading OS onto RAID 5 array?

    On server I would not prefer instaling OS on RAID5 drive, because if something fails and OS has to be reinstaled it can be quite messy to install RAID5 drivers if they are not already supported by OS. by TheR