You may have used Dell's installation utilities, which would have loaded the appropriate drivers for you. You cannot use that process here. I would suggest nLiteOS.com.
Over the top repair has the machine booting, thanks FLASH & PCMEINERS.
I was able to perform simple file back up accept for some directories. Second disk with SP2 still not installed.
I went to use the Windows back up utility and start with system backup and many files skipped with following:
Backup Type: Copy
Backup started on 8/25/2015 at 3:54 PM. Warning: Unable to open "C:\NTDETECT.COM" - skipped. Reason: The file or directory is corrupted and unreadable.
Error: Could not access portions of directory System State\Boot Files\C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\DAO. You may not have permission to open the file, or the directory may be missing or damaged. Please contact the owner or administrator.
Warning: Unable to open "C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\DAO" - skipped. Reason: The file or directory is corrupted and unreadable.
Error: Could not access portions of directory System State\COM+ Class Registration Database. You may not have permission to open the file, or the directory may be missing or damaged. Please contact the owner or administrator.
Error: Could not access portions of directory System State\Registry. You may not have permission to open the file, or the directory may be missing or damaged. Please contact the owner or administrator.
Backup completed on 8/25/2015 at 3:54 PM. Directories: 4 Files: 1 Bytes: 297,196
Should I run chkdsk to attempt to repair? Try to rebuild array? Serversupply sent a seagate refurb but assured it has same DELL firmware with DELL code. Was expecting a wd.
It should boot on a degraded array (single disk failed in RAID 5).
You can still rebuild in place of the failed disk, but as far as Windows goes, I would attempt to repair the OS from the installation CD (chkdsk /r, fixboot) after rebuilding the failed disk.
Thank you for your help. Should I place the new drive in failed drive position or use the hot-swappable bay? And just to clarify then, array rebuild will start automatically before OS load, or OS is required with Dell Server Management Software?
When I tried to load OS from cd I get a stop 0x0000007B error before recovery console option.
Thank you for your help. Should I place the new drive in failed drive position or use the hot-swappable bay? And just to clarify then, array rebuild will start automatically before OS load, or OS is required with Dell Server Management Software?
You could use OMSA from the OS, but since you can't access the OS, you won't use it here.
When I tried to load OS from cd I get a stop 0x0000007B error before recovery console option.
You need to give Windows the driver for the RAID controller (use the 'hard drive' format, must first be run to extract contents):
The server shipped without an OS or floppy drive (unavailable). I was able to load Server 2003 then. I don't recall any additional steps. Did something change?
A refurbed drive will be here tomorrow. Is it better to sort out good boot on the two assumed 'good' drives, or add the replacement drive to array before I run chkdsk and try to sort out bad boot.
Also, I read about chkdsk and even rebuild possibly damaging data in remaining disks. Do you think backing up images of the two good drives is required? Maybe that is only if bad drive is left in place, I did disconnect the bad drive completely.
The S100 is a rebranded Intel chipset RAID - it is managed pre-boot. I refuse to use the S-series controllers, so I'll take your word that they are more easily irreparably damaged. I will also recommend against EVER using an S-series controller.
Your advice is noted. So is the issue purely controller, not RAID choice? Would not have made a difference if it was RAID 1 or 5? Our older DELL server runs RAID 1, no problems but unaware of controller.
Your thoughts or any experience on data recovery service, besides the obvious expense?
"Is an array rebuild still possible once I replace same part no. HDD? "
Flash -
"You can still rebuild in place of the failed disk, but as far as Windows goes, I would attempt to repair the OS from the installation CD (chkdsk /r, fixboot) after rebuilding the failed disk."
The S100 controller is a driver based controller, meaning that the Windows driver must be loaded and started before most functions, including a rebuild can be preformed. You will not be able to rebuild the drive before repairing Windows.
The repair will need to be attempted without rebuilding the drive, which should be fine as even though the array is degraded, the virtual disk presented to the OS should remain unchanged.
Please note that on this series of controllers I have seen this issue many times and attempts at repairing the OS are mosty in vain.
I thought that the S100 / S300 were manufactured by a company called Dot Hill. Although it is managed pre-boot where you can create raid arrays and such, a rebuild requires the driver to be started within Windows. These controllers seem to work fine until you lose a drive, then all bets are off. I definitely agree with Flash, do not use them on anything but low end systems.
Data recovery can get your data back, but it is certainly expensive. Typically, repairing the OS and repairing the RAID array are completely separate and independent procedures, so you can try to repair the OS without repairing the array (although it is usually good practice to repair the array first, 1) it will be slower in a degraded state, and 2) some read/write errors can't be corrected). If you are successful in repairing the OS, then you can focus on repairing the array if admin4u is correct.
Slip streaming driver got me to recovery console, much appreciate Flash.
Is chkdsk /r /fixboot conservative enough or only option, I have read that if array is further degraded within online disks, a chkdsk could further damage data. Is it possible to start OMSA at this point?
Is it possible to back up C: or D: partitions in this state?
theflash1932
9 Legend
•
16.3K Posts
0
August 24th, 2015 16:00
You may have used Dell's installation utilities, which would have loaded the appropriate drivers for you. You cannot use that process here. I would suggest nLiteOS.com.
pcmeiners
4 Operator
•
1.8K Posts
0
August 25th, 2015 16:00
Possible you may need to add the raid drivers again.
Flip a coin, I would overwrite the matrox settings, you can always change the setting you get.
jlapointe
12 Posts
0
August 25th, 2015 17:00
Over the top repair has the machine booting, thanks FLASH & PCMEINERS.
I was able to perform simple file back up accept for some directories. Second disk with SP2 still not installed.
I went to use the Windows back up utility and start with system backup and many files skipped with following:
Backup Type: Copy
Backup started on 8/25/2015 at 3:54 PM.
Warning: Unable to open "C:\NTDETECT.COM" - skipped.
Reason: The file or directory is corrupted and unreadable.
Error: Could not access portions of directory System State\Boot Files\C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\DAO.
You may not have permission to open the file, or the directory may be missing or damaged.
Please contact the owner or administrator.
Warning: Unable to open "C:\PROGRAM FILES\COMMON FILES\MICROSOFT SHARED\DAO" - skipped.
Reason: The file or directory is corrupted and unreadable.
Error: Could not access portions of directory System State\COM+ Class Registration Database.
You may not have permission to open the file, or the directory may be missing or damaged.
Please contact the owner or administrator.
Error: Could not access portions of directory System State\Registry.
You may not have permission to open the file, or the directory may be missing or damaged.
Please contact the owner or administrator.
Backup completed on 8/25/2015 at 3:54 PM.
Directories: 4
Files: 1
Bytes: 297,196
Should I run chkdsk to attempt to repair? Try to rebuild array? Serversupply sent a seagate refurb but assured it has same DELL firmware with DELL code. Was expecting a wd.
Thanks again
theflash1932
9 Legend
•
16.3K Posts
0
August 24th, 2015 11:00
It should boot on a degraded array (single disk failed in RAID 5).
You can still rebuild in place of the failed disk, but as far as Windows goes, I would attempt to repair the OS from the installation CD (chkdsk /r, fixboot) after rebuilding the failed disk.
jlapointe
12 Posts
0
August 24th, 2015 14:00
Thank you for your help. Should I place the new drive in failed drive position or use the hot-swappable bay? And just to clarify then, array rebuild will start automatically before OS load, or OS is required with Dell Server Management Software?
When I tried to load OS from cd I get a stop 0x0000007B error before recovery console option.
theflash1932
9 Legend
•
16.3K Posts
0
August 24th, 2015 14:00
You could use OMSA from the OS, but since you can't access the OS, you won't use it here.
You need to give Windows the driver for the RAID controller (use the 'hard drive' format, must first be run to extract contents):
http://www.dell.com/support/home/us/en/19/Drivers/DriversDetails?driverId=D1RP4
Because 2003 is old and stupid, you will need to load this via floppy disk or use nLiteOS.com to integrate it into your installation media.
jlapointe
12 Posts
0
August 24th, 2015 15:00
The server shipped without an OS or floppy drive (unavailable). I was able to load Server 2003 then. I don't recall any additional steps. Did something change?
jlapointe
12 Posts
0
August 24th, 2015 16:00
A refurbed drive will be here tomorrow. Is it better to sort out good boot on the two assumed 'good' drives, or add the replacement drive to array before I run chkdsk and try to sort out bad boot.
Also, I read about chkdsk and even rebuild possibly damaging data in remaining disks. Do you think backing up images of the two good drives is required? Maybe that is only if bad drive is left in place, I did disconnect the bad drive completely.
Thanks again. I will work on nLiteOS stuff next.
theflash1932
9 Legend
•
16.3K Posts
0
August 24th, 2015 22:00
The S100 is a rebranded Intel chipset RAID - it is managed pre-boot. I refuse to use the S-series controllers, so I'll take your word that they are more easily irreparably damaged. I will also recommend against EVER using an S-series controller.
jlapointe
12 Posts
0
August 24th, 2015 22:00
Your advice is noted. So is the issue purely controller, not RAID choice? Would not have made a difference if it was RAID 1 or 5? Our older DELL server runs RAID 1, no problems but unaware of controller.
Your thoughts or any experience on data recovery service, besides the obvious expense?
Thanks again.
Admin4U
112 Posts
0
August 24th, 2015 22:00
jlapointe
"Is an array rebuild still possible once I replace same part no. HDD? "
Flash -
"You can still rebuild in place of the failed disk, but as far as Windows goes, I would attempt to repair the OS from the installation CD (chkdsk /r, fixboot) after rebuilding the failed disk."
The S100 controller is a driver based controller, meaning that the Windows driver must be loaded and started before most functions, including a rebuild can be preformed. You will not be able to rebuild the drive before repairing Windows.
The repair will need to be attempted without rebuilding the drive, which should be fine as even though the array is degraded, the virtual disk presented to the OS should remain unchanged.
Please note that on this series of controllers I have seen this issue many times and attempts at repairing the OS are mosty in vain.
jlapointe
12 Posts
0
August 24th, 2015 22:00
Based on Admin4U experience, do you think slipstreaming the driver into server 2003 setup is still worth a try? Still attempt repair with NTLiteOS?
And your certain the OS deployment utility Dell provided wont get the setup disk to recovery console?
Thanks again to you and Admin4U
Admin4U
112 Posts
0
August 24th, 2015 22:00
I thought that the S100 / S300 were manufactured by a company called Dot Hill. Although it is managed pre-boot where you can create raid arrays and such, a rebuild requires the driver to be started within Windows. These controllers seem to work fine until you lose a drive, then all bets are off. I definitely agree with Flash, do not use them on anything but low end systems.
theflash1932
9 Legend
•
16.3K Posts
0
August 25th, 2015 12:00
Data recovery can get your data back, but it is certainly expensive. Typically, repairing the OS and repairing the RAID array are completely separate and independent procedures, so you can try to repair the OS without repairing the array (although it is usually good practice to repair the array first, 1) it will be slower in a degraded state, and 2) some read/write errors can't be corrected). If you are successful in repairing the OS, then you can focus on repairing the array if admin4u is correct.
jlapointe
12 Posts
0
August 25th, 2015 13:00
Slip streaming driver got me to recovery console, much appreciate Flash.
Is chkdsk /r /fixboot conservative enough or only option, I have read that if array is further degraded within online disks, a chkdsk could further damage data. Is it possible to start OMSA at this point?
Is it possible to back up C: or D: partitions in this state?
Thanks again.