O usuário não pode montar discos após atualizar para o Saucy

Question

Eu fiz o upgrade para o Saucy e não consigo mais montar nenhum disco, porque não tenho permissão:

Eupossomontarodiscocommount,masissonãoérealmenteumasolução...

Comopossoativaramontagemparaousuárionovamente?

blkid

/dev/sda5:UUID="fd5c349d-683e-4958-9fd2-bd825f10b471" TYPE="ext4" 
/dev/sdb1: UUID="4e0ae3da-4001-43c7-99b4-95112b9177fd" TYPE="ext4" 
/dev/sdc1: LABEL="MU-3-466G-info" UUID="6c680a34-5392-4cff-8f9a-ac9c906db75f" TYPE="ext4" 
/dev/sdc2: UUID="764d42e6-66af-413c-9148-2709c8b084c1" TYPE="crypto_LUKS" 

fdisk -l

Disk /dev/sda: 320.1 GB, 320072933376 bytes
255 heads, 63 sectors/track, 38913 cylinders, total 625142448 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disk identifier: 0x0719ee6e

   Device Boot      Start         End      Blocks   Id  System
/dev/sda2            2046   593893375   296945665    5  Extended
Partition 2 does not start on physical sector boundary.
/dev/sda5            2048   554829823   277413888   83  Linux

Disk /dev/sdb: 30.0 GB, 30016659456 bytes
255 heads, 63 sectors/track, 3649 cylinders, total 58626288 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
Disk identifier: 0x000e8129

   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1   *        2048    58626047    29312000   83  Linux

Disk /dev/sdc: 500.1 GB, 500107859968 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773164 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
Disk identifier: 0x0007fa35

   Device Boot      Start         End      Blocks   Id  System
/dev/sdc1              63      208844      104391   83  Linux
/dev/sdc2          208845   976768064   488279610   83  Linux

cat /etc/fstab

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
proc            /proc           proc    nodev,noexec,nosuid 0       0
# / was on /dev/sdb1 during installation
UUID=4e0ae3da-4001-43c7-99b4-95112b9177fd /               ext4    discard,errors=remount-ro 0       1
# /home was on /dev/sda5 during installation
UUID=fd5c349d-683e-4958-9fd2-bd825f10b471 /home           ext4    defaults        0       2
# /tmp was on /dev/sda7 during installation
#UUID=c0e28121-6b95-459a-8f88-3e9ee11292aa /tmp            ext4    defaults        0       2
# /var was on /dev/sda6 during installation
#UUID=9eaadf4b-95ef-40d3-860f-48e6f4ea9186 /var            ext4    defaults        0       2
# swap was on /dev/sda1 during installation
#UUID=e2a27ad7-d887-4fe7-831f-bbde2e4e3056 none            swap    sw              0       0

#/dev/mapper/cryptswap1 none swap sw 0 0

    

Answer 1

Para o DM que você usa (kdm, gdm, lightdm etc.), faça o seguinte:

1. Anexe o seguinte ao topo do /etc/pam.d/your_dm_file :

   session required pam_loginuid.so
   session required pam_systemd.so
   

2. Logout, Reiniciar X, Login

3. Verifique se tudo funciona
4. Remova a correção aplicada na etapa 1.
5. Fazer logout, Reiniciar X, Fazer login
6. Verifique se tudo ainda está funcionando!

Essa correção chamada (etapa 1) pode ser removida quando você fizer login e verificar se você tem um sistema em funcionamento. Aparentemente, permite que o sistema atualizado conclua algum processo que corrija o problema subjacente. Uma vez feito (após um login admin?), A correção pode ser removida.

Ele também esclareceu todos os relatórios de falhas que recebi diretamente após o login.