Slow install for PVE1.5

[nick]

In this moment I can't I just buy them and I don't have the budget to buy another 2 disk's. I wait maybe Tom can provide me a trick to partition the disk. But the strange part is thha WD say's that for LINUX and MACOSX there are no problems. Only XP it's affected...

Or PVE work with different format?

 

[resignation]

They say that because Windows XP does not have a tool that can create and properly align partitions, while Linux and OSX does. However that does not mean it will work 'out of the box', as you still need to manually create the partitions for the drive to function correctly as stated in the previous post/thread..

 

[tom]

I have no better idea here, go the Debian Lenny way.

 

[nick]

can someone tell me how I need to format the disk? I never make an install on LVD disk partition...or make some different disk setup. An example maybe, a link with an example...

I will start with Debian Lenny 5.04 AMD64.

 

[nick]

I make another 2 tests:

1) I try to install Debian Lenny 5.04 AMD64 with automatic partition...I leave 2 hours on partitioning step, and still not finish.
2) I make a clean install on an 160GB disk, and after that I try to clone that disk with acronis. This app report 8 days to finish the task.

I still think that it's a matter of drivers. In Windows, on the same machine these disk's work correct. On linux, very bad. I will try ather distro (CentOS and Suse) to see the results.

 

[illodius]

Hmmm interesting thread. I have installed it once on a new system :
Intel Core Dual E5400 2.7Ghz Asus P5G41T-M-LX motherboard Kingston 2 GIG 1333Mhz DDR3 Memory WD 500Gig HDD inbuilt Ethernet, and first time installed sweet and fast, then installed it again (putting WIFIGATOR on it!) I have the "IO DELAYS" sitting at 99.59%, and yes it's a WD, so best to try a new drive as the systems takes 30 mins to start up and seems DOG slow when running. PS, not a linux man really, just having to build a server for local WIFI authentication, need to use www.WiFigator.com on it so bought a new server.....

 

[nick]

I try to install on debian lenny AMD64 but to format the disk in ext3 will take 1-2 days; so I give up. I think it's something incompatible in Linux...I still search for a sollution.

 

[illodius]

hmmm interesting thread. I have installed it once on a new system :
Intel core dual e5400 2.7ghz asus p5g41t-m-lx motherboard kingston 2 gig 1333mhz ddr3 memory wd 500gig hdd inbuilt ethernet, and first time installed sweet and fast, then installed it again (putting wifigator on it!) i have the "io delays" sitting at 99.59%, and yes it's a wd, so best to try a new drive as the systems takes 30 mins to start up and seems dog slow when running. Ps, not a linux man really, just having to build a server for local wifi authentication, need to use www.wifigator.com on it so bought a new server.....

update: Was the western digital green hdd. Proxmox doesn't like them at all, using a seagate now, no dramas like a new machine, which it is!

 

[nick]

I make a test recomanded by WD: I use Acronis WD edition to clone the existing disk to WD disk. The cloning process was OK, but now I need to repair the bootloader (LILO). PVE have a procedure for this? How I can make the new disk to boot?

 

[tom]

fyi, we are using grub as bootloader. there are many tools around (google) fixing grub.

 

[nick]

Hi All,

after 2 weeks of tests I have the first conclusions. Are good so that's why I want to share this information. First, the problem was fixed, with not real explanations...but this is the conclusion:

1) The disk need to be installed on server WITHOUT any contact with the chase. If the disk do not have any contact with the chase everything it's perfect and the disk work normal.
2) If I mount the disk normal (with screws) the disk work but very very slow...and with a lot of errors. I test this on 3 different servers and the same results. So the problems seems to be an electrical issue...but no real explanations. Other disks are working perfect in the same chase.

Anyway, I mount him without contact between chase and disk with plastic screws and now it's normal.

These are the results with 2 machines already started on PVE:

pve_slave_1:~# pveperf
CPU BOGOMIPS:      19200.65
REGEX/SECOND:      792346
HD SIZE:           94.49 GB (/dev/mapper/pve-root)
BUFFERED READS:    84.63 MB/sec
AVERAGE SEEK TIME: 11.51 ms
FSYNCS/SECOND:     908.95
DNS EXT:           112.32 ms
DNS INT:           2.01 ms (xxxx.xx)
pve_slave_1:~# pveperf
CPU BOGOMIPS:      19200.65
REGEX/SECOND:      797321
HD SIZE:           94.49 GB (/dev/mapper/pve-root)
BUFFERED READS:    81.63 MB/sec
AVERAGE SEEK TIME: 11.56 ms
FSYNCS/SECOND:     827.48
DNS EXT:           141.92 ms
DNS INT:           2.00 ms (xxxx.xx)

 

[tom]

use shorter screws - better?

 

[nick]

it's not about screws...it's about metal contact between hard disk and chase. I test without screws...same results!
The plastic screws are sale length...so it's not a reason!

The solution was discovered by mistake...when I make a test and I put the hard disk on the plastic bag that he came...and on that moment the disk was work normal

 

[whinpo]

incredible...

you need to be lucky to find the solution to such a problem...