[cisco-voip] MCS-7828-H3 Raid array
Ryan Ratliff
rratliff at cisco.com
Fri Aug 22 11:52:07 EDT 2008
Unfortunately no. 6.1.2.9901.28 means it will be in 6.1.3. The 7.0
versions are various builds of 7.x. Any time you see a .99xx it
means it is going into the next version.
-Ryan
On Aug 22, 2008, at 11:47 AM, Jason Aarons ((US)) wrote:
Ok found the problem as this is an exact match to our issue; We had
upgraded to 6.1.2-1000-13 at install, but that doesn’t match
6.1.2.9901.28. Is the fixed version a ES that TAC can provide?
http://tools.cisco.com/Support/BugToolKit/search/getBugDetails.do?
method=fetchBugDetails&bugId=CSCsm25875
Symptom:
Operations impacted after a single disk failure on a system with
redundant disks.
Conditions:
Single disk fail on system with redundant disks.
Workaround:
None. Use DRS to back up data, and restore the data after the failed
HD is replaced.
Product
Cisco Unified Communications Manager (CallManager)
1st Found-In
6.0(1)
6.1(1.1000.8)
Fixed-In
7.0(0.39700.87)
6.1(2.9901.28)
7.0(0.66666.1)
7.0(0.66666.2)
Related Bug Information Single drive failure causes server outage
Symptom: Single bad drive in RAID 1 configuration causes entire
system to fail. Conditions: CUCMBE 6.1.1a and MSC7828H3-K9-BE.
Workaround: In this instance there is no workaround. Server will no
longer boot.
From: cisco-voip-bounces at puck.nether.net [mailto:cisco-voip-
bounces at puck.nether.net] On Behalf Of Jason Aarons (US)
Sent: Friday, August 22, 2008 11:17 AM
To: cisco-voip at puck.nether.net
Subject: [cisco-voip] MCS-7828-H3 Raid array
Sorry story has changed from 7818-H3 to 7828-H3….I wish I had records
of what they bought…
How is the raid array in a 7828-H3 configured in both preloaded and
when installing media from disk? During media install? Is there
anyway to view a raid array ?
Customer bought a preloaded MCS-7828-H3 and a drive failed, now they
think the RAID array was “not setup properly”.
Since it was preloaded I didn’t think anything had to be done to
setup a RAID array.
Bug perhaps?
Are there instructions from TAC on how to properly handle a failed
drive scenario? Perhaps something wasn’t followed?
the Call Manager Server is down, and won’t boot. I’ve just tried
rebooting it again, and it gets part of the way through the reboot,
and falls over at this spot –
‘Checking Filesystems’
‘Couldn’t find matching Filesystems: LABEL=/partB’ [FAILED]
It currently sitting at a prompt saying –
‘Give root password for maintenance’:
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the intended
addressee, you are hereby notified that you have received this
communication in error and that any use or reproduction of this email
or its contents is strictly prohibited and may be unlawful. If you
have received this communication in error, please notify us
immediately by replying to this message and deleting it from your
computer. Thank you.
Disclaimer: This e-mail communication and any attachments may contain
confidential and privileged information and is for use by the
designated addressee(s) named above only. If you are not the intended
addressee, you are hereby notified that you have received this
communication in error and that any use or reproduction of this email
or its contents is strictly prohibited and may be unlawful. If you
have received this communication in error, please notify us
immediately by replying to this message and deleting it from your
computer. Thank you.
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20080822/45a6d0f0/attachment-0001.html>
More information about the cisco-voip
mailing list