Hi everyone,
I have to make a clarification:
Trying to create a CT/VM or a logical volume on my proxmox server does not work. lvcreate leads to the unclear error message
Since I was able to create the LVM on my notebook, and simply plugged the drive (usb 3.1) from the notebook (Arch, working) to the server (Debian, not working), there must be a difference in LVM on arch and LVM on debian/proxmox.
Does anybody know, how to get rid of the "bcache_invalidate is dirty"
Thank you,
Peer
I wanted to consolidate my local IT environment using proxmox .. yesterday ;-) .. and made a pretty stupid mistake:
I created LVMs on two 14 TB HDDs and attached them via usb 3.1 as external drives. Since I had trouble getting them into the proxmox-storage I formated them newly from within proxmox (with ext4 ..) what made then unusable.
I knew, that LVM works with physical and logical volumes. But my idea was, proxmox would take care of the correct partititon type, change it, and afterwards format and access it.
Now the drives are still being shown as LVMs, but do always throw errors, when I try zu change them:
If I wipe the disk:
But afterwards trying to change anything on the partition, i.e. delete it via cfdisk leads zu
( journalctl: )
[/code]
I also tried "chfdisk -z" and to "dd" the first 16 MB disk with random numbers. But no effect. Does anybody have an idea, how to get the disk working again?
Thanks
Peer
Here are some additional Information:
~# fdisk -x /dev/sdb ; fdisk -x /dev/sdc
I have to make a clarification:
Trying to create a CT/VM or a logical volume on my proxmox server does not work. lvcreate leads to the unclear error message
Code:
~# lvcreate -vvvv -n docker_home -L 30GB pm01_open
..
18:06:00.034945 label/label.c:1957 Error writing device /dev/sdb1 at 5632 length 1536.
01.051386 device/bcache.c:1374 WARNING: bcache_invalidate: block (0, 0) still dirty.
01.051424 format_text/format-text.c:965 Failed to write metadata to /dev/sdb1.
01.051430 metadata/metadata.c:3050 <backtrace>
01.051435 metadata/metadata.c:3059 Failed to write VG pm01_open.
..Since I was able to create the LVM on my notebook, and simply plugged the drive (usb 3.1) from the notebook (Arch, working) to the server (Debian, not working), there must be a difference in LVM on arch and LVM on debian/proxmox.
Does anybody know, how to get rid of the "bcache_invalidate is dirty"
Thank you,
Peer
At the first moment I thought it was my mistake. Now, that I know the issue a little bit better, I renamed the title (fomerly: "Accidentially format a LVM partition with ext4"). Leaving the posting for its technical details. |
I wanted to consolidate my local IT environment using proxmox .. yesterday ;-) .. and made a pretty stupid mistake:
I created LVMs on two 14 TB HDDs and attached them via usb 3.1 as external drives. Since I had trouble getting them into the proxmox-storage I formated them newly from within proxmox (with ext4 ..) what made then unusable.
I knew, that LVM works with physical and logical volumes. But my idea was, proxmox would take care of the correct partititon type, change it, and afterwards format and access it.
Now the drives are still being shown as LVMs, but do always throw errors, when I try zu change them:
Bash:
~# pvcreate test -d /dev/sdb1
No device found for test.
WARNING: ext4 signature detected on /dev/sdb1 at offset 1080. Wipe it? [y/n]: y
Wiping ext4 signature on /dev/sdb1.
Error writing device /dev/sdb1 at 1080 length 2.
WARNING: bcache_invalidate: block (0, 0) still dirty.
Failed to wipe ext4 signature on /dev/sdb1.
1 existing signature left on the device.If I wipe the disk:
Bash:
~# wipefs --all --force /dev/sdb
/dev/sdb: 8 bytes were erased at offset 0x00000200 (gpt): 45 46 49 20 50 41 52 54
/dev/sdb: 8 bytes were erased at offset 0xcbbbffffe00 (gpt): 45 46 49 20 50 41 52 54
/dev/sdb: 2 bytes were erased at offset 0x000001fe (PMBR): 55 aaBut afterwards trying to change anything on the partition, i.e. delete it via cfdisk leads zu
( journalctl: )
Bash:
Jul 13 11:36:28 proxmox01 kernel: I/O error, dev sdc, sector 27344764888 op 0x1:(WRITE) flags 0x800 phys_seg 5prio class 0
Jul 13 11:36:28 proxmox01 kernel: Buffer I/O error on dev sdc, logical block 3418095611, lost async page write
Jul 13 11:36:28 proxmox01 kernel: Buffer I/O error on dev sdc, logical block 3418095612, lost async page write
Jul 13 11:36:28 proxmox01 kernel: Buffer I/O error on dev sdc, logical block 3418095613, lost async page write
Jul 13 11:36:28 proxmox01 kernel: Buffer I/O error on dev sdc, logical block 3418095614, lost async page write
Jul 13 11:36:28 proxmox01 kernel: Buffer I/O error on dev sdc, logical block 3418095615, lost async page write
Jul 13 11:46:46 proxmox01 pvedaemon[997]: <root@pam> successful auth for user 'root@pam'I also tried "chfdisk -z" and to "dd" the first 16 MB disk with random numbers. But no effect. Does anybody have an idea, how to get the disk working again?
Thanks
Peer
Here are some additional Information:
Bash:
# lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 476.9G 0 disk
├─sda1 8:1 0 1007K 0 part
├─sda2 8:2 0 1G 0 part /boot/efi
└─sda3 8:3 0 475.9G 0 part
├─pve-swap 252:0 0 8G 0 lvm [SWAP]
├─pve-root 252:1 0 96G 0 lvm /
├─pve-data_tmeta 252:2 0 3.6G 0 lvm
│ └─pve-data 252:4 0 348.8G 0 lvm
└─pve-data_tdata 252:3 0 348.8G 0 lvm
└─pve-data 252:4 0 348.8G 0 lvm
sdb 8:16 0 12.7T 0 disk
└─sdb1 8:17 0 12.7T 0 part
sdc 8:32 0 12.7T 0 disk
└─sdc1 8:33 0 12.7T 0 part~# fdisk -x /dev/sdb ; fdisk -x /dev/sdc
Bash:
Disk /dev/sdb: 12.73 TiB, 14000519643136 bytes, 27344764928 sectors
Disk model: MG07ACA14TE
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: <UUID>
First usable LBA: 2048
Last usable LBA: 27344764894
Alternative LBA: 27344764927
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33
Device Start End Sectors Type-UUID UUID Name Attrs
/dev/sdb1 2048 27344762879 27344760832 <UUID> <UUID>
Disk /dev/sdc: 12.73 TiB, 14000519643136 bytes, 27344764928 sectors
Disk model: MG07ACA14TE
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: <UUID>
First usable LBA: 2048
Last usable LBA: 27344764894
Alternative LBA: 27344764927
Partition entries starting LBA: 2
Allocated partition entries: 128
Partition entries ending LBA: 33
Device Start End Sectors Type-UUID UUID Name Attrs
/dev/sdc1 2048 27344762879 27344760832 <UUID> <UUID>
Bash:
Last edited: