Quantcast
Channel: VMware Communities : Popular Discussions - VI: VMware ESX® 3.0
Viewing all articles
Browse latest Browse all 60069

Partition Table differences... should I be alarmed?

$
0
0

So... I know very little about 'nix environments... which is why I figured I'd better go off to ask people who do know more.

 

I'm trying to troubleshoot why my ESX hosts can see 8 LUNs on my SAN, but cannot see a 9th that I just created -I haven't given up on trying to figure that one out myself, but it did bring to light other information that I wanted to run past you.  Please note the <------- arrows located at the parts which worry me.

 

# fdisk -l /dev/sda

 

Disk /dev/sda: 124.5 GB, 124552151040 bytes

255 heads, 63 sectors/track, 15142 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

   Device Boot    Start       End    Blocks   Id  System

/dev/sda1             1     15142 121628051   fb  Unknown   <----


This looks like it is normal... I think...

#

 

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

 

# fdisk -l /dev/sda1

 

Disk /dev/sda1: 124.5 GB, 124547124224 bytes

255 heads, 63 sectors/track, 15141 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

Disk /dev/sda1 doesn't contain a valid partition table    <----


this scares the HELL out of me... I've had partition problems out the wazoo in the past.

#

 

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

 

# fdisk /dev/sda1

Device contains neither a valid DOS partition table, nor Sun, SGI or OSF disklabel

Building a new DOS disklabel. Changes will remain in memory only,

until you decide to write them. After that, of course, the previous

content won't be recoverable.

 

 

The number of cylinders for this disk is set to 15141.

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)

Warning: invalid flag 0x0000 of partition table 4 will be corrected by w(rite)    <----


This also really scares me.

 

Command (m for help): p

 

Disk /dev/sda1: 124.5 GB, 124547124224 bytes

255 heads, 63 sectors/track, 15141 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

     Device Boot    Start       End    Blocks   Id  System

 

Command (m for help):

 

/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\/\

 

# fdisk -l /dev/sdd

 

Disk /dev/sdd: 26.8 GB, 26843136000 bytes        <----


Okay, that should be about it... the LUN is actually 25GB though

255 heads, 63 sectors/track, 3263 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

   Device Boot    Start       End    Blocks   Id  System

/dev/sdd1             1     16709 134214978+  fb  Unknown

# fdisk -l /dev/sdd1

 

Disk /dev/sdd1: 137.4 GB, 137436137984 bytes   <----


What?  137.4GB?

255 heads, 63 sectors/track, 16708 cylinders

Units = cylinders of 16065 * 512 = 8225280 bytes

 

Disk /dev/sdd1 doesn't contain a valid partition table

#


Viewing all articles
Browse latest Browse all 60069

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>