Hi All
I am getting the error "drive with volume sys is failing" about once a week now.
A reboot of the server sorts it out, and my WHS icon returns to green, I have run the repair, but it does not seem to have any effect ?
is there possible some sort of corruption that anyone is aware of that can cause this ?
thanks for any insight
Welcome to We Got Served Forums
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. If you already have an account, login here - otherwise create an account for free today!
Drive With Volume Sys Is Failing
Started by
jodyn
, Oct 07 2009 02:22 PM
#1
Posted 07 October 2009 - 02:22 PM
jodyn
-
- Members
-
- 1,277 posts
Advanced Member
- Gender:Male
- Location:UK
Back to top
#2
Posted 07 October 2009 - 05:50 PM
Ikon
-
- Members
-
- 8 posts
Newbie
Here's what I would do: shut down my WHS, remove the sys drive & attach as a secondary drive to another PC, then boot from my SpinRite CD & run it on level 2 to start. If that passes (whether clean or if it recovered sectors), run again on level 4. If it passes level 4, put it back in service. If it doesn't pass, try to clone the failing drive to a new one.Hi All
I am getting the error "drive with volume sys is failing" about once a week now.
A reboot of the server sorts it out, and my WHS icon returns to green, I have run the repair, but it does not seem to have any effect ?
is there possible some sort of corruption that anyone is aware of that can cause this ?
thanks for any insight
If you don't own SpinRite, I recommend you buy a copy: http://grc.com/spinrite.
#3
Posted 10 October 2009 - 08:33 AM
Drashna Jaelre (WGS)
Contributor
-
- Lead Moderator
-
- 12,462 posts
Tinkerer
- Gender:Male
- Location:San Diego, CA, USA
- Interests:Computers, Home Server (obviously), math, science, good books, friends
Contributor
Did you happen to resize the system partition after installation? If so, you may want to consider a reistallation (it will keep the same size partition for sys, but should "fix" that issue.
#4
Posted 30 October 2009 - 08:48 PM
Niel
-
- Members
-
- 1 posts
Newbie
A clue:
Every comment regarding this error on every forum I've see is about an ST350063 OAS drive comming up with this error so maybe it's an problem related to this model drive only.
Every comment regarding this error on every forum I've see is about an ST350063 OAS drive comming up with this error so maybe it's an problem related to this model drive only.
#5
Posted 31 October 2009 - 07:33 AM
jodyn
-
- Members
-
- 1,277 posts
Advanced Member
- Gender:Male
- Location:UK
A clue:
Every comment regarding this error on every forum I've see is about an ST350063 OAS drive comming up with this error so maybe it's an problem related to this model drive only.
Hi
My OS Drive is a WD 1TB
My second drive is however the ST350062
hmmmm.....
i get the error about once a week.
#6
Posted 31 October 2009 - 07:36 AM
jodyn
-
- Members
-
- 1,277 posts
Advanced Member
- Gender:Male
- Location:UK
Did you happen to resize the system partition after installation? If so, you may want to consider a reistallation (it will keep the same size partition for sys, but should "fix" that issue.
Still the original 20GB partition.
I want to re-install, but can't be bothered with re-installing exchange.....
#7
Posted 05 November 2009 - 09:20 PM
ezzye
-
- Members
-
- 25 posts
Member
I just got my first yellow warning on the system drive. Now what is the general consensus for this?
Should I choose the repair option in the console?
My drive is one of the prior seagate problem drives I think--ST3100034OAS
So If I want to replace the drive what is the simplest and safest course of action?
Any advice is appreciated. Man I wish there was a system backup option.
Should I choose the repair option in the console?
My drive is one of the prior seagate problem drives I think--ST3100034OAS
So If I want to replace the drive what is the simplest and safest course of action?
Any advice is appreciated. Man I wish there was a system backup option.
#8
Posted 06 November 2009 - 08:01 AM
jodyn
-
- Members
-
- 1,277 posts
Advanced Member
- Gender:Male
- Location:UK
#9
Posted 06 November 2009 - 09:52 AM
Drashna Jaelre (WGS)
Contributor
-
- Lead Moderator
-
- 12,462 posts
Tinkerer
- Gender:Male
- Location:San Diego, CA, USA
- Interests:Computers, Home Server (obviously), math, science, good books, friends
Contributor
Unfortunately, this is one of WHS's weak points... I've heard a number of reports that basically, if you switch out the system drive with a blank drive, it will let you do a "reinstall" and rebuild the file structure for you.
#10
Posted 06 November 2009 - 08:14 PM
ezzye
-
- Members
-
- 25 posts
Member
Unfortunately, this is one of WHS's weak points... I've heard a number of reports that basically, if you switch out the system drive with a blank drive, it will let you do a "reinstall" and rebuild the file structure for you.
So I could leave all my data drives still plugged in? Switch out the system drive with a blank drive and select reinstall option with the whs disc, I would be good to go? Would I still need to do the migrate data thing in the wiki?
I know you guys probably get tired of going over the same stuff all the time, but just want to be sure before I lose 5+ TB of movies.
Thanks
#11
Posted 30 December 2009 - 10:44 AM
spile
-
- Members
-
- 462 posts
Advanced Member
- Gender:Male
- Location:Worcestershire, UK
To bring this thread back in line with the OP, does anyone know a way to fix the Volume Sys is failing issue?
There are lots of people with this problem and yet there doesn't seem a definitive cure or fix.
The HD on my HP Proliant ML115 G5 has been coming up with this error every two weeks or so for a year or more and there is nothing wrong with it.
Same issue...
http://social.micros...4-c37ed01718cf/
http://forums.anandt...d.php?t=2024365
http://forum.wegotse...sys-is-failing/
There are lots of people with this problem and yet there doesn't seem a definitive cure or fix.
The HD on my HP Proliant ML115 G5 has been coming up with this error every two weeks or so for a year or more and there is nothing wrong with it.
Same issue...
http://social.micros...4-c37ed01718cf/
http://forums.anandt...d.php?t=2024365
http://forum.wegotse...sys-is-failing/
#12
Posted 30 December 2009 - 10:58 AM
spile
-
- Members
-
- 462 posts
Advanced Member
- Gender:Male
- Location:Worcestershire, UK
Interesting - I've just done an RDP into WHS and run the Disk management snap in - all the drives show "Healthy", so WHS doesn't appear to have a problem but the connector on my desktop does???
http://forum.wegotse...=images&img=258
http://forum.wegotse...=images&img=259
http://forum.wegotse...=images&img=258
http://forum.wegotse...=images&img=259
#13
Posted 30 December 2009 - 11:07 AM
Dave Marchant (WGS)
-
- Moderators
-
- 3,665 posts
Advanced Member
- Gender:Male
- Location:High Wycombe, UK
I am now getting this too. I have a bit more I can add to the information so far.
I have checked my Server's Event Logs and there is no error at all reported there. My Twitter add-in gave me the time the alert was issued and it coincides with the Chkdsk that runs just after midnight. A reboot clears the alert (I can't find any other way) and I have now had it about once per week for the last 3 or 4 weeks.
I am not going to do anything drastic at present as I think this is a reporting bug more than anything (based on the posts here).
I have checked my Server's Event Logs and there is no error at all reported there. My Twitter add-in gave me the time the alert was issued and it coincides with the Chkdsk that runs just after midnight. A reboot clears the alert (I can't find any other way) and I have now had it about once per week for the last 3 or 4 weeks.
I am not going to do anything drastic at present as I think this is a reporting bug more than anything (based on the posts here).
#14
Posted 30 December 2009 - 12:02 PM
spile
-
- Members
-
- 462 posts
Advanced Member
- Gender:Male
- Location:Worcestershire, UK
I wonder if it could be related to WHS going into hibernation via LightsOut?
Very annoying to have to go into the console and reboot the server - I want my WHS to sit quietly and do its job!
Very annoying to have to go into the console and reboot the server - I want my WHS to sit quietly and do its job!
#15
Posted 30 December 2009 - 12:02 PM
niw_uk1964
-
- Members
-
- 363 posts
Advanced Member
- Gender:Male
- Location:United Kingdom
-
Interests:Motorcycles
Racing motorcycles as in racing them
Computers - Linux
I've long been of the opinion that this is a bug - it just started happening one day out of the blue. I suspect after an update. I've never seen a problem with my data...I get this problem affecting 3 of my drives (out of 8). A reboot clears the problem for a week or two.
#16
Posted 30 December 2009 - 12:02 PM
Dave Marchant (WGS)
-
- Moderators
-
- 3,665 posts
Advanced Member
- Gender:Male
- Location:High Wycombe, UK
My WHS is on permanently so I don't think so.I wonder if it could be related to WHS going into hibernation via LightsOut?
Very annoying to have to go into the console and reboot the server - I want my WHS to sit quietly and do its job!
#17
Posted 30 December 2009 - 01:38 PM
jodyn
-
- Members
-
- 1,277 posts
Advanced Member
- Gender:Male
- Location:UK
mine is also on 24/7 and i dont use lightsout
as with everyone else reporting this, a reboot fixes it for a week or a bit longer
as with everyone else reporting this, a reboot fixes it for a week or a bit longer
#18
Posted 30 December 2009 - 03:00 PM
spile
-
- Members
-
- 462 posts
Advanced Member
- Gender:Male
- Location:Worcestershire, UK
A post on one of the other threads mentioned this might be a UPS issue. Clutching at straws I know but anyone tried disconnecting their UPS to see if the errors go away?
Just tried a server reboot without a repair and it has stopped reporting an error!
Just tried a server reboot without a repair and it has stopped reporting an error!
#19
Posted 30 December 2009 - 03:09 PM
jodyn
-
- Members
-
- 1,277 posts
Advanced Member
- Gender:Male
- Location:UK
#20
Posted 01 January 2010 - 11:25 PM
Drashna Jaelre (WGS)
Contributor
-
- Lead Moderator
-
- 12,462 posts
Tinkerer
- Gender:Male
- Location:San Diego, CA, USA
- Interests:Computers, Home Server (obviously), math, science, good books, friends
Contributor
My guess is that it's more to do with the idle spin down power saving setting than anything else. Not sure, but somebody should report a bug aboing this, or check to see if there is one already (and post a link). A similar discussion appeared with DE performance issues, and I got an immediate response, so PLEASE, post a bug in connect.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users
Community Forum Software by IP.Board
Licensed to: Terry Walsh, We Got Served.
