HPE GreenLake Administration
- Community Home
- >
- Storage
- >
- Legacy
- >
- Disk
- >
- add Jamacia disk to the enclosure
Disk
1832645
Members
2696
Online
110043
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
05-15-2006 03:36 AM
05-15-2006 03:36 AM
add Jamacia disk to the enclosure
Good morning. I am experiencing problems when I try to add 2 drives to a jamaica enclosure.
There are 2 slots empty and they are the bottom slots.
When I added the first 4.3GB drive it reconize the dirve with no problems and I am able to see it with ioscan.
When I add the second 4.3GB drive I get a lot SCSI resets and the other drives in the enclosure also report vgsync errors. Dow any one knwos about any limitation on this enclosures or why I am not able to add one more drive in the last available slot.
Bellow is a example of the errors received.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Reset detected -- lbolt: 491732948, bus: 1
May 15 11:17:18 mcccrsd0 vmunix: LVM: Path (device 0x1f01d000) to PV 11 in VG 1 Failed!
May 15 11:17:18 mcccrsd0 vmunix: LVM: Path (device 0x1f01e000) to PV 12 in VG 1 Failed!
May 15 11:17:18 mcccrsd0 vmunix: LVM: Path (device 0x1f01c000) to PV 10 in VG 1 Failed!
May 15 11:17:18 mcccrsd0 vmunix:
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Read error -- dev: b 31 0x013000, errno: 126, resid: 2048,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 8, sectno: 16, offset: 8192, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: LVM: vg[0]: pvnum=1 (dev_t=0x1f013000) is POWERFAILED
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 8192,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 5432, sectno: 10864, offset: 5562368, bcount: 8192.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 1024,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3211477, sectno: 6422954, offset: -1006414848, bcount: 1024.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 4096,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3242008, sectno: 6484016, offset: -975151104, bcount: 4096.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 3072,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3235413, sectno: 6470826, offset: -981904384, bcount: 3072.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 2048,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3217944, sectno: 6435888, offset: -999792640, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3211806, sectno: 6423612, offset: -1006077952, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3211778, sectno: 6423556, offset: -1006106624, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3211760, sectno: 6423520, offset: -1006125056, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Write error -- dev: b 31 0x013000, errno: 126, resid: 1024,
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 2048,
May 15 11:17:19 mcccrsd0 above message repeats 3 times
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3211664, sectno: 6423328, offset: -1006223360, bcount: 1024.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 2048,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3211492, sectno: 6422984, offset: -1006399488, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3179334, sectno: 6358668, offset: -1039329280, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3179352, sectno: 6358704, offset: -1039310848, bcount: 2048.
Any help is appreciated.
Thank you
There are 2 slots empty and they are the bottom slots.
When I added the first 4.3GB drive it reconize the dirve with no problems and I am able to see it with ioscan.
When I add the second 4.3GB drive I get a lot SCSI resets and the other drives in the enclosure also report vgsync errors. Dow any one knwos about any limitation on this enclosures or why I am not able to add one more drive in the last available slot.
Bellow is a example of the errors received.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Reset detected -- lbolt: 491732948, bus: 1
May 15 11:17:18 mcccrsd0 vmunix: LVM: Path (device 0x1f01d000) to PV 11 in VG 1 Failed!
May 15 11:17:18 mcccrsd0 vmunix: LVM: Path (device 0x1f01e000) to PV 12 in VG 1 Failed!
May 15 11:17:18 mcccrsd0 vmunix: LVM: Path (device 0x1f01c000) to PV 10 in VG 1 Failed!
May 15 11:17:18 mcccrsd0 vmunix:
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Read error -- dev: b 31 0x013000, errno: 126, resid: 2048,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 8, sectno: 16, offset: 8192, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: LVM: vg[0]: pvnum=1 (dev_t=0x1f013000) is POWERFAILED
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 8192,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 5432, sectno: 10864, offset: 5562368, bcount: 8192.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 1024,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3211477, sectno: 6422954, offset: -1006414848, bcount: 1024.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 4096,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3242008, sectno: 6484016, offset: -975151104, bcount: 4096.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 3072,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3235413, sectno: 6470826, offset: -981904384, bcount: 3072.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 2048,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3217944, sectno: 6435888, offset: -999792640, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3211806, sectno: 6423612, offset: -1006077952, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3211778, sectno: 6423556, offset: -1006106624, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3211760, sectno: 6423520, offset: -1006125056, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Write error -- dev: b 31 0x013000, errno: 126, resid: 1024,
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 2048,
May 15 11:17:19 mcccrsd0 above message repeats 3 times
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3211664, sectno: 6423328, offset: -1006223360, bcount: 1024.
May 15 11:17:18 mcccrsd0 vmunix: SCSI: Async write error -- dev: b 31 0x013000, errno: 126, resid: 2048,
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3211492, sectno: 6422984, offset: -1006399488, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3179334, sectno: 6358668, offset: -1039329280, bcount: 2048.
May 15 11:17:18 mcccrsd0 vmunix: blkno: 3179352, sectno: 6358704, offset: -1039310848, bcount: 2048.
Any help is appreciated.
Thank you
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2006 09:33 AM
05-15-2006 09:33 AM
Re: add Jamacia disk to the enclosure
Is there a chance the second added disk is faulty? this would be my first guess.
We have some Jamaicas still in use and fully populated.
I would suggest You at first remove this disk and try to get application downtime, and then try if the same behaviour shows in the other disk slot and vice versa.
reasons might be:
(if I remember correctly one can manually assign scsi ID's at the rear of the HASS)
- a used scsi id is assigned twice, i.e. using ID 7 already used by the scsi hba
- disk module broken
- backplane broken
I'll ask a workmate of mine about this tomorrow, he has a lot more experience with these enclosures.
We have some Jamaicas still in use and fully populated.
I would suggest You at first remove this disk and try to get application downtime, and then try if the same behaviour shows in the other disk slot and vice versa.
reasons might be:
(if I remember correctly one can manually assign scsi ID's at the rear of the HASS)
- a used scsi id is assigned twice, i.e. using ID 7 already used by the scsi hba
- disk module broken
- backplane broken
I'll ask a workmate of mine about this tomorrow, he has a lot more experience with these enclosures.
yesterday I stood at the edge. Today I'm one step ahead.
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