Eu tenho um problema ao escrever alterações em arquivos / etc / fstab que tornam o sistema somente leitura.
Eu tenho duas unidades no meu laptop - SSD e HDD. Eu li muitas opiniões sobre otimização de SSD, alguém diz que hoje em dia não é necessário se preocupar, mas eu enfrentei um problema ao tentar otimizar o uso de SSDs. Adicionar quaisquer opções de otimização às partições no fstab torna / somente leitura após a reinicialização do sistema.
Aqui está o meu arquivo 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>
# / was on /dev/sda2 during installation
UUID=b6ebbe28-8654-4919-8094-5eee18954247 / ext4 discard, noatime, errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=A5F0-7D4E /boot/efi vfat umask=0077 0 1
# /home was on /dev/sda4 during installation
UUID=1e4e6052-c8ba-4548-8ffd-457a4bc460bf /home ext4 discard, noatime, defaults 0 2
# /var was on /dev/sdb1 during installation
UUID=d1fa1a62-eca1-4e13-8bf6-f30300a01cab /var ext4 defaults 0 2
# swap was on /dev/sda3 during installation
UUID=69c38a83-596d-4ad1-ab87-599445c4e910 none swap sw 0 0
# moving temporary files from SSD to RAM
tmpfs /tmp tmpfs defaults 0 0
#tmpfs /var/tmp tmpfs defaults 0 0
#tmpfs /var/lock tmpfs defaults 0 0
#tmpfs /var/spool/postfix tmpfs defaults 0 0
UUID="ec529d46-81de-43e5-ad88-d50818f93421" /sghdd ext4 defaults 0 2
# mount MEDIA partition as sghdd folder
UUID="ec529d46-81de-43e5-ad88-d50818f93421" /sghdd ext4 defaults 0 2
# moving SSD/home folders to MEDIA
/sghdd/Downloads /home/ornichola/Downloads none bind 0 0
/sghdd/Public /home/ornichola/Public none bind 0 0
/sghdd/Videos /home/ornichola/Videos none bind 0 0
/sghdd/Pictures /home/ornichola/Pictures none bind 0 0
/sghdd/Music /home/ornichola/Music none bind 0 0
Com a adição de qualquer opção (discard, noatime, relatime) a / dev / sda2 e / dev / sda4, o problema ocorre após a reinicialização do sistema. Todas as tentativas de usar o aptitude são bloqueadas de acordo com o sistema de arquivos somente leitura.
Para evitar isso, eu devo inicializar a partir do liveCD, montar meu / partition e remover opções adicionadas do fstab. Depois disso eu executo no sistema liveCD:
sudo mount -o remount,rw /dev/sda2 /
reinicialize o sistema instalado, execute:
sudo fsck -n -f
e somente depois eu posso usar o aptitude novamente.
O principal objetivo de alterar o fstab é adicionar opções de descartar, relatime, nodiratime (ou noatime) às parções de SSD. Por que o sistema está indo para somente leitura?
Saída de blkid :
ornichola@silver:~$ sudo blkid
/dev/sda1: LABEL="EFIBOOT" UUID="A5F0-7D4E" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="9a3525d1-9e84-4a06-84d2-2b96818ac1b8"
/dev/sda2: UUID="b6ebbe28-8654-4919-8094-5eee18954247" TYPE="ext4" PARTUUID="a5cd0868-f118-40a5-9ffd-09282504722d"
/dev/sda3: UUID="69c38a83-596d-4ad1-ab87-599445c4e910" TYPE="swap" PARTUUID="9199a9cb-9656-489f-83ef-4fe2800e6706"
/dev/sda4: UUID="1e4e6052-c8ba-4548-8ffd-457a4bc460bf" TYPE="ext4" PARTUUID="4bf6d060-a7bf-491d-ae53-da80b13c838d"
/dev/sdb1: UUID="d1fa1a62-eca1-4e13-8bf6-f30300a01cab" TYPE="ext4" PARTUUID="6c06b7b5-67dd-4b39-9f63-58c3876b9cfb"
/dev/sdb2: LABEL="MEDIA" UUID="ec529d46-81de-43e5-ad88-d50818f93421" TYPE="ext4" PARTUUID="869b4d14-7a3b-4eb3-b784-e6fbe3db5514"
ornichola@silver:~$
e saída de fsck enquanto o sistema é somente leitura e opções adicionadas ao fstab:
ornichola@silver:~$ sudo fsck -n -f
fsck from util-linux 2.27.1
fsck: /etc/fstab: parse error at line 9 -- ignore
fsck: /etc/fstab: parse error at line 13 -- ignore
fsck.fat 3.0.28 (2015-05-16)
0x41: Dirty bit is set. Fs was not properly unmounted and some data may be corrupt.
Automatically removing dirty bit.
Leaving filesystem unchanged.
/dev/sda1: 9 files, 870/130812 clusters
e2fsck 1.42.13 (17-May-2015)
Warning! /dev/sdb1 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong (4853291, counted=4853223).
Fix? no
Free inodes count wrong (1301362, counted=1301355).
Fix? no
/dev/sdb1: 9358/1310720 files (0.4% non-contiguous), 389589/5242880 blocks
e2fsck 1.42.13 (17-May-2015)
Warning! /dev/sdb2 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
MEDIA: 16/59744256 files (0.0% non-contiguous), 3800856/238947328 blocks
e2fsck 1.42.13 (17-May-2015)
Warning! /dev/sdb2 is mounted.
Warning: skipping journal recovery because doing a read-only filesystem check.
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
MEDIA: 16/59744256 files (0.0% non-contiguous), 3800856/238947328 blocks
ornichola@silver:~$