Search results

Thats probably it indeed.

Is this something you could safely do on a proxmox node (outside container on the node itself)? Or is it safer to go with the mentioned NFS3 option inside a container? Looking for a simple way to setup a nfs directory inside the cluster for backup purposes.

Hi Udo, Thanks. We eventually solved it. I already used UUID's after prvious advice from you, this was not the problem. We booted with proxmox debug. Then tried to reinstall grub. After that we got the menu upon boot instead of just the cursor, but the system would not load any kernel because...

Tonight I upgraded all our nodes from pm 1.3 to 1.8 an kernel 2.24 to 2.18 One of the nodes that contain all our backups won't boot anymore. BEcause of the large disksize it has two lun's. No matter wich I select in the bios it won;t boot. I just get a black screen with a cursor blinking. I...

Recently I upgraded two of our nodes to 1.8 with kernel 1.18. I made a tenporarly new cluster of these two nodes. Entered the backups (snapshot) information for both nodes trough the master. Backups work, I see the naming convention is changed (btw. the hostname of the node in the name of the...

sorry, found the answer; http://forum.proxmox.com/threads/6656-Howto-add-a-view-of-a-harddisc-in-Local-System-Status?highlight=hd+data+space It would be nice indeed to be able to see the data space used on all nodes in one view like in 1.3.

I upgraded two nodes from 1.3 to 1.8 (kernel .18). No I noticed the frontend does not show the space for the data partition. Is that normal?

Hi Tom, I'm really very suprised to hear that most new Proxmox users don't use OpenVZ. Is everybody suddenly switching to Windows? I can't imagine that Openvz has become so marginal that you choose to release a unstable version as default, but I probably (certainly) dont oversee everything...

We decided to upgrade our nodes from proxmox 1.3 to 1.8. So I took a look at the wiki: http://pve.proxmox.com/wiki/Downloads It suggested installing the 2.6.32 kernel branch. So I did. After having some problems we started doubting the versions, 6.18 says latest stable, but 6.32 is the default...

Finally figured it out :/ The missing disk IS /sda I followed the great Udo steps with /dev/sda and my vz partition is growing while I watch. Now, time for some paracetamol.

Lets try again, sorry but I really need this fixed. I found this solution given by Udo: Now I'm not sure If I need to do pvcreate /dev/sdb and vgextend pve /dev/sdb or do I need to use "/dev/sdb1" or "/dev/sdb2" in my case? again my fdisk -l:

I found an old thread that said to run pvcreate. I did that obviously I missed a step: so still my 7.9B not available. I'll wait for your answer now ;)

I managed to get proxmox installed on the smaller partition. I now get at df -h fdisk -l blkid I tried to mount /dev/sda -> /var/lib/vz But I get a message about blocks upon booting, so I guess I need some formatting orso to do. I understand this is quite basic linux but could someone please...

I'm doing a reinstall of a server that had 8 1TB disks with 8 2TB disks. I'm installing version 1.3 for the time being, next week we will shift to 1.8. After the 7 hour initialisation of the raid-10 partion of 8TB I tried to install proxmox. Unfortunaly it gave: unable to create data volume at...

Thanks Udo, I experimented some more and indeed the UUID solves it all. Thank you very much!

I tested a little more and still don't quite get it, hope someone can explain a bit more. The problem apparently appears when I attach a usb-drive to the server. The drive is not in fstab because I usually mount it manually. If I remove the USB drive the server boots normal, with the disk...

I understand, the devices where renamed because the boot order changed... Never noticed that before. Thanks, I learned a couple of things :)

I have no idea what happened, but I changed the boot order in the bios and let the raidcard boot first instead of the cdrom and that seems to solve it. I don't understand why this works? It should have no influence? What was changed by the upgrade that caused this behaviour?

Hi Udo, Thank you for your help, much appreciated. I understand I have to edit the fstab? I did a fdisk -l and this was the output: Does this tell me what to change /dev/sda1 to in the fstab?

I'm upgrading (luckily a test server) from PM 1.3 to 1.8 with kernel 2.6.32 I followed the steps on the dowload page. The server uses a 3ware raidcard 2x sata. All was running fine without problems before the reboot. I can't make a screenshot so I post a foto of the error: I searched the...