- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Difficulty with fdisk and cciss Raid 5
Operating System - Linux
1753821
Members
9278
Online
108805
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
Go to solution
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
тАО09-18-2009 08:30 AM
тАО09-18-2009 08:30 AM
I have an HP Proliant DL180G5 with SuSE Linux 10 SP2 installed.
I have a 5TB Raid array composed of disks that are internal to the machine.
lorapp01:~ # cat /proc/driver/cciss/cciss0
cciss0: HP Smart Array P400 Controller
Board ID: 0x3234103c
Firmware Version: 5.22
IRQ: 98
Logical drives: 1
Sector size: 2048
Current Q depth: 0
Current # commands on controller: 0
Max Q depth since init: 5
Max # commands on controller since init: 161
Max SG entries since init: 31
Sequential access devices: 0
cciss/c0d0: 5000.85GB RAID 5
Here is the partition listing so far from fdisk:
lorapp01:~ # fdisk /dev/cciss/c0d0
The number of cylinders for this disk is set to 607986.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/cciss/c0d0: 5000.8 GB, 5000855773184 bytes
255 heads, 63 sectors/track, 607986 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 39163 314576766 83 Linux
/dev/cciss/c0d0p2 39164 52218 104864287+ 82 Linux swap / Solaris
/dev/cciss/c0d0p3 52219 319567 2147480842+ 8e Linux LVM
I want to add a fourth partition with 1.9 TB but when I try to add it then fdisk wants to use the same starting cylinder 52219 as the previous third partition:
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Selected partition 4
First cylinder (52219-607986, default 52219):
I choose 319568 but after adding the 4th partition and printing the partition table it shows the starting cylinder 52218, which is 1 cylinder less than the previous partition.
First cylinder (52219-607986, default 52219): 319568
Last cylinder or +size or +sizeM or +sizeK (319568-607986, default 607986):
Using default value 607986
Command (m for help): p
Disk /dev/cciss/c0d0: 5000.8 GB, 5000855773184 bytes
255 heads, 63 sectors/track, 607986 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 39163 314576766 83 Linux
/dev/cciss/c0d0p2 39164 52218 104864287+ 82 Linux swap / Solaris
/dev/cciss/c0d0p3 52219 319567 2147480842+ 8e Linux LVM
/dev/cciss/c0d0p4 52218 73288 169241969+ 83 Linux
Partition table entries are not in disk order
Can anyone tell me what I'm doing wrong?
Thanks,
Ed
I have a 5TB Raid array composed of disks that are internal to the machine.
lorapp01:~ # cat /proc/driver/cciss/cciss0
cciss0: HP Smart Array P400 Controller
Board ID: 0x3234103c
Firmware Version: 5.22
IRQ: 98
Logical drives: 1
Sector size: 2048
Current Q depth: 0
Current # commands on controller: 0
Max Q depth since init: 5
Max # commands on controller since init: 161
Max SG entries since init: 31
Sequential access devices: 0
cciss/c0d0: 5000.85GB RAID 5
Here is the partition listing so far from fdisk:
lorapp01:~ # fdisk /dev/cciss/c0d0
The number of cylinders for this disk is set to 607986.
There is nothing wrong with that, but this is larger than 1024,
and could in certain setups cause problems with:
1) software that runs at boot time (e.g., old versions of LILO)
2) booting and partitioning software from other OSs
(e.g., DOS FDISK, OS/2 FDISK)
Command (m for help): p
Disk /dev/cciss/c0d0: 5000.8 GB, 5000855773184 bytes
255 heads, 63 sectors/track, 607986 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 39163 314576766 83 Linux
/dev/cciss/c0d0p2 39164 52218 104864287+ 82 Linux swap / Solaris
/dev/cciss/c0d0p3 52219 319567 2147480842+ 8e Linux LVM
I want to add a fourth partition with 1.9 TB but when I try to add it then fdisk wants to use the same starting cylinder 52219 as the previous third partition:
Command (m for help): n
Command action
e extended
p primary partition (1-4)
p
Selected partition 4
First cylinder (52219-607986, default 52219):
I choose 319568 but after adding the 4th partition and printing the partition table it shows the starting cylinder 52218, which is 1 cylinder less than the previous partition.
First cylinder (52219-607986, default 52219): 319568
Last cylinder or +size or +sizeM or +sizeK (319568-607986, default 607986):
Using default value 607986
Command (m for help): p
Disk /dev/cciss/c0d0: 5000.8 GB, 5000855773184 bytes
255 heads, 63 sectors/track, 607986 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Device Boot Start End Blocks Id System
/dev/cciss/c0d0p1 * 1 39163 314576766 83 Linux
/dev/cciss/c0d0p2 39164 52218 104864287+ 82 Linux swap / Solaris
/dev/cciss/c0d0p3 52219 319567 2147480842+ 8e Linux LVM
/dev/cciss/c0d0p4 52218 73288 169241969+ 83 Linux
Partition table entries are not in disk order
Can anyone tell me what I'm doing wrong?
Thanks,
Ed
No one is ever really going to be free until nerd persecution ends.
Solved! Go to Solution.
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-18-2009 01:22 PM
тАО09-18-2009 01:22 PM
Solution
Maybe is a problem because of the size of the partitions and fdisk cannot handle it correctly.
http://anothersysadmin.wordpress.com/2008/09/30/fdisk-and-the-15tb-partition-size-limit/
http://www.cyberciti.biz/tips/fdisk-unable-to-create-partition-greater-2tb.html
http://anothersysadmin.wordpress.com/2008/09/30/fdisk-and-the-15tb-partition-size-limit/
http://www.cyberciti.biz/tips/fdisk-unable-to-create-partition-greater-2tb.html
Por que hacerlo dificil si es posible hacerlo facil? - Why do it the hard way, when you can do it the easy way?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО09-21-2009 06:15 AM
тАО09-21-2009 06:15 AM
Re: Difficulty with fdisk and cciss Raid 5
Thank you for the speedy response.
No one is ever really going to be free until nerd persecution ends.
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