Thank you for the help guys. I finally got the null modem working with the good drives. I swap in the bad drives, reboot and before I even set CONSOLE ON, the drive was working.
I guess as seen before it took the thing quite a while to fix itself but eventually did. Is there a log file I can read to see what happened? I have a feeling it's gonna be a good year. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] On Behalf Of Bruce Timberlake Sent: Tuesday, December 31, 2002 8:33 AM To: [EMAIL PROTECTED] Subject: Re: [cobalt-developers] Qube 3 Not responding -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > RAID sync can take an hour or so to run, but I thought everything else > worked while the sync was in progress. It should. However, just the other day I had a power outage on my single drive Qube (nearly full 30GB drive). It took almost 2.5 hours for the thing to fix itself... I thought at first that it had been "fried" as I got no reponse, etc. So I connected the null modem cable and watched while it ran fsck a couple of times (there's some sort of internal IDE timeout that reset the process after a while; guess nobody ever figured it could take a LONG time for fsck to run!) Thus my suggestion to connect the null modem cable and see what's really going on... - -- Bruce Timberlake http://www.brtnet.org/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQE+EZyCvLA2hUZ9kgwRAlFnAJ46FvEo4MqLTDdaL3/mVEvfq/EBegCcD3Fp mNYRx6Bw5cbKIdk0MziIyH4= =dsoI -----END PGP SIGNATURE----- _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers _______________________________________________ cobalt-developers mailing list [EMAIL PROTECTED] http://list.cobalt.com/mailman/listinfo/cobalt-developers
