Jump to content

waterlou

Folding Member
  • Content Count

    261
  • Joined

  • Last visited

About waterlou

  • Rank
    Member

Profile Information

  • Location
    B-AH-STON
  1. Hey All - I am shutting down the army for a while. I will keep the MacMini running, but have decided that I need to keep it cool for a bit. After recently achieving a few milestones, I wasn't about to crack the top 10 with the rigs (3) and points (14K / week) I was getting. In any case, this will allow hardnrg to have a chance and FINALLY catch up! Cheers all! Waterlou
  2. Thank you king! Good luck!
  3. waterlou

    Up We Go !

    Congrats Jude! You have company in the x,000,000 club!
  4. waterlou

    Up We Go! X 2

    Well - it took me a year to go from 0-100K ... and now a year later, I am passing into new territory... bye bye x00,000s and hello x,000,000 !! 1,000,000 points should be coming through tonight! Cheers all!
  5. So then its straight forward. Load up WinXP install (don't forget your floppy for the raid driver). Get to the install screen and use the recovery console. All you need to do there is a fixmbr I think (you'll see two of them, fixboot and fixmbr). Run those and you should be good to go. Sometimes the MBR gets messed up. Good luck!
  6. I think I found out what the problem is. I re-flashed the BIOS on the card to non-raid so I could run some diagnostics on the drive. And it looks like the PSU fried the drive because none of the diagnostic tests can run. ARGH!
  7. Happens to me all the time -- go to your bios. Check the hard drives listed there. Your Raid-0 should be listed there. Then check to see your HDD drive sequence - your Raid array should be first. Then check your boot device sequence, and ensure that the HDD is listed there as an option (typically after cd-rom and/or floppy). Good luck!
  8. No, sorry. There are 4 disks. 2 sets of 2. Each group is configured as a Raid-0 array. I just succeeded in creating an array with the WD320s once I brought them on line. And I think I am close to getting the WD250s raid going. When I go into the Raid config manager it notifies me that all 4 of the drives are "reserved", which tells me they are "stamped" with something. I updated the Windows based Sil RaidSata5 utility and it shows a "blue" disk flagged as a "pass through". So I think the metadata that the disks are stamped with (ie: the Raid config data in the boot sector) is corrupted. And it's showing one of the disks as a pass-through (or JBOD) and hence an invalid raid array. Causing windows to take forever to boot up... Any advice is appreciated on the subject! Thanks! ps: the good news is that all my "valuable" data (pics, movies, music, etc) is backed up on a USB drive on a weekly basis!
  9. Hey Guys - I've been running a 4 drive raid cabinet for 2 years with little to no issue. 2 Raid-0 arrays were configured and are connected via eSata to a card in my file server. So the psu on my Raid cabinet started to fail and the disks would power suddenly down. So, I conveniently replaced it with a new one (350W). Everything is fine on boot, the Raid conroller BIOS sees all 4 drives (WD 250 x2, WD 320 x2) Then things get hoaky in windows. First, windows takes forever mins to boot up... I think due to the following log file detail. I decided to unplug two drives (WD320) to try and get one raid array up and running. When I go to the Sil Sata Raid manager, and attempt to recreate the raid group from drives that ALREADY were in a group (but no longer identified). Here is the log file from the raid manager software. 01/10/08 02:24.31 PM Controller 0 - Sil3124r5 Controller Informational Begin group discovery 01/10/08 02:24.31 PM Controller 0 - Sil3124r5 Device Error SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried) 01/10/08 02:24.31 PM Controller 0 - Sil3124r5 Device Error SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried) 01/10/08 02:24.31 PM Controller 0 - Sil3124r5 Device Error SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried) 01/10/08 02:24.31 PM Controller 0 - Sil3124r5 Device Error SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried) 01/10/08 02:24.31 PM Controller 0 - Sil3124r5 Device Error SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried) 01/10/08 02:24.31 PM Controller 0 - Sil3124r5 Device Error SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried) 01/10/08 02:24.31 PM Controller 0 - Sil3124r5 Device Error SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried) 01/10/08 02:24.31 PM Controller 0 - Sil3124r5 Device Error SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried) 01/10/08 02:24.31 PM Controller 0 - Sil3124r5 Controller Informational Initialization Complete 01/10/08 02:31.07 PM Controller 0 - Sil3124r5 Application Informational Database initialized.. 01/10/08 02:31.51 PM Controller 0 - Sil3124r5 Device Informational Segment created, PathId 2, TargetId 0, PBN 0, Capacity 1d1c5170, Segment Count 1 01/10/08 02:31.51 PM Controller 0 - Sil3124r5 Device Informational Segment created, PathId 3, TargetId 0, PBN 0, Capacity 1d1c5170, Segment Count 1 01/10/08 02:31.51 PM Controller 0 - Sil3124r5 RAID Informational Start Create, Group 0 01/10/08 02:31.51 PM Controller 0 - Sil3124r5 RAID Informational Configure RAID Group task 01/10/08 02:31.51 PM Controller 0 - Sil3124r5 Device Error SRB Status 84, Path/Target 2:0, Sense Data 00:0b:00:0 (ShouldMetadataRequestBeRetried) 01/10/08 02:31.51 PM Controller 0 - Sil3124r5 RAID Error Create aborted, Group 0 01/10/08 02:31.51 PM Controller 0 - Sil3124r5 RAID Warning Member 0 (Path ID = 2, Target ID = 0 dropped from group 0 "Volume A" 01/10/08 02:31.51 PM Controller 0 - Sil3124r5 Device Informational Segment deleted, PathId 2, TargetId 0, PBN 0, Capacity 1d1c5170, Segment Count 0 01/10/08 02:31.51 PM Controller 0 - Sil3124r5 RAID Warning Group 0 "Volume A" is OFFLINE 01/10/08 02:31.51 PM Controller 0 - Sil3124r5 RAID Warning Member 1 (Path ID = 3, Target ID = 0 dropped from group 0 "Volume A" 01/10/08 02:31.51 PM Controller 0 - Sil3124r5 Device Informational Segment deleted, PathId 3, TargetId 0, PBN 0, Capacity 1d1c5170, Segment Count 0 I've been running raid for years. And this one is baffling me. Looks like it's finding some sort of corrupted metadata and refuses to over-ride it. So I can't recreate the group, and thus can't create a new drive in windows. When all 4 drives are connected, and I go into the RAID BIOS on bootup, one of the new WD320 shows as a "logical" drive and all the others as "reserved". Any advice would be welcome!
  10. ===UPDATED=== Found the answer I was looking for!! http://forums.overclockersclub.com/index.p...st&p=351709 Thanks! ============ Hey all - I've done a few searches. And the closest I came to finding the solution was connecting "two PSUs together" using the ole paperclip in the lime-green connector slot. The PS on my raid storage case has failed. It was an el cheapo 350W supply that was modded to be used with a switch (assuming they just connected some of the ATX harness wires to the switch). I went out and bought a low-end 350W ANTEC supply at Microcenter and really am not interested in re-doing the switch setup that was previously there. Is there a way to get the power-supply to fire up using just the on/off switch found on the back of it? Bypassing the ATX hookup? I just need power from the 4 molex plugs to power the drives. That's all. Thanks in advance! Waterlou
  11. I am getting about 920 ppd on my T2500. Not bad for a lil laptop
  12. For Whom the Bell Tolls!! Sorry sdy284
  13. Bummer chavalcito ... but thanks for continuing to add to the cause!
  14. Queue Jaws music ... Just a couple days away! averaging 20k weeks, not bad w/ 3 full time and 1 part time machine Cheers! And Keep Folding!
×
×
  • Create New...