|
#1
December 27th, 2007, 01:33 PM
| |||
| |||
| RAID drive has a bad b-node tree error I set up a RAID using 4 Segate 320GB SATA drives in it's own box. It is connected to my G5 (OS 10.4.1) via a Highpoint RocketRaid 2210 card. After 2 months, I have gotten the b-node tree error twice. The drive fails to mount and drive utilities (including Drive Genius, DiskWarriror) can't fix it. I was able to use Drive Rescue 2 to get the info off of it, but I am concerned as to why this keeps happening. I can reinitialize the drive and get it working again, but this is not a solution. Could it be defective drives or can it be something else? Any help is appreciated.  |
|
#2
December 27th, 2007, 03:00 PM
| |||
| |||
| What level RAID are you using? Do you have a spare Seagate you can swap for any one of the current 4 drives, one at a time? My first suspicion would be the controller card as timing is a huge issue with RAID. Could also be a funky cable as that host is connected by a separate cable to each drive, correct? Are you really using only 10.4.1? That's not a typo? If true, you might want to check to see if a later version of Tiger offers better support for that RAID card. 10.4.1 is kind of outdated now.... Last edited by sp_clark; December 27th, 2007 at 03:09 PM. Reason: afterthoughts |
|
#3
January 2nd, 2008, 11:07 AM
| |||
| |||
| RAID 5. I don't have extra drives, but I will look into the controller card. My OS ids 10.4.10, so I'll look into that as well. Thanks. |
 |
« Anyone recommend some speakers for iMac?
|
usb drive in system profiler but not in finder or disk utility »
| Thread Tools | |
|
|
All times are GMT -5. The time now is 11:00 AM.
