[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Odd partition tables on Lenny



I've got Lenny installed on a Sun Enterprise 4500. When I list partitions with fdisk, I get duplicate entries, almost as if fdisk is recursing down into slice 3 on all dislabels or something, reading the partition table from that as well. Furthermore, it freaks out about the first disk, which was partitioned and formatted by the installer:

thwomp:/mnt# fdisk -l
Detected sun disklabel with wrong version [0x00000000].
Detected sun disklabel with wrong sanity [0x00000000].
Detected sun disklabel with wrong num_partitions [0].
Warning: Wrong values need to be fixed up and will be corrected by w(rite)

Disk /dev/sda (Sun disk label): 255 heads, 63 sectors, 2213 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
/dev/sda1             0      1945  15623212+   1  Boot
/dev/sda2          1945      2213   2152710   82  Linux swap
/dev/sda3             0      2213  17775922+   5  Whole disk
Detected sun disklabel with wrong version [0x00000000].
Detected sun disklabel with wrong sanity [0x00000000].
Detected sun disklabel with wrong num_partitions [0].
Warning: Wrong values need to be fixed up and will be corrected by w(rite)

Disk /dev/sda1 (Sun disk label): 255 heads, 63 sectors, 2213 cylinders
Units = cylinders of 16065 * 512 bytes

    Device Flag    Start       End    Blocks   Id  System
/dev/sda1p1             0      1945  15623212+   1  Boot
/dev/sda1p2          1945      2213   2152710   82  Linux swap
/dev/sda1p3             0      2213  17775922+   5  Whole disk
Detected sun disklabel with wrong version [0x00000000].
Detected sun disklabel with wrong sanity [0x00000000].
Detected sun disklabel with wrong num_partitions [0].
Warning: Wrong values need to be fixed up and will be corrected by w(rite)

Disk /dev/sda3 (Sun disk label): 255 heads, 63 sectors, 2213 cylinders
Units = cylinders of 16065 * 512 bytes

    Device Flag    Start       End    Blocks   Id  System
/dev/sda3p1             0      1945  15623212+   1  Boot
/dev/sda3p2          1945      2213   2152710   82  Linux swap
/dev/sda3p3             0      2213  17775922+   5  Whole disk

Disk /dev/sdb (Sun disk label): 255 heads, 63 sectors, 8932 cylinders
Units = cylinders of 16065 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
/dev/sdb1             1      8932  71738257+  83  Linux native
/dev/sdb3             0      8932  71746290    5  Whole disk

Disk /dev/sdb3 (Sun disk label): 255 heads, 63 sectors, 8932 cylinders
Units = cylinders of 16065 * 512 bytes

    Device Flag    Start       End    Blocks   Id  System
/dev/sdb3p1             1      8932  71738257+  83  Linux native
/dev/sdb3p3             0      8932  71746290    5  Whole disk

Disk /dev/sdc (Sun disk label): 64 heads, 32 sectors, 34732 cylinders
Units = cylinders of 2048 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
/dev/sdc1             1     34732  35564544   83  Linux native
/dev/sdc3             0     34732  35565568    5  Whole disk

Disk /dev/sdc3 (Sun disk label): 64 heads, 32 sectors, 34732 cylinders
Units = cylinders of 2048 * 512 bytes

    Device Flag    Start       End    Blocks   Id  System
/dev/sdc3p1             1     34732  35564544   83  Linux native
/dev/sdc3p3             0     34732  35565568    5  Whole disk


Some background info, the first disk is on the built-in esp scsi, and was partitioned manually with the installer, and formatted with same. The second two disks are both fibre channel and are on an Emulex PCI card in a PCI I/O module. I created partition tables on them manually with fdisk later, and formatted them myself. Now, this duplicate partition table thing isn't a big problem, except that is messes with the RAID. Here's a couple of other disks I have:

Disk /dev/sdd (Sun disk label): 64 heads, 32 sectors, 8637 cylinders
Units = cylinders of 2048 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
/dev/sdd1             1      8637   8843264   fd  Linux raid autodetect
/dev/sdd3             0      8637   8844288    5  Whole disk

Disk /dev/sdd3 (Sun disk label): 64 heads, 32 sectors, 8637 cylinders
Units = cylinders of 2048 * 512 bytes

    Device Flag    Start       End    Blocks   Id  System
/dev/sdd3p1             1      8637   8843264   fd  Linux raid autodetect
/dev/sdd3p3             0      8637   8844288    5  Whole disk

... /dev/sd[e-m] omitted....

Disk /dev/sdn (Sun disk label): 64 heads, 32 sectors, 8637 cylinders
Units = cylinders of 2048 * 512 bytes

   Device Flag    Start       End    Blocks   Id  System
/dev/sdn1             1      8637   8843264   fd  Linux raid autodetect
/dev/sdn3             0      8637   8844288    5  Whole disk

Disk /dev/sdn3 (Sun disk label): 64 heads, 32 sectors, 8637 cylinders
Units = cylinders of 2048 * 512 bytes

    Device Flag    Start       End    Blocks   Id  System
/dev/sdn3p1             1      8637   8843264   fd  Linux raid autodetect
/dev/sdn3p3             0      8637   8844288    5  Whole disk

These 11 disks are all part of a software RAID array. They were all partitioned/formatted on this box, and are all fibre channel disks. I can start the array just fine, and all goes well. But if the machine is shut down and brought back up, when the kernel goes to detect and assemble arrays, I get a recursive loop on the console where the kernel detects that the superblock on /dev/sdn1 is too similar to the superblock on /dev/sdn3p1 (gee, I wonder why). I have to power off the fibre channel box, allow the kernel to get past the raid autodetect, then power it back on. Once that's done, I can re-assemble the array manually.

-Ian


Reply to: