Search results

hmm, you might be right. I often had some issues with this usb drive. I'll give it a try. Thanks

-- -- -- -- -- -- -- 40 51 00 ff ff ff 0f Error: WP at LBA = 0x0fffffff = 268435455 Commands leading to the command that caused the error were: CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name -- -- -- -- -- -- -- -- ---------------- --------------------...

SMART Attributes Data Structure revision number: 10 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_ FAILED...

ok, for the record, I ran the commands without mounting the disk first anyway. Thanks first part: root@pve:~# smartctl -a /dev/sdd smartctl 7.1 2019-12-30 r5022 [x86_64-linux-5.4.34-1-pve] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF...

I ran smartctl -a /dev/sdd and my HD seems to be ok.

Hi, I ran two backup jobs of two of my VMS to an external usb HD. The first one got success, but I got a error message for the second backup job: ..... 2020-09-14 09:26:37 INFO: status: 66% (58118701056/88046829568), sparse 1% (1627414528), duration 1856, read/write 30/29 MB/s 2020-09-14...

I installed the ntfs-3g packet. I thought that I would fix the issue. I then mounted the HD again: root@pve:/# mount -t ntfs-3g /dev/sdd1 /media/external But when in datacenter->storage I tried to create a Directory, I got this message this time: illegal path for directory storage...

Since I wanted to use my external HD usb drive to backup a couple of VMs, I plugged it on my Proxmox machine and I ran: fdisk -l ..... Disk /dev/sdd: 465.8 GiB, 500107862016 bytes, 976773168 sectors Disk model: Transcend Units: sectors of 1 * 512 = 512 bytes Sector size...

I have no problem at rebooting/turning off the machine. Most importantly, I need to figure out if something can go wrong. Thanks By the way, is there any way to backup the Proxmox OS (not data or VMs) or the entire configuration. Do I need to use a software like, say, RescueZilla?

Can I modify it on the fly without messing the network configuration up somehow? Thanks

I have this setup on my Proxmox machine's network: and this for my pfsense VM network devices: vmbr0 is the pfsense's WAN port, while the vmbr1 is its LAN port at which are connected the virtual adapters of other VMs created in Proxmox as well as the LAN physical port, so that pfsense can...

I ran my Proxmox machine this morning and got this error message at the boot: It was taking a lot of time, so I turned off the machine and unplugged the HD. I then got this at the next boot: It worked, Proxmox started. What does it mean? What happened? Thanks

Ok, I did it!! Everything went fine. Still eager to know about question 2. Thank you

Ok 1) I quote a line above # I'm assuming that scsi1 is available on that VM. I have this for my target VM. Is it ok to run qm set VMID --scsi1 /dev/disk/by-id/THE-ID-YOU-GOT-FROM-THE-PREVIOUS-STEP ? 2) The new disk is now recognized as /dev/sdb. What if I add another disk? Could it mess...

As for the second possibility, should I run the "Initialize disk with GPT" button first? Thanks

Hi everyone, I plugged a rather old SATA HD to my PC with Proxmox installed on it. I'd like now to assign it directly to OMV5 (one of my VMS installed in Proxmox) as a backup disk. Some details about it (sdb): Disk /dev/sdb: 114.5 GiB, 122942324736 bytes, 240121728 sectors Disk model: Maxtor...

Yes, you are most probably right. Thank you very much

here it is: root@pve:~# pveversion -v proxmox-ve: 6.2-1 (running kernel: 5.4.34-1-pve) pve-manager: 6.2-4 (running version: 6.2-4/9824574a) pve-kernel-5.4: 6.2-1 pve-kernel-helper: 6.2-1 pve-kernel-5.4.34-1-pve: 5.4.34-2 ceph-fuse: 12.2.11+dfsg1-2.1+b1 corosync: 3.0.3-pve1 criu: 3.11-3...

root@pve:/etc/pve# cat storage.cfg dir: local path /var/lib/vz content iso,backup,vztmpl lvmthin: local-lvm thinpool data vgname pve content images,rootdir lvm: VM vgname VM content rootdir,images nodes pve shared 0 dir...

I ran a backup of another VM and it went smoothly, and as I already said, I did it for the same VM too a week ago, and everything went ok on the same storage. Strange Thanks