- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- DL380G4 & SLES9 Install - failed on cciss/c0d0p1
Operating System - Linux
1753518
Members
4890
Online
108795
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
02-08-2005 04:50 PM
02-08-2005 04:50 PM
DL380G4 & SLES9 Install - failed on cciss/c0d0p1
Hi, first time on this forum.
Have just built a new DL380 G4 server with SLES9 and got an error not seen with the same build on a G3 model. This is a primary oracle system and
have EXT3 with custom partitioning.
extract-------------error
>JBD: barrier-based sync failed on cciss/c0d0p1 - disabling barriers
<6>kjournald starting. Commit interval 5 seconds
<6>EXT3 FS on cciss/c0d0p7, internal journal
<6>EXT3-fs: mounted filesystem with ordered data mode.
[...] couple of other smaller error on mtrr.
-----i opened a ticket with SUSE and got this--
JBD is the module responsible of the journaling here of the ext3 filesystem.
The above mentioned barrier is a transaction barrier. Such a mechanism has been introduced to ensure data consistency after power loss.
A synchronisation with this mechanism is first tried and then if a problem occurs, it reverts to the old mechanism (without barrier). As there is no further error, it worked fine.
-------------------------end
would really like to eliminate this incase it presents as a problem latter.
the G4 & SLES9 are a very green mix & its only been the last week or so that the certification martix of both HP & novell now even reflect that this mix is fully supported. I have applied the PSP7.11 pack which is for SLES8/9 and no difference.
A perminent fix really needs to be worked out between HP & SUSE, so it installs just like on the G3 or as SLES8 did.
attached - any HP SUSE linux techs offer a solution?
rgs Ewan Layton
Have just built a new DL380 G4 server with SLES9 and got an error not seen with the same build on a G3 model. This is a primary oracle system and
have EXT3 with custom partitioning.
extract-------------error
>JBD: barrier-based sync failed on cciss/c0d0p1 - disabling barriers
<6>kjournald starting. Commit interval 5 seconds
<6>EXT3 FS on cciss/c0d0p7, internal journal
<6>EXT3-fs: mounted filesystem with ordered data mode.
[...] couple of other smaller error on mtrr.
-----i opened a ticket with SUSE and got this--
JBD is the module responsible of the journaling here of the ext3 filesystem.
The above mentioned barrier is a transaction barrier. Such a mechanism has been introduced to ensure data consistency after power loss.
A synchronisation with this mechanism is first tried and then if a problem occurs, it reverts to the old mechanism (without barrier). As there is no further error, it worked fine.
-------------------------end
would really like to eliminate this incase it presents as a problem latter.
the G4 & SLES9 are a very green mix & its only been the last week or so that the certification martix of both HP & novell now even reflect that this mix is fully supported. I have applied the PSP7.11 pack which is for SLES8/9 and no difference.
A perminent fix really needs to be worked out between HP & SUSE, so it installs just like on the G3 or as SLES8 did.
rgs Ewan Layton
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
02-09-2005 08:11 PM
02-09-2005 08:11 PM
Re: DL380G4 & SLES9 Install - failed on cciss/c0d0p1
It seem the answer is dont worry this is fine.
At the lecture of your attachement I notice the following, dont know if is a "real problem", but perhaps you missed this ?
Did you try booting with nobiospnp!
<3>PnPBIOS: Warning! Your PnP BIOS caused a fatal error. Attempting to continue
<3>PnPBIOS: You may need to reboot with the "nobiospnp" option to operate stably
<3>PnPBIOS: Check with your vendor for an updated BIOS
<3>PnPBIOS: dev_node_info: unexpected status 0x28
<3>PnPBIOS: Unable to get node info. Aborting.
disclaimer in am not a HP SUSE linux tech, just your ordinary (poor,probably under avarage) system manager.
Jean-Pierre
At the lecture of your attachement I notice the following, dont know if is a "real problem", but perhaps you missed this ?
Did you try booting with nobiospnp!
<3>PnPBIOS: Warning! Your PnP BIOS caused a fatal error. Attempting to continue
<3>PnPBIOS: You may need to reboot with the "nobiospnp" option to operate stably
<3>PnPBIOS: Check with your vendor for an updated BIOS
<3>PnPBIOS: dev_node_info: unexpected status 0x28
<3>PnPBIOS: Unable to get node info. Aborting.
disclaimer in am not a HP SUSE linux tech, just your ordinary (poor,probably under avarage) system manager.
Jean-Pierre
Smile I will feel the difference
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