Created
July 31, 2018 04:25
-
-
Save henriqueutsch/2d6de827a5e28e34e95b67e3c19a7c3d to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#Compilar netatalk | |
Não precisa, de apt-get install netatalk | |
#Montagem de hd erro1 | |
Instalar hfutils | |
#Montagem de hd em read only | |
Reparar HD | |
sudo fsck.hfsplus /dev/sdXY | |
#Rede lenta para acessar | |
Montar hd leitura e escrita | |
#Problema de permissão - Mesmo colocando usuario e senha o Time Machine recusa | |
sudo chmod 777 /mnt/TimeMachine | |
https://discussions.apple.com/thread/1580562?tstart=0 | |
#Volume não monta | |
http://askubuntu.com/questions/332315/how-to-read-and-write-hfs-journaled-external-hdd-in-ubuntu-without-access-to-os | |
sudo mount -t hfsplus -o force,rw /dev/sdx# /media/mntpoint | |
#Se não der para reparar ou o Disk Utility nao reconhecer tem que baixar o Disk Warrior e reparar | |
http://unix.stackexchange.com/questions/109673/how-to-repair-a-corrupted-hfs-partition-from-a-damaged-hard-disk | |
https://thepiratebay.org/torrent/12206443/Disk_Warrior_5.0_[DiskWarrior] | |
#O disco deve estar montado para leitura e escrita | |
Read only deixa a rede lenta | |
http://apple.stackexchange.com/questions/92979/ | |
how-to-remount-an-internal-drive-as-read-write-in-mountain-lion | |
#Permissao acesso | |
http://superuser.com/questions/516494/permission-issue-accessing-netatalk-share-on-os-x | |
#Diretórios não aparecem | |
sudo nano /etc/netatalk/AppleVolumes.default | |
#Erro sudo umount /dev/sda2 | |
umount: /media/Backup: target is busy | |
(In some cases useful info about processes that | |
use the device is found by lsof(8) or fuser(1).) | |
sudo umount -l /dev/sda2 | |
#Erro sudo fsck.hfsplus /dev/sda2 | |
sudo fsck.hfsplus -drfy /dev/sda2 | |
https://apple.stackexchange.com/questions/81093/what-are-next-steps-when-fsck-reports-could-not-be-repaired-after-3-attempts |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment