- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- ProLiant Servers (ML,DL,SL)
- >
- DL585 running SuSe
ProLiant Servers (ML,DL,SL)
1756509
Members
2458
Online
108848
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
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
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
07-04-2007 08:51 AM
07-04-2007 08:51 AM
DL585 running SuSe
I have an interesting problem and I cannot seem to find an answer so I figured I would seek professional OS help! I have posed this question in the Openview forum and no one can help me so I thought I would try here.
The background is that a script in Openview is failing trying to discover the volume group configuration on this server. Part of this discovery is to retrieve the hardware path for the disks. I checked the script and it's looking for the hardware path in /proc/scsi/scsi but this file is empty. All our servers are pretty much the same and this file is empty on all of them so here are my questions.
WHY!?!
I checked and it is running a RAID controller and the hwinfo command returns:
root # hwinfo --disk
23: None 00.0: 10600 Disk
[Created at block.190]
Unique ID: Q1WQ.kjXhxzegEH5
SysFS ID: /block/cciss!c0d0
Hardware Class: disk
Model: "CCISS disk 0/0"
Device: "CCISS disk 0/0"
Device File: /dev/cciss/c0d0
Device Number: block 104:0-104:15
BIOS id: 0x80
Geometry (Logical): CHS 35139/255/32
Size: 286734240 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
and when I check /proc/driver/cciss/cciss0 I get:
root # more /proc/driver/cciss/cciss0
cciss0: HP Smart Array 6i Controller
Board ID: 0x40910e11
Firmware Version: 2.36
IRQ: 19
Logical drives: 1
Current Q depth: 0
Current # commands on controller: 0
Max Q depth since init: 5
Max # commands on controller since init: 384
Max SG entries since init: 31
Sequential access devices: 0
cciss/c0d0: 146.80GB RAID 1(1+0)
I realize that this is not something I will be able to fix on my own but I'm hoping that some SuSe expert can explain why /proc/scsi/scsi is empty and if it's supposed to be. We are running SuSe 9.x and 10.x versions.
The background is that a script in Openview is failing trying to discover the volume group configuration on this server. Part of this discovery is to retrieve the hardware path for the disks. I checked the script and it's looking for the hardware path in /proc/scsi/scsi but this file is empty. All our servers are pretty much the same and this file is empty on all of them so here are my questions.
WHY!?!
I checked and it is running a RAID controller and the hwinfo command returns:
root # hwinfo --disk
23: None 00.0: 10600 Disk
[Created at block.190]
Unique ID: Q1WQ.kjXhxzegEH5
SysFS ID: /block/cciss!c0d0
Hardware Class: disk
Model: "CCISS disk 0/0"
Device: "CCISS disk 0/0"
Device File: /dev/cciss/c0d0
Device Number: block 104:0-104:15
BIOS id: 0x80
Geometry (Logical): CHS 35139/255/32
Size: 286734240 sectors a 512 bytes
Config Status: cfg=yes, avail=yes, need=no, active=unknown
and when I check /proc/driver/cciss/cciss0 I get:
root # more /proc/driver/cciss/cciss0
cciss0: HP Smart Array 6i Controller
Board ID: 0x40910e11
Firmware Version: 2.36
IRQ: 19
Logical drives: 1
Current Q depth: 0
Current # commands on controller: 0
Max Q depth since init: 5
Max # commands on controller since init: 384
Max SG entries since init: 31
Sequential access devices: 0
cciss/c0d0: 146.80GB RAID 1(1+0)
I realize that this is not something I will be able to fix on my own but I'm hoping that some SuSe expert can explain why /proc/scsi/scsi is empty and if it's supposed to be. We are running SuSe 9.x and 10.x versions.
Conformity Destroys a mans initiative and independence. It supresses his powerful inner drive to do his own thing.
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