donte10
Member
- Reaction score
- 1
- Location
- Milwaukee, WI
Let me tell you what I got. I have a fairly new client that began to have issues with their Symantec Backup Exec running backups all night long and into the late morning around 11am. This was not normal, they used to be finished before the staff returned to the office in the morning at 7am. In addition, the client would also get blue screens, but seemed to be caused when running Symantec backups. So the client decided to troubleshoot with a Symantec support tech without success (they remoted into the server).
I happened to drop in for a different workstation problem that was reported and thought I'd take a peak at the server. I noticed errors in the event viewer log like:
Under System Log:
error: the device\hardisk0\DR0, has a bad block.
warning: error detected harddisk1\DR2 during a paging operation.
Under Applications Log:
Source: Symantec "Job failed with error: corrupt data encountered"
Source: VSS "VSS Writer has rejected an event -- probably caused by faulty hardware.
Note: This server is using RAID 1 with 2x 500GB SATA drives (400GB used). Server is 4-5 years old running Server 2008. Keep in mind client has no good backup for about 1-month.
I think it's a bad hard drive.. so I ran 'Crystal Disk Info' and it turns out that Drive A is reporting 'CAUTION' with reallocated sectors and Drive B is reporting 'BAD' with reallocated sectors.
My plan was to rebuild one drive at a time starting with the worser of the two drives (crossing fingers that drive A would not be too bad to copy from). So I took out the Drive B and inserted a new enterprise SATA 1TB drive, hoping that it would rebuild and be ok. The LSI LOGIC RAID card said it was resynching/rebuilding the drive, so I left it run over night. I returned the next day to find that the Drive B is reporting 'failed' in the RAID controller firmware. (I tried again with a new drive and same thing). I believe the rebuild is not working because of the faulty Drive A.
Hopefully I explained this well...what do you think? One question is can I install a bigger drive into the raid to rebuild. It looks like it auto adjusted down to 500GB.
Also, what is the next step for me to get this system up and running with fresh drives? I was thinking cloning using another alternative software, but wasn't sure if that's my next step. How would I do this anyway?
I happened to drop in for a different workstation problem that was reported and thought I'd take a peak at the server. I noticed errors in the event viewer log like:
Under System Log:
error: the device\hardisk0\DR0, has a bad block.
warning: error detected harddisk1\DR2 during a paging operation.
Under Applications Log:
Source: Symantec "Job failed with error: corrupt data encountered"
Source: VSS "VSS Writer has rejected an event -- probably caused by faulty hardware.
Note: This server is using RAID 1 with 2x 500GB SATA drives (400GB used). Server is 4-5 years old running Server 2008. Keep in mind client has no good backup for about 1-month.
I think it's a bad hard drive.. so I ran 'Crystal Disk Info' and it turns out that Drive A is reporting 'CAUTION' with reallocated sectors and Drive B is reporting 'BAD' with reallocated sectors.
My plan was to rebuild one drive at a time starting with the worser of the two drives (crossing fingers that drive A would not be too bad to copy from). So I took out the Drive B and inserted a new enterprise SATA 1TB drive, hoping that it would rebuild and be ok. The LSI LOGIC RAID card said it was resynching/rebuilding the drive, so I left it run over night. I returned the next day to find that the Drive B is reporting 'failed' in the RAID controller firmware. (I tried again with a new drive and same thing). I believe the rebuild is not working because of the faulty Drive A.
Hopefully I explained this well...what do you think? One question is can I install a bigger drive into the raid to rebuild. It looks like it auto adjusted down to 500GB.
Also, what is the next step for me to get this system up and running with fresh drives? I was thinking cloning using another alternative software, but wasn't sure if that's my next step. How would I do this anyway?