A partição criptografada Luks torna-se somente leitura quando tento escrever

0

Eu tenho uma unidade criptografada que eu montei na minha instalação do Ubuntu 17.10. Quando eu primeiro descriptografar o contêiner e montar a partição, ele aparece como 'rw' na montagem (saídas detalhadas abaixo). Assim que tento escrever qualquer coisa, recebo um erro que diz que é um sistema de arquivos somente para leitura e é exibido como 'ro' no mount. Eu posso ler os arquivos na unidade muito bem.

Não tenho certeza se isso é importante, mas se isso acontecer, essa instalação do Ubuntu 17.10 está sendo executada dentro do Virtual Box. A unidade externa está sendo conectada à máquina por meio de um controlador de armazenamento virtual USB que acessa um disco .vmdk apontando para a unidade. A unidade não seria montada sem a opção 'Usar cache de E / S do host' selecionada.

Abaixo estão algumas informações do terminal, incluindo mount e fdisk. Eu mudei para root para pular digitando no sudo para cada comando. Não é assim que eu normalmente corro.

Agradecemos antecipadamente e deixe-me saber se há mais comandos de diagnóstico que eu devo mostrar.

Solução de problemas:

Conecte o disco rígido e use o utilitário 'Disks' para desbloquear a partição, mas não para montá-la. Eu recebo o seguinte (cortando as informações sobre os outros discos):

    root@ubuntu-17-10-vm:~# fdisk -l


    Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 02248FB5-A2E4-487F-8BB3-9F2E3B5E9C7A

    Device     Start        End    Sectors  Size Type
    /dev/sdb1   2048 5860533134 5860531087  2.7T Linux filesystem



    Disk /dev/mapper/luks-3ac27466-39e7-49b9-875c-db8953433731: 2.7 TiB, 3000589819392 bytes, 5860526991 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes

Neste ponto, "mount | grep luks" não retorna nada. Agora, seleciono o botão 'Mount Selected Partiton' no utilitário Disks e tentamos o fdisk e o mount novamente:

    root@ubuntu-17-10-vm:~# fdisk -l
    Disk /dev/sda: 30 GiB, 32212254720 bytes, 62914560 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: dos
    Disk identifier: 0x6afa8f26

    Device     Boot Start      End  Sectors Size Id Type
    /dev/sda1  *     2048 62912511 62910464  30G 83 Linux


    Disk /dev/sdb: 2.7 TiB, 3000592982016 bytes, 5860533168 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes
    Disklabel type: gpt
    Disk identifier: 02248FB5-A2E4-487F-8BB3-9F2E3B5E9C7A

    Device     Start        End    Sectors  Size Type
    /dev/sdb1   2048 5860533134 5860531087  2.7T Linux filesystem


    Disk /dev/mapper/luks-3ac27466-39e7-49b9-875c-db8953433731: 2.7 TiB, 3000589819392 bytes, 5860526991 sectors
    Units: sectors of 1 * 512 = 512 bytes
    Sector size (logical/physical): 512 bytes / 512 bytes
    I/O size (minimum/optimal): 512 bytes / 512 bytes


    root@ubuntu-17-10-vm:~# mount|grep luks
    /dev/mapper/luks-3ac27466-39e7-49b9-875c-db8953433731 on /mnt/3TB type ext4 (rw,nosuid,nodev,relatime,data=ordered,x-gvfs-show)

Eu tento criar um diretório e sou impedido:

    root@ubuntu-17-10-vm:~# cd /mnt/3TB
    root@ubuntu-17-10-vm:/mnt/3TB# mkdir Temp
    mkdir: cannot create directory ‘Temp’: Read-only file system

Em seguida, vamos ver o mount novamente e a partição é somente leitura:

    root@ubuntu-17-10-vm:/mnt/3TB# mount|grep luks
    /dev/mapper/luks-3ac27466-39e7-49b9-875c-db8953433731 on /mnt/3TB type ext4 (ro,nosuid,nodev,relatime,data=ordered,x-gvfs-show)

A entrada fstab para este dispositivo é bastante genérica:

    /dev/disk/by-label/3TB /mnt/3TB auto nosuid,nodev,nofail,x-gvfs-show  0 0

Alguma ideia? Alguma sugestão sobre o que mais copiar / colar aqui para ajudar a identificar o problema?

Edite 29-12 @ Xen2050

Aqui está o texto pertinente do arquivo syslog em vários pontos. Isso ocorre antes que a unidade USB esteja ligada após uma inicialização limpa.

    Dec 29 08:49:20 ubuntu-17-10-vm systemd[1]: dev-disk-by\x2dlabel-3TB.device: Job dev-disk-by\x2dlabel-3TB.device/start timed out.
    Dec 29 08:49:20 ubuntu-17-10-vm systemd[1]: Timed out waiting for device dev-disk-by\x2dlabel-3TB.device.
    Dec 29 08:49:20 ubuntu-17-10-vm systemd[1]: Dependency failed for /mnt/3TB.
    Dec 29 08:49:20 ubuntu-17-10-vm systemd[1]: mnt-3TB.mount: Job mnt-3TB.mount/start failed with result 'dependency'.
    Dec 29 08:49:20 ubuntu-17-10-vm systemd[1]: dev-disk-by\x2dlabel-3TB.device: Job dev-disk-by\x2dlabel-3TB.device/start failed with result 'timeout'.

Não há arquivo dmesg em / var / log

Iniciando minha unidade USB e anexando-a no VB.

    Dec 29 08:59:26 ubuntu-17-10-vm kernel: [ 1021.868287] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
    Dec 29 08:59:26 ubuntu-17-10-vm kernel: [ 1021.888204] usb 2-1: LPM exit latency is zeroed, disabling LPM.
    Dec 29 08:59:26 ubuntu-17-10-vm kernel: [ 1021.888587] usb 2-1: New USB device found, idVendor=80ee, idProduct=0030
    Dec 29 08:59:26 ubuntu-17-10-vm kernel: [ 1021.888589] usb 2-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
    Dec 29 08:59:26 ubuntu-17-10-vm kernel: [ 1021.888591] usb 2-1: Product: USB Harddisk
    Dec 29 08:59:26 ubuntu-17-10-vm kernel: [ 1021.888592] usb 2-1: Manufacturer: VirtualBox
    Dec 29 08:59:26 ubuntu-17-10-vm mtp-probe: checking bus 2, device 2: "/sys/devices/pci0000:00/0000:00:0c.0/usb2/2-1"
    Dec 29 08:59:26 ubuntu-17-10-vm mtp-probe: bus: 2, device: 2 was not an MTP device
    Dec 29 08:59:26 ubuntu-17-10-vm kernel: [ 1022.009260] usb-storage 2-1:1.0: USB Mass Storage device detected
    Dec 29 08:59:26 ubuntu-17-10-vm kernel: [ 1022.009494] scsi host3: usb-storage 2-1:1.0
    Dec 29 08:59:26 ubuntu-17-10-vm kernel: [ 1022.009562] usbcore: registered new interface driver usb-storage
    Dec 29 08:59:26 ubuntu-17-10-vm kernel: [ 1022.050760] usbcore: registered new interface driver uas
    Dec 29 08:59:27 ubuntu-17-10-vm kernel: [ 1023.024461] scsi 3:0:0:0: Direct-Access     VBOX     HARDDISK         1.0  PQ: 0 ANSI: 5
    Dec 29 08:59:27 ubuntu-17-10-vm kernel: [ 1023.024753] sd 3:0:0:0: Attached scsi generic sg2 type 0
    Dec 29 08:59:27 ubuntu-17-10-vm kernel: [ 1023.025237] sd 3:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
    Dec 29 08:59:27 ubuntu-17-10-vm kernel: [ 1023.025563] sd 3:0:0:0: [sdb] 5860533168 512-byte logical blocks: (3.00 TB/2.73 TiB)
    Dec 29 08:59:27 ubuntu-17-10-vm kernel: [ 1023.025843] sd 3:0:0:0: [sdb] Write Protect is off
    Dec 29 08:59:27 ubuntu-17-10-vm kernel: [ 1023.025845] sd 3:0:0:0: [sdb] Mode Sense: 04 00 10 00
    Dec 29 08:59:27 ubuntu-17-10-vm kernel: [ 1023.026128] sd 3:0:0:0: [sdb] Write cache: enabled, read cache: enabled, supports DPO and FUA
    Dec 29 08:59:27 ubuntu-17-10-vm kernel: [ 1023.026780] sd 3:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
    Dec 29 08:59:27 ubuntu-17-10-vm kernel: [ 1023.081040]  sdb: sdb1
    Dec 29 08:59:27 ubuntu-17-10-vm kernel: [ 1023.081977] sd 3:0:0:0: [sdb] Very big device. Trying to use READ CAPACITY(16).
    Dec 29 08:59:27 ubuntu-17-10-vm kernel: [ 1023.083190] sd 3:0:0:0: [sdb] Attached SCSI disk
    Dec 29 08:59:30 ubuntu-17-10-vm gnome-shell[1362]: JS WARNING: [resource:///org/gnome/shell/ui/modalDialog.js 218]: reference to undefined property "GdkX11Screen"

digitando a senha no utilitário Disks (montada automaticamente)

    Dec 29 09:01:01 ubuntu-17-10-vm dbus-daemon[985]: Activating service name='org.gnome.DiskUtility'
    Dec 29 09:01:02 ubuntu-17-10-vm dbus-daemon[985]: Successfully activated service 'org.gnome.DiskUtility'
    Dec 29 09:01:20 ubuntu-17-10-vm kernel: [ 1136.489506] NET: Registered protocol family 38
    Dec 29 09:01:20 ubuntu-17-10-vm systemd[1]: Mounting /mnt/3TB...
    Dec 29 09:01:20 ubuntu-17-10-vm udisksd[664]: Unlocked LUKS device /dev/sdb1 as /dev/dm-0
    Dec 29 09:01:21 ubuntu-17-10-vm kernel: [ 1136.871036] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    Dec 29 09:01:21 ubuntu-17-10-vm kernel: [ 1136.871039] sd 3:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] 
    Dec 29 09:01:21 ubuntu-17-10-vm kernel: [ 1136.871040] sd 3:0:0:0: [sdb] tag#0 Add. Sense: Write error
    Dec 29 09:01:21 ubuntu-17-10-vm kernel: [ 1136.871042] sd 3:0:0:0: [sdb] tag#0 CDB: Write(16) 8a 08 00 00 00 00 00 00 18 00 00 00 00 08 00 00
    Dec 29 09:01:21 ubuntu-17-10-vm kernel: [ 1136.871043] print_req_error: I/O error, dev sdb, sector 6144
    Dec 29 09:01:21 ubuntu-17-10-vm kernel: [ 1136.871052] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
    Dec 29 09:01:21 ubuntu-17-10-vm kernel: [ 1136.889074] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
    Dec 29 09:01:21 ubuntu-17-10-vm systemd[1]: Mounted /mnt/3TB.
    Dec 29 09:01:21 ubuntu-17-10-vm dbus-daemon[985]: Activating service name='org.gnome.Shell.HotplugSniffer'
    Dec 29 09:01:21 ubuntu-17-10-vm dbus-daemon[985]: Successfully activated service 'org.gnome.Shell.HotplugSniffer'
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.103798] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.103801] sd 3:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] 
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.103802] sd 3:0:0:0: [sdb] tag#0 Add. Sense: Write error
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.103804] sd 3:0:0:0: [sdb] tag#0 CDB: Write(16) 8a 00 00 00 00 00 ae 84 18 00 00 00 00 08 00 00
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.103806] print_req_error: I/O error, dev sdb, sector 2927892480
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.103815] Buffer I/O error on dev dm-0, logical block 365985792, lost sync page write
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.103869] JBD2: Error -5 detected when updating journal superblock for dm-0-8.
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.103873] Aborting journal on device dm-0-8.
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.187267] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.187269] sd 3:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] 
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.187271] sd 3:0:0:0: [sdb] tag#0 Add. Sense: Write error
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.187273] sd 3:0:0:0: [sdb] tag#0 CDB: Write(16) 8a 08 00 00 00 00 ae 84 18 00 00 00 00 08 00 00
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.187274] print_req_error: I/O error, dev sdb, sector 2927892480
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.187282] Buffer I/O error on dev dm-0, logical block 365985792, lost sync page write
    Dec 29 09:01:27 ubuntu-17-10-vm kernel: [ 1143.187292] JBD2: Error -5 detected when updating journal superblock for dm-0-8.

Desmontando e re-montando a partição

    Dec 29 09:07:00 ubuntu-17-10-vm kernel: [ 1476.484779] EXT4-fs (dm-0): previous I/O error to superblock detected
    Dec 29 09:07:00 ubuntu-17-10-vm kernel: [ 1476.572332] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    Dec 29 09:07:00 ubuntu-17-10-vm kernel: [ 1476.572334] sd 3:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] 
    Dec 29 09:07:00 ubuntu-17-10-vm kernel: [ 1476.572336] sd 3:0:0:0: [sdb] tag#0 Add. Sense: Write error
    Dec 29 09:07:00 ubuntu-17-10-vm kernel: [ 1476.572338] sd 3:0:0:0: [sdb] tag#0 CDB: Write(16) 8a 08 00 00 00 00 00 00 18 00 00 00 00 08 00 00
    Dec 29 09:07:00 ubuntu-17-10-vm kernel: [ 1476.572339] print_req_error: I/O error, dev sdb, sector 6144
    Dec 29 09:07:00 ubuntu-17-10-vm kernel: [ 1476.572349] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
    Dec 29 09:07:00 ubuntu-17-10-vm udisksd[664]: Unmounted /dev/dm-0 on behalf of uid 1000
    Dec 29 09:07:04 ubuntu-17-10-vm kernel: [ 1479.784459] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    Dec 29 09:07:04 ubuntu-17-10-vm kernel: [ 1479.784462] sd 3:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] 
    Dec 29 09:07:04 ubuntu-17-10-vm kernel: [ 1479.784464] sd 3:0:0:0: [sdb] tag#0 Add. Sense: Write error
    Dec 29 09:07:04 ubuntu-17-10-vm kernel: [ 1479.784466] sd 3:0:0:0: [sdb] tag#0 CDB: Write(16) 8a 08 00 00 00 00 00 00 18 00 00 00 00 08 00 00
    Dec 29 09:07:04 ubuntu-17-10-vm kernel: [ 1479.784468] print_req_error: I/O error, dev sdb, sector 6144
    Dec 29 09:07:04 ubuntu-17-10-vm kernel: [ 1479.784478] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
    Dec 29 09:07:04 ubuntu-17-10-vm kernel: [ 1479.812154] EXT4-fs (dm-0): mounted filesystem with ordered data mode. Opts: (null)
    Dec 29 09:07:04 ubuntu-17-10-vm udisksd[664]: Mounted /dev/dm-0 (system) at /mnt/3TB on behalf of uid 1000
    Dec 29 09:07:04 ubuntu-17-10-vm dbus-daemon[985]: Activating service name='org.gnome.Shell.HotplugSniffer'
    Dec 29 09:07:04 ubuntu-17-10-vm dbus-daemon[985]: Successfully activated service 'org.gnome.Shell.HotplugSniffer'
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.081405] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.081409] sd 3:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] 
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.081411] sd 3:0:0:0: [sdb] tag#0 Add. Sense: Write error
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.081413] sd 3:0:0:0: [sdb] tag#0 CDB: Write(16) 8a 00 00 00 00 00 ae 84 18 00 00 00 00 08 00 00
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.081415] print_req_error: I/O error, dev sdb, sector 2927892480
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.081437] Buffer I/O error on dev dm-0, logical block 365985792, lost sync page write
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.081500] JBD2: Error -5 detected when updating journal superblock for dm-0-8.
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.081503] Aborting journal on device dm-0-8.
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.186841] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.186844] sd 3:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] 
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.186845] sd 3:0:0:0: [sdb] tag#0 Add. Sense: Write error
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.186847] sd 3:0:0:0: [sdb] tag#0 CDB: Write(16) 8a 08 00 00 00 00 ae 84 18 00 00 00 00 08 00 00
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.186848] print_req_error: I/O error, dev sdb, sector 2927892480
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.186857] Buffer I/O error on dev dm-0, logical block 365985792, lost sync page write
    Dec 29 09:07:10 ubuntu-17-10-vm kernel: [ 1486.186885] JBD2: Error -5 detected when updating journal superblock for dm-0-8.

abra a janela de comando, cd / mnt / 3TB, sudo mkdir temp (que falha)

    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.780629] EXT4-fs (dm-0): previous I/O error to superblock detected
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.880404] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.880407] sd 3:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] 
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.880409] sd 3:0:0:0: [sdb] tag#0 Add. Sense: Write error
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.880411] sd 3:0:0:0: [sdb] tag#0 CDB: Write(16) 8a 08 00 00 00 00 00 00 18 00 00 00 00 08 00 00
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.880413] print_req_error: I/O error, dev sdb, sector 6144
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.880423] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.880462] EXT4-fs error (device dm-0): ext4_journal_check_start:60: Detected aborted journal
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.880465] EXT4-fs (dm-0): Remounting filesystem read-only
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.880468] EXT4-fs (dm-0): previous I/O error to superblock detected
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.987581] sd 3:0:0:0: [sdb] tag#0 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_SENSE
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.987584] sd 3:0:0:0: [sdb] tag#0 Sense Key : Medium Error [current] 
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.987586] sd 3:0:0:0: [sdb] tag#0 Add. Sense: Write error
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.987589] sd 3:0:0:0: [sdb] tag#0 CDB: Write(16) 8a 08 00 00 00 00 00 00 18 00 00 00 00 08 00 00
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.987591] print_req_error: I/O error, dev sdb, sector 6144
    Dec 29 09:08:51 ubuntu-17-10-vm kernel: [ 1586.987600] Buffer I/O error on dev dm-0, logical block 0, lost sync page write
    
por Wick 28.12.2017 / 21:21

0 respostas