we are running raid 5 configuration on a fujitsu siemens server - 3 drives and a hotswap. System crashed and when we try to mount the exchange databases again it gives error that there is no diskspace, but there is plenty.. any ideas? Specialist says its harddrive failure but he wasnt to sure..
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
Hard drive going bad, you need to recover all your data as soon as possible. It is likely that the RSC has exceeded the space allocated to spare disc space, however, you can check this by downloading and running HDD tune (freeware) to ascertain the disc health and any bad sectors, if there are more than 2 bad sectors and the RSC on the health page is shown in red or yellow, the drive needs replacing
1) Go to www.devicedoctor.com 2) Download and install the software 3) Run the software and click on scan 4) It will pick the correct audio driver for you, click download and install the driver 5) This will hopefully restore your sound
As RAID uses block for block copy, a re-sync when adding in a new mirror on RAID 1 will take some time, and system performance will be affected during that time period. There is no indication in windows if the rebuild is complete as this is being done on a hardware level by the controller. Both Raid 5 and RAID 10 have added benefits , but alos require more storage (a lot more in case of RAID 10 as you will have effectivly 3 spares for 1 data.) Raid 5 has the best space/protection pay off, but will be slightly slower than both RAID 1 and RAID 0 as parity has to be calculated for each write. As caffineshark states your best option is to use a combination of the methods we have described:
1) Use the two SATA disks as RAID 0 for performance and reliability. 2) Make backup images of the boot volume using Drive Image / Ghost and store on external USB IDE drive, and then offsite.
If you make an image in the USB drive, make sure you run a verfiy of the image after creation to make sure it's valid.
This should allow you to restore in a DR sutuation, but also give you some decent HDD crash protection.
The crash sounds more like a hard drive failure, or maybe something was improperly written to the master boot record sector or another such important sector. I'd try to fix the MBR (google that: "Fix MBR windows xp") to see if everything is really gone or just hidden because the boot record (index) is lost.