HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- RHEL 4 on CL380 with CR3500 disk array.
Operating System - Linux
1831296
Members
3568
Online
110022
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
Forums
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
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
10-26-2005 10:51 AM
10-26-2005 10:51 AM
RHEL 4 on CL380 with CR3500 disk array.
As soon as I bring up the second node, I start
getting scsi reset errors in dmesg, and the shared drives are no longer accessible. Here
are the details:
Both servers are identical, except for the
fact that /etc/modprobe.conf has "hostid:6"
for sym53c8xx on the bottom node, matching
the firmware SCSI ID. BTW, I changed the SCSI
ID to 6 for both the ports (local as well as shared) in the BIOS for the bottom node.
The local drives show up under /dev/ida/c0..
and the shared drives (two of them) as /dev/sda
and /dev/sdb.
I have upgraded the firmware on both the CR3500 and the nodes.
Here's the output of /var/log/messages as soon
as I run a "modprobe -v sym53c8xx". It appears that despite my option of "hostid:6" to sym53c8xx, it is still using a SCSI ID of 7:
Oct 26 15:51:33 southdakota kernel: ACPI: PCI interrupt 0000:03:04.0[A] -> GSI 27 (level, low) -> IRQ 209
Oct 26 15:51:33 southdakota kernel: sym0: <896> rev 0x7 at pci 0000:03:04.0 irq 209
Oct 26 15:51:33 southdakota kernel: sym0: using 64 bit DMA addressing
Oct 26 15:51:33 southdakota kernel: sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
Oct 26 15:51:33 southdakota kernel: sym0: SCSI BUS has been reset.
Oct 26 15:51:33 southdakota kernel: scsi4 : sym-2.1.18j
Oct 26 15:51:36 southdakota kernel: scsi: unknown device type 12
Oct 26 15:51:36 southdakota kernel: Vendor: Compaq Model: CR3500 Rev: x2r-
Oct 26 15:51:36 southdakota kernel: Type: RAID ANSI SCSI revision: 02
Oct 26 15:51:36 southdakota kernel: target4:0:2: Beginning Domain Validation
Oct 26 15:51:36 southdakota kernel: sym0:2: wide asynchronous.
Oct 26 15:51:36 southdakota kernel: sym0:2: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 15)
Oct 26 15:51:36 southdakota kernel: target4:0:2: Domain Validation skipping write tests
Oct 26 15:51:36 southdakota kernel: target4:0:2: Ending Domain Validation
Oct 26 15:51:36 southdakota kernel: Vendor: Compaq Model: CR3500 Rev: x2r-
Oct 26 15:51:36 southdakota kernel: Type: Direct-Access ANSI SCSI revision: 02
Oct 26 15:51:36 southdakota kernel: SCSI device sda: 17762304 512-byte hdwr sectors (9094 MB)
Oct 26 15:51:36 southdakota kernel: SCSI device sda: drive cache: write through
Oct 26 15:51:36 southdakota kernel: sda:
Oct 26 15:51:36 southdakota kernel: Attached scsi disk sda at scsi4, channel 0, id 2, lun 1
Oct 26 15:51:36 southdakota kernel: scsi: unknown device type 12
Oct 26 15:51:36 southdakota scsi.agent[3332]: disk at /devices/pci0000:03/0000:03:04.0/host4/target4:0:2/4:0:2:1
Oct 26 15:51:37 southdakota kernel: Vendor: Compaq Model: CR3500 Rev: x2r-
Oct 26 15:51:37 southdakota kernel: Type: RAID ANSI SCSI revision: 02
Oct 26 15:51:37 southdakota kernel: sym0:3:0: tagged command queuing enabled, command queue depth 16.
Oct 26 15:51:37 southdakota kernel: target4:0:3: Beginning Domain Validation
Oct 26 15:51:37 southdakota kernel: sym0:3: wide asynchronous.
Oct 26 15:51:37 southdakota kernel: sym0:3: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 15)
Oct 26 15:51:37 southdakota kernel: target4:0:3: Domain Validation skipping write tests
Oct 26 15:51:37 southdakota kernel: target4:0:3: Ending Domain Validation
Oct 26 15:51:40 southdakota kernel: ACPI: PCI interrupt 0000:03:04.1[B] -> GSI 26 (level, low) -> IRQ 217
Oct 26 15:51:40 southdakota kernel: sym1: <896> rev 0x7 at pci 0000:03:04.1 irq 217
Oct 26 15:51:40 southdakota kernel: sym1: using 64 bit DMA addressing
Oct 26 15:51:40 southdakota kernel: sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking
Oct 26 15:51:40 southdakota kernel: sym1: SCSI BUS has been reset.
Oct 26 15:51:40 southdakota kernel: scsi5 : sym-2.1.18j
Appreciate if anyone can throw some light on this.
Surya.
getting scsi reset errors in dmesg, and the shared drives are no longer accessible. Here
are the details:
Both servers are identical, except for the
fact that /etc/modprobe.conf has "hostid:6"
for sym53c8xx on the bottom node, matching
the firmware SCSI ID. BTW, I changed the SCSI
ID to 6 for both the ports (local as well as shared) in the BIOS for the bottom node.
The local drives show up under /dev/ida/c0..
and the shared drives (two of them) as /dev/sda
and /dev/sdb.
I have upgraded the firmware on both the CR3500 and the nodes.
Here's the output of /var/log/messages as soon
as I run a "modprobe -v sym53c8xx". It appears that despite my option of "hostid:6" to sym53c8xx, it is still using a SCSI ID of 7:
Oct 26 15:51:33 southdakota kernel: ACPI: PCI interrupt 0000:03:04.0[A] -> GSI 27 (level, low) -> IRQ 209
Oct 26 15:51:33 southdakota kernel: sym0: <896> rev 0x7 at pci 0000:03:04.0 irq 209
Oct 26 15:51:33 southdakota kernel: sym0: using 64 bit DMA addressing
Oct 26 15:51:33 southdakota kernel: sym0: No NVRAM, ID 7, Fast-40, LVD, parity checking
Oct 26 15:51:33 southdakota kernel: sym0: SCSI BUS has been reset.
Oct 26 15:51:33 southdakota kernel: scsi4 : sym-2.1.18j
Oct 26 15:51:36 southdakota kernel: scsi: unknown device type 12
Oct 26 15:51:36 southdakota kernel: Vendor: Compaq Model: CR3500 Rev: x2r-
Oct 26 15:51:36 southdakota kernel: Type: RAID ANSI SCSI revision: 02
Oct 26 15:51:36 southdakota kernel: target4:0:2: Beginning Domain Validation
Oct 26 15:51:36 southdakota kernel: sym0:2: wide asynchronous.
Oct 26 15:51:36 southdakota kernel: sym0:2: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 15)
Oct 26 15:51:36 southdakota kernel: target4:0:2: Domain Validation skipping write tests
Oct 26 15:51:36 southdakota kernel: target4:0:2: Ending Domain Validation
Oct 26 15:51:36 southdakota kernel: Vendor: Compaq Model: CR3500 Rev: x2r-
Oct 26 15:51:36 southdakota kernel: Type: Direct-Access ANSI SCSI revision: 02
Oct 26 15:51:36 southdakota kernel: SCSI device sda: 17762304 512-byte hdwr sectors (9094 MB)
Oct 26 15:51:36 southdakota kernel: SCSI device sda: drive cache: write through
Oct 26 15:51:36 southdakota kernel: sda:
Oct 26 15:51:36 southdakota kernel: Attached scsi disk sda at scsi4, channel 0, id 2, lun 1
Oct 26 15:51:36 southdakota kernel: scsi: unknown device type 12
Oct 26 15:51:36 southdakota scsi.agent[3332]: disk at /devices/pci0000:03/0000:03:04.0/host4/target4:0:2/4:0:2:1
Oct 26 15:51:37 southdakota kernel: Vendor: Compaq Model: CR3500 Rev: x2r-
Oct 26 15:51:37 southdakota kernel: Type: RAID ANSI SCSI revision: 02
Oct 26 15:51:37 southdakota kernel: sym0:3:0: tagged command queuing enabled, command queue depth 16.
Oct 26 15:51:37 southdakota kernel: target4:0:3: Beginning Domain Validation
Oct 26 15:51:37 southdakota kernel: sym0:3: wide asynchronous.
Oct 26 15:51:37 southdakota kernel: sym0:3: FAST-20 WIDE SCSI 40.0 MB/s ST (50.0 ns, offset 15)
Oct 26 15:51:37 southdakota kernel: target4:0:3: Domain Validation skipping write tests
Oct 26 15:51:37 southdakota kernel: target4:0:3: Ending Domain Validation
Oct 26 15:51:40 southdakota kernel: ACPI: PCI interrupt 0000:03:04.1[B] -> GSI 26 (level, low) -> IRQ 217
Oct 26 15:51:40 southdakota kernel: sym1: <896> rev 0x7 at pci 0000:03:04.1 irq 217
Oct 26 15:51:40 southdakota kernel: sym1: using 64 bit DMA addressing
Oct 26 15:51:40 southdakota kernel: sym1: No NVRAM, ID 7, Fast-40, LVD, parity checking
Oct 26 15:51:40 southdakota kernel: sym1: SCSI BUS has been reset.
Oct 26 15:51:40 southdakota kernel: scsi5 : sym-2.1.18j
Appreciate if anyone can throw some light on this.
Surya.
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.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP