Displaying 3 results from an estimated 3 matches for "9c2d".
Did you mean:
902d
2019 Jul 23
2
mdadm issue
...dev/md/export_1 metadata=1.2 name=<server>:export_1
UUID=637ef224:91b445d8:69d48980:adc8bc70
and, from /etc/fstab, the same drives
/dev/mapper/luks-5e007234-cd4c-47c6-b305-734f353a4405 /
xfs defaults,x-systemd.device-timeout=0 0 0
/dev/mapper/luks-3da4ae38-b78a-4fb4-9c2d-b029a9b16378 /export/1 xfs
defaults 0 0
excerpt the last luks doesn't exist. They *both* say UUID, so it's *so*
simple to understand (NOT). I got the mdraid UUID from mdadm --examine
--scan.
mark
mark
2019 Jul 23
2
mdadm issue
Just rebuilt a C6 box last week as C7. Four drives, and sda and sdb for
root, with RAID-1 and luks encryption.
Layout:
lsblk
NAME MAJ:MIN RM SIZE RO TYPE
MOUNTPOINT
sda 8:0 0 931.5G 0 disk
??sda1 8:1 0 200M 0 part
/boot/efi
??sda2
2013 Jan 17
0
XCP 1.1 SR_BACKEND_FAILURE_46 The VDI is not available [opterr=VDI already attached RW] issue
...with attached lvmoiscsi SR.
Is there any solution to this problem?
/var/log/SMlog:
[32484] 2013-01-17 14:59:44.200883 vdi_activate {''sr_uuid'':
''e33281eb-ba4c-3829-9b61-7c64764dff9c'', ''subtask_of'':
''OpaqueRef:78dd7c48-383b-253c-9c2d-a60edcb9e2e1'', ''vdi_ref'':
''OpaqueRef:9e3252f6-403b-7045-2147-401beeafc8ca'', ''vdi_on_boot'':
''persist'', ''args'': [''true''], ''vdi_location'':
''ff54dd4f-5ad3-4...