Quote:
|
Originally Posted by DebonairOne
Hey Hey... My one server is back online and operational... I guess OSv4 just took a long time to do what it was supposed to do... anyway, my only issue with this one is the cracked raid that I can't get around... I posted this info in another thread, but haven't found a solution that works for me yet... if anyone has resolved this and can post their process, I would appreciate it..
It was posted to use the following command.. config devices config individual ##### force - where ##### is the number of the cracked raid device... so mine looks like this... config devices config individual 50000 force - and it doesn't repair the raid...
Any thoughts..... and thanks to all registered geeks for their help on getting this server resurrrected in the first place...
|
Ok...this is a 2000 right? Is this a RAID 0 or RAID 1 setup? If it's a RAID 0, there is an idea you might try. I used this trick when I had a RAID 0 that was getting marginal on me. When I'd boot the server the system would say the array failed. Now the risk you run with this idea is that if something is terribly wrong you might loose data. Then in that case you might want to image your drives. No idea if that'll do any good in case something does go wrong but I'll leave that to you to decide. Then go into Disk Utilities and then Disk Startup Settings. Set the server to perform a disk check always (so it scans when the system is started up or rebooted) and then make sure that it is set to automatically fix errors. After that power the server down (don't just restart it) but shut it down. When the system starts up it will automatically start checking the disks. If you have secure HTTP enabled you probably won't be able to use the web interface. In that case I'd shut that down before shutting down the server so that you can use regular HTTP to monitor the disk check status.
When I had that problem it would run the disk check and the thing would pass. I did that for about a week. I finally got tired of waiting for the system to start up so I backed up everything (was too lazy to do it in the first place) and then reconfigured the drives to JBOD and back to RAID 0. Everything worked fine after that. I'm not sure why it happens. I know that the system had been configured as a RAID 0 for a couple of years by then and hadn't ever been reformatted.
Hope it works.
INT 20h