Slow install for PVE1.5

nick

Renowned Member
Mar 28, 2007
364
1
83
Hi All,

I just replace an 160GB disk with another one new disk (WD6400AARS) and I start a new install from a CD with the image download this morning.

I start setup, I set the IP, but from 3 hours since I start the install process the progress is on 22% "Creating data filesystem". It's not too slow? This server was used for 2 years already on PVE. It's a Xeon 3220 with 8GB RAM.

I need to check something else?

Thank you for help.
 
After 4hours the PVE installation failed and I receive this message:

command 'mkfs.ext3 -m 0 -F /dev/pve/data' failed with exit code 1 ar /usr/bin/proxinstall line 153

What can I do? It's a problem with Hard Disk or something else?
 
After 4hours the PVE installation failed and I receive this message:

command 'mkfs.ext3 -m 0 -F /dev/pve/data' failed with exit code 1 ar /usr/bin/proxinstall line 153

What can I do? It's a problem with Hard Disk or something else?
Hi,
i have done the same some days ago with an old 160GB-Disk and it's takes about 2 min. for the filesystem.
Any errors on the error-console?
Does the bios reconice the hard disc well?
Perhaps try another sata-port or a bios-update (it's perhaps a sata-3 hd?).

Udo
 
The model is
WD Caviar Green
SATA Hard Drives
640 GB, SATA 3 Gb/s, 64 MB Cache

the BIOS is the last version available and see the hard correct. Also the setup recognize the disk as 596GB capacity...

Other errors...I don't see. I change the hard disk with another one. The setup it's already started for 40 minutes and the progress bar is on 23%
If I receive the error again I will look closer on this error.

I hope it's not an hardware incompatibility.
 
Not sure if it's related, but i've had nothing but problems using WD Green drives under Linux. The drives would go offine, take forever to format, all kinds of odd behaviour..

I would stick with WD Black drives, much better performance and none of the green power saving junk in the mix.
 
Not sure if it's related, but i've had nothing but problems using WD Green drives under Linux. The drives would go offine, take forever to format, all kinds of odd behaviour..

I would stick with WD Black drives, much better performance and none of the green power saving junk in the mix.
Hi,
i think to save power make sense...
I had the same disk since over one year inside my desktop at home without problems (and only with linux). But perhaps WD had trouble with some disks...

Udo
 
Honestly this sounds like a disk issue not a Proxmox install issue. Have you tried to diagnose the disk to see if it bad? I recommend running badblocks on it for a few days and seeing the results.

But I second the statement to stay with WD Black's or I would also recommend the RE3's.
 
I just see today, after I leave installation started over the night, that the PVE it's installed. I reboot the system and it's OK. Maybe it's take much time to format the disk...I don't know. Anyway, I will make another test with the first disk who give me that error.

I will post the results
 
I start a new test. I will post the exact values after I finish. From memory (because I run this test after restart) I obtain:

CPU BOGOMIPS: 19200.88
REGEX/SECOND: 796169
HD SIZE: ???? GB (/dev/mapper/pve-root)
BUFFERED READS: arround 90 MB/sec
AVERAGE SEEK TIME: 10-11 ms
FSYNCS/SECOND: around 450
 
OK, I make another tests.
Another strange situation that I observe on this disk. I run pveperf 3 times continuos...and look to results:

Code:
pve_slave_1:~# pveperf
CPU BOGOMIPS:      19200.95
REGEX/SECOND:      802398
HD SIZE:           94.49 GB (/dev/mapper/pve-root)
BUFFERED READS:    39.15 MB/sec
AVERAGE SEEK TIME: 11.12 ms
FSYNCS/SECOND:     498.28
DNS EXT:           91.86 ms
DNS INT:           1.64 ms (xxxxx)
pve_slave_1:~# pveperf
CPU BOGOMIPS:      19200.95
REGEX/SECOND:      801556
HD SIZE:           94.49 GB (/dev/mapper/pve-root)
BUFFERED READS:    0.51 MB/sec
AVERAGE SEEK TIME: 35.08 ms
FSYNCS/SECOND:     309.04
DNS EXT:           100.18 ms
DNS INT:           1.82 ms (xxxxx)
pve_slave_1:~# pveperf
CPU BOGOMIPS:      19200.95
REGEX/SECOND:      791993
HD SIZE:           94.49 GB (/dev/mapper/pve-root)
BUFFERED READS:    1.26 MB/sec
AVERAGE SEEK TIME: 12.18 ms
FSYNCS/SECOND:     388.93
DNS EXT:           97.81 ms
DNS INT:           1.90 ms (xxxxxx)

Why I obtain this values? I have no VM Installed on this server.

pve_slave_1:~# pveversion -v

pve-manager: 1.5-8 (pve-manager/1.5/4674)
running kernel: 2.6.24-10-pve
proxmox-ve-2.6.24: 1.5-21
pve-kernel-2.6.24-10-pve: 2.6.24-21
pve-kernel-2.6.18-2-pve: 2.6.18-5
qemu-server: 1.1-11
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-10
vncterm: 0.9-2
vzctl: 3.0.23-1pve8
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-2
 
I run again pveperf aster 5 minutes an these are the results:

Code:
pve_slave_1:~# pveperf
CPU BOGOMIPS:      19200.95
REGEX/SECOND:      786973
HD SIZE:           94.49 GB (/dev/mapper/pve-root)
BUFFERED READS:    80.30 MB/sec
AVERAGE SEEK TIME: 10.75 ms
FSYNCS/SECOND:     527.04
DNS EXT:           93.81 ms
DNS INT:           2.17 ms (xxxxxx)

pve_slave_1:~# pveperf
CPU BOGOMIPS:      19200.95
REGEX/SECOND:      793889
HD SIZE:           94.49 GB (/dev/mapper/pve-root)
BUFFERED READS:    80.64 MB/sec
AVERAGE SEEK TIME: 11.81 ms
FSYNCS/SECOND:     658.35
DNS EXT:           107.44 ms
DNS INT:           1.97 ms (smc.ro)

I don't understand...what can I do?
 
I set in BIOS SATA mode to Legacy (last was Enhanced) and now the tests (pveperf) return constant values. But, in some cases the system respond very slow, and I see a very high I/O Delay (more then 30%) - in situation that on this server it's no virtual machine installed.

Anyone have any idea about this?
 
I set in BIOS SATA mode to Legacy (last was Enhanced) and now the tests (pveperf) return constant values. But, in some cases the system respond very slow, and I see a very high I/O Delay (more then 30%) - in situation that on this server it's no virtual machine installed.

Anyone have any idea about this?
Hi Nick,
i think you should test the same with an different disk.

Udo
 
I install hdparm to see the status, and look OK.

Code:
pve_slave_1:~# hdparm -i /dev/sda

/dev/sda:

 Model=WDC WD6400AARS-00Y5B1                   , FwRev=80.00A80, SerialNo=     WD-WCAV5A932942
 Config={ HardSect NotMFM HdSw>15uSec SpinMotCtl Fixed DTR>5Mbs FmtGapReq }
 RawCHS=16383/16/63, TrkSize=0, SectSize=0, ECCbytes=50
 BuffType=unknown, BuffSize=0kB, MaxMultSect=16, MultSect=?16?
 CurCHS=16383/16/63, CurSects=16514064, LBA=yes, LBAsects=1250263728
 IORDY=on/off, tPIO={min:120,w/IORDY:120}, tDMA={min:120,rec:120}
 PIO modes:  pio0 pio3 pio4
 DMA modes:  mdma0 mdma1 mdma2
 UDMA modes: udma0 udma1 udma2 udma3 udma4 udma5 *udma6
 AdvancedPM=no WriteCache=enabled
 Drive conforms to: Unspecified:  ATA/ATAPI-1,2,3,4,5,6,7

 * signifies the current active mode
 
WD Green drives are junk and horrible under linux, plain and simple.

Google 'WD Green Linux' and look at the endless threads about how much trouble they give most people who own them. Do yourself a favour and put in a different drive, even a $50 500GB Seagate 7200.12 SATA will be much much better..
 
I make a install on this server with Win 7 Pro x64 and this version work perfect. I will test the server with Debian 6 AMD64 to see if it's a general problem with Debian distro. I will test also with CentOS 5 X64
 
And how I can solve this issue? PVE create the partition automatically...and I can't change anything in partition properties. Maybe there are hidden options in PVE for disk that can help us to solve this issue?
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!