- Community Home
- >
- Servers and Operating Systems
- >
- Integrity Servers
- >
- disk problem at rx2620 integrity server
Integrity Servers
1753774
Members
6477
Online
108799
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2007 11:03 AM
тАО08-07-2007 11:03 AM
disk problem at rx2620 integrity server
HELLO,
I installed this night on a rx2620 integrity server with openvms 8.3-0 and
with following firmware version :
MP FW : E.03.30
BMC FW: 04:03
SYSTEM FW : 04:21
EFI FW : 5.48
a new 300 GB 15k RPM ultra320 scsi low profile hotplug disk partnumber AD261A (internal supported storage device of rx2620 integrity server)
situation before :
NVK$ sho dev d
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA3000: Mounted 0 I64_V82 30074944 834 1
$3$DKA0: (NVK) ShadowSetMember 0 (member of DSA3000:)
$3$DKA100: (NVK) Mounted 0 DATA 13970480 147
$3$DQA0: (NVK) Online 0
$3$DQA1: (NVK) Offline 2
NVK$
Situation after
NVK$ sho dev d
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA3000: Mounted 0 I64_V82 30074944 834 1
$3$DKA0: (NVK) ShadowSetMember 0 (member of DSA3000:)
$3$DKA100: (NVK) Mounted 0 DATA 13970480 1471 1
$3$DKB200: (NVK) Online 15
$3$DKB201: (NVK) Online 26
$3$DKB202: (NVK) Online 13
$3$DKB203: (NVK) Online 23
$3$DKB204: (NVK) Online 14
$3$DKB205: (NVK) Online 22
$3$DKB206: (NVK) Online 16
$3$DKB207: (NVK) Online 22
$3$DQA0: (NVK) Online 0
$3$DQA1: (NVK) Offline 2
NVK$
BAsically I have put fysically one scsi drive of 300 GB in bay 2 of the internal storage bays (upper storage bay)but then I got 8 devices which refer all to the same disk.
I can see that the new disk uses the other scsi channel than the ones in bay 0 and bay 1.
Did some have the same experience and more important how can I solve this. Is this a faulty disk and if so why do I get 8 devices which refer to that same new fysical drive
when I do an init I got the following result :
init $3$DKB200:
_Label: data1
%INIT-F-MEDOFL, medium is offline
NVK$
Please send feedback to mdhaene1@volvocars.com
Thank you in advance
Best regards,
Mario
I installed this night on a rx2620 integrity server with openvms 8.3-0 and
with following firmware version :
MP FW : E.03.30
BMC FW: 04:03
SYSTEM FW : 04:21
EFI FW : 5.48
a new 300 GB 15k RPM ultra320 scsi low profile hotplug disk partnumber AD261A (internal supported storage device of rx2620 integrity server)
situation before :
NVK$ sho dev d
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA3000: Mounted 0 I64_V82 30074944 834 1
$3$DKA0: (NVK) ShadowSetMember 0 (member of DSA3000:)
$3$DKA100: (NVK) Mounted 0 DATA 13970480 147
$3$DQA0: (NVK) Online 0
$3$DQA1: (NVK) Offline 2
NVK$
Situation after
NVK$ sho dev d
Device Device Error Volume Free Trans Mnt
Name Status Count Label Blocks Count Cnt
DSA3000: Mounted 0 I64_V82 30074944 834 1
$3$DKA0: (NVK) ShadowSetMember 0 (member of DSA3000:)
$3$DKA100: (NVK) Mounted 0 DATA 13970480 1471 1
$3$DKB200: (NVK) Online 15
$3$DKB201: (NVK) Online 26
$3$DKB202: (NVK) Online 13
$3$DKB203: (NVK) Online 23
$3$DKB204: (NVK) Online 14
$3$DKB205: (NVK) Online 22
$3$DKB206: (NVK) Online 16
$3$DKB207: (NVK) Online 22
$3$DQA0: (NVK) Online 0
$3$DQA1: (NVK) Offline 2
NVK$
BAsically I have put fysically one scsi drive of 300 GB in bay 2 of the internal storage bays (upper storage bay)but then I got 8 devices which refer all to the same disk.
I can see that the new disk uses the other scsi channel than the ones in bay 0 and bay 1.
Did some have the same experience and more important how can I solve this. Is this a faulty disk and if so why do I get 8 devices which refer to that same new fysical drive
when I do an init I got the following result :
init $3$DKB200:
_Label: data1
%INIT-F-MEDOFL, medium is offline
NVK$
Please send feedback to mdhaene1@volvocars.com
Thank you in advance
Best regards,
Mario
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-07-2007 04:24 PM
тАО08-07-2007 04:24 PM
Re: disk problem at rx2620 integrity server
the rx2620 actually has 3 slots for internal hard disk. the 3rd slot actually belongs to another scsi channel. perhaps you can try plugging the disk into the slot and see if the same behaviour happen. if it do not, then it could be possibly due to the first scsi channel for the first and second slots.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО08-09-2007 05:24 AM
тАО08-09-2007 05:24 AM
Re: disk problem at rx2620 integrity server
The top/third slot SCSI B-bus appears faulty, or the new disk in the DKB200 top/third slot is faulty, there's bus under or over termination, a SCSI unit number collision, bent pins, etc. This looks to be a hardware problem.
Regardless, I would load current ECOs for OpenVMS I64 V8.3 as there have been a number of SCSI-related patches and updates released over the past few months. Load the current FIBRE_SCSI kit.
I'd power-cycle the box, if that hasn't already been tried. I'd try swapping a different spare disk. And I'd look at anything else connected to the SCSI B-bus, as that bus can go external. And I'd see if the ECOs sort this out.
Stephen Hoffman
HoffmanLabs LLC
Regardless, I would load current ECOs for OpenVMS I64 V8.3 as there have been a number of SCSI-related patches and updates released over the past few months. Load the current FIBRE_SCSI kit.
I'd power-cycle the box, if that hasn't already been tried. I'd try swapping a different spare disk. And I'd look at anything else connected to the SCSI B-bus, as that bus can go external. And I'd see if the ECOs sort this out.
Stephen Hoffman
HoffmanLabs LLC
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP