Couple issues found during 2.0 testing

[gcmartin]

In testing Proxmox VE, several issues were found.

Problem#1
I seem to remember fdisk issues being reported last year. See below for the problem accounting. Proxmox is a polished product. Although this is correctable by the user, this kind of issue should not occur.

Problem#2
All modern servers have 2 LAN connections on te Motherboard. Proxmox does not ask which adapter to be used for LAN to WAN service at installation time. Nor, does it do an auto-detect for where the LAN cabe is plugged.

These 2 items, you may want to address before you make Proxmox VE generally available.(GA)

All in all, the 2.0 beta looks very well. Thanks for this great work.


------------------------------------ FDISK Problems -----------------------------------
From Proxmox VE

# fdisk -l
 
 Disk /dev/sda: 10.3 GB, 10262568960 bytes
 255 heads, 63 sectors/track, 1247 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: 0x0001bbb8
 
    Device Boot      Start         End      Blocks   Id  System
 /dev/sda1   *           1          66      523264   83  Linux
 Partition 1 does not end on cylinder boundary.
 /dev/sda2              66        1248     9497600   8e  Linux LVM
 
 Disk /dev/dm-0: 2415 MB, 2415919104 bytes
 255 heads, 63 sectors/track, 293 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: 0x00000000
 
 Disk /dev/dm-0 doesn't contain a valid partition table
 
 Disk /dev/dm-1: 1207 MB, 1207959552 bytes
 255 heads, 63 sectors/track, 146 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: 0x00000000
 
 Disk /dev/dm-1 doesn't contain a valid partition table
 
 Disk /dev/dm-2: 4894 MB, 4894752768 bytes
 255 heads, 63 sectors/track, 595 cylinders
 Units = cylinders of 16065 * 512 = 8225280 bytes
 Sector size (logical/physical): 512 bytes / 512 bytes
 I/O size (minimum/optimal): 512 bytes / 512 bytes
 Disk identifier: 0x00000000
 
 Disk /dev/dm-2 doesn't contain a valid partition table

From PartedMagic

root@PartedMagic:~# fdisk -l

Disk /dev/sda: 10.3 GB, 10262568960 bytes
255 heads, 63 sectors/track, 1247 cylinders, total 20044080 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0001bbb8

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *        2048     1048575      523264   83  Linux
/dev/sda2         1048576    20043775     9497600   8e  Linux LVM

Disk /dev/mapper/pve-swap: 1207 MB, 1207959552 bytes
255 heads, 63 sectors/track, 146 cylinders, total 2359296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/pve-swap doesn't contain a valid partition table

Disk /dev/mapper/pve-root: 2415 MB, 2415919104 bytes
255 heads, 63 sectors/track, 293 cylinders, total 4718592 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/pve-root doesn't contain a valid partition table

Disk /dev/mapper/pve-data: 4894 MB, 4894752768 bytes
255 heads, 63 sectors/track, 595 cylinders, total 9560064 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

Disk /dev/mapper/pve-data doesn't contain a valid partition table

 

[dietmar]

fdisk is probably an outdated - try parted.

 

[gcmartin]

Thanks @Dietmar
I was referring to the message that is shown in the screen that reflects
"Disk device doesn't contain a valid partition table"

Thanks is the part about the polishing that I thought Promox would consider addressing. The message shown the results of the Proxmox install process....not by any user action or need.

Albeit small item to show you, it does raise eyelids when administrators see this because this need-not occur. Proxmox is a rather mature product.

How this helps

 

[dietmar]

Albeit small item to show you, it does raise eyelids when administrators see this because this need-not occur.

How can I avoid that?

 

[udo]

Thanks @Dietmar
I was referring to the message that is shown in the screen that reflects
"Disk device doesn't contain a valid partition table"
...

Hi,
but the system can't see an partitiontable on a single partition. That's normal also on other linux-systems.
Look this

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0xaf70c8fe

   Device Boot      Start         End      Blocks   Id  System
/dev/sda1            2048      128519       63236   fd  Linux raid autodetect
/dev/sda2          128520    63055124    31463302+  fd  Linux raid autodetect
/dev/sda3        63055125   126110249    31527562+  fd  Linux raid autodetect
/dev/sda4       126110250   623321999   248605875   fd  Linux raid autodetect

Disk /dev/sdb: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00041816

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048      128519       63236   fd  Linux raid autodetect
/dev/sdb2          128520    63055124    31463302+  fd  Linux raid autodetect
/dev/sdb3        63055125   126110249    31527562+  fd  Linux raid autodetect
/dev/sdb4       126110250   623321999   248605875   fd  Linux raid autodetect                                                                         
                                                                                                                                                      
Disk /dev/md0: 64 MB, 64684032 bytes                                                                                                                  
2 heads, 4 sectors/track, 15792 cylinders, total 126336 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

[B]Disk /dev/md0 doesn't contain a valid partition table[/B]

Where no partitiontable is, they can't displayed...

Udo

 

[gcmartin]

Thanks @Dietmar. Did a little digging on these.
FDISK - fdisk is old. But, functional. (I think this is true) When fdisk creates a partition, it works on a cylinder boundary for partition allocation. Thus this warning does not arise. But, when other tools create partition, they create it on a block boundary. Here's why the problem exist. FURTHER, I have found that using GPARTED, I can create a partition on a cylinder boundary. When this is done, it averts the problem you have. I haven't used Parted in over 10 years so, I'm not sure how you would use parted at system build-time to create the partitions so that you skip this issues; but, I'm sure there's a way.

Other issue. I have found my instructions on how I fixed it the last time. I cost me 3 reboots, but system boots fast.

Now, I have a system where those messages do not occur. (Again, I wish I could give you more information on how you would do these things at build-time, but, because I am unfamiliar with your process for system build, I cannot help.

So, one is very easy for you to fix, the other probably will take a moment more in thought.

Hope this helps

 

[lojasyst]

Gcmartin

Can you tell me how can I fix the firt issue?

Thanks