Consegui resolver, a solução foi ter baixado a mesma versão do versão do Debian, dar boot pelo DVD e entrar no modo rescue, eu achei bem intuitivo aquilo, eu pensei que era pra digitar linha de comando, mas não foi assim, o modo rescue restaura com criptografia e tudo, se for ver nem era preciso usar a live cd, o grub foi restaurado pro estado que estava antes de instalar o Windows 10, ou seja aparecia no grub o Windows 7, mas nada que um update-grub no Debian não resolvesse, está tudo ok agora.
Que alivio em saber que recuperei meu sistema, e meu windows está atualizado, obrigado a todos por tudo e desculpe o incomodo. Pra quem pode sofrer com isso, restaurar no modo rescue tem que ter noção de qual é a partição raiz, qual partição instalar o grub e por ai vai, a parte da live cd me ajudou um pouco a pegar a noção disso. Em 4 de setembro de 2017 03:20, Luiz Carlos <lc94...@gmail.com> escreveu: > O Debian que estou não é live cd, é só pra ver o lance de rescue, mas será > possível restaurar com partições criptografadas? > > Em 4 de setembro de 2017 03:16, Luiz Carlos <lc94...@gmail.com> escreveu: > >> Estou aqui baixando uma distro do Debian equivalente a minha versão, >> vamos ver no que vai dar. >> Será que danifiquei a minha partição do Linux? Bem, eu consigo montar a >> raiz e a home, n sei se tenho esperanças de arrumar. >> >> Em 4 de setembro de 2017 02:39, Linux - Junior Polegato < >> li...@juniorpolegato.com.br> escreveu: >> >>> Olá! >>> >>> Seguindo os passos que passei, antes do grub-install e update-grub, >>> tente iniciar os serviços de lvm que estão em /etc/rc5.d, deve ter um >>> .service que deve funcionar. >>> >>> Mais um ponto, aconselho utilizar o CD de instalação do Debian, >>> iniciando em modo de recuperação ou instalação até o ponto em que são >>> reconhecidas todas as partições do HD, então no Shell que abrir >>> (Ctrl+Alt+F2) siga os passos que passei, lembrando ser importante que o >>> kernel do instalador seja da mesma arquitetura do instalado no HD, i386 ou >>> amd64, se for versão próxima ou igual, melhor ainda. >>> >>> []'s >>> >>> Junior Polegato >>> >>> Em 3 de set de 2017 11:36 PM, "Luiz Carlos" <lc94...@gmail.com> >>> escreveu: >>> >>>> # systemctl start lvm2-lvmetad.socket >>>> Running in chroot, ignoring request. >>>> >>>> >>>> Em 4 de setembro de 2017 02:32, <jmhenri...@yahoo.com.br> escreveu: >>>> >>>>> Experimenta rodar os mesmos comandos, só que após dar o chroot, inicie >>>>> os serviços de lvmetad que estão faltando de acordo com a sua mensagem de >>>>> erro: >>>>> >>>>> >>>>> systemctl start lvm2-lvmetad.service >>>>> systemctl start lvm2-lvmetad.socket >>>>> >>>>> E só daí o grub-install ou updategrub >>>>> >>>>> Faz isso com e sem o GRUB_ENABLE_CRYPTODISK habilitado, só por via >>>>> das dúvidas, o log disse que precisava disso habilitado, e que o lvmetad >>>>> não foi contactado. Deve resolver. >>>>> >>>>> Abracos >>>>> >>>>> Henry >>>>> >>>>> >>>>> >>>>> Enviado do meu smartphone BlackBerry 10. >>>>> *De: *Luiz Carlos >>>>> *Enviada: *domingo, 3 de setembro de 2017 21:38 >>>>> *Para: *DUP >>>>> *Assunto: *Re: Erro ao recuperar grub de um Debian com LVM >>>>> Criptografado. >>>>> >>>>> Henrique e Junior, executei os seguintes comandos: >>>>> mint mint # modprobe dm-crypt >>>>> mint mint # cryptsetup luksOpen /dev/sda5 linux >>>>> Enter passphrase for /dev/sda5: >>>>> mint mint # vgscan >>>>> Reading all physical volumes. This may take a while... >>>>> Found volume group "lvmc" using metadata type lvm2 >>>>> mint mint # lvscan >>>>> ACTIVE '/dev/lvmc/swap' [1.86 GiB] inherit >>>>> ACTIVE '/dev/lvmc/root' [37.25 GiB] inherit >>>>> ACTIVE '/dev/lvmc/home' [327.60 GiB] inherit >>>>> mint mint # mkdir /media/linux >>>>> mint mint # mount /dev/lvmc/root /media/linux/ >>>>> mint mint # mount -o bind /dev/ /media/linux/dev >>>>> mint mint # mount -o bind /proc/ /media/linux/proc >>>>> mint mint # chroot /media/linux /bin/bash >>>>> root@mint:/# grub-install /dev/sda >>>>> Installing for i386-pc platform. >>>>> Failed to find sysfs mount point >>>>> WARNING: Failed to connect to lvmetad. Falling back to device >>>>> scanning. >>>>> dev/block/252:2/holders/: opendir failed: Not a directory >>>>> dev/block/252:1/holders/: opendir failed: Not a directory >>>>> dev/block/252:3/holders/: opendir failed: Not a directory >>>>> dev/block/252:0/holders/: opendir failed: Not a directory >>>>> dev/block/8:33/holders/: opendir failed: Not a directory >>>>> dev/block/8:32/holders/: opendir failed: Not a directory >>>>> dev/block/8:16/holders/: opendir failed: Not a directory >>>>> dev/block/8:3/holders/: opendir failed: Not a directory >>>>> dev/block/8:5/holders/: opendir failed: Not a directory >>>>> dev/block/11:0/holders/: opendir failed: Not a directory >>>>> dev/block/8:1/holders/: opendir failed: Not a directory >>>>> dev/block/8:2/holders/: opendir failed: Not a directory >>>>> dev/block/8:4/holders/: opendir failed: Not a directory >>>>> dev/block/8:0/holders/: opendir failed: Not a directory >>>>> dev/block/1:7/holders/: opendir failed: Not a directory >>>>> dev/block/1:6/holders/: opendir failed: Not a directory >>>>> dev/block/1:9/holders/: opendir failed: Not a directory >>>>> dev/block/1:8/holders/: opendir failed: Not a directory >>>>> dev/block/1:5/holders/: opendir failed: Not a directory >>>>> dev/block/1:4/holders/: opendir failed: Not a directory >>>>> dev/block/1:10/holders/: opendir failed: Not a directory >>>>> dev/block/1:11/holders/: opendir failed: Not a directory >>>>> dev/block/1:3/holders/: opendir failed: Not a directory >>>>> dev/block/1:15/holders/: opendir failed: Not a directory >>>>> dev/block/1:2/holders/: opendir failed: Not a directory >>>>> dev/block/1:13/holders/: opendir failed: Not a directory >>>>> dev/block/1:14/holders/: opendir failed: Not a directory >>>>> dev/block/1:12/holders/: opendir failed: Not a directory >>>>> dev/block/1:0/holders/: opendir failed: Not a directory >>>>> dev/block/1:1/holders/: opendir failed: Not a directory >>>>> dev/block/7:0/holders/: opendir failed: Not a directory >>>>> dev/block/7:7/holders/: opendir failed: Not a directory >>>>> dev/block/7:1/holders/: opendir failed: Not a directory >>>>> dev/block/7:6/holders/: opendir failed: Not a directory >>>>> dev/block/7:5/holders/: opendir failed: Not a directory >>>>> dev/block/7:3/holders/: opendir failed: Not a directory >>>>> dev/block/7:4/holders/: opendir failed: Not a directory >>>>> dev/block/7:2/holders/: opendir failed: Not a directory >>>>> dev/block/252:2/holders/: opendir failed: Not a directory >>>>> dev/block/252:1/holders/: opendir failed: Not a directory >>>>> dev/block/252:3/holders/: opendir failed: Not a directory >>>>> dev/block/252:0/holders/: opendir failed: Not a directory >>>>> dev/block/8:33/holders/: opendir failed: Not a directory >>>>> dev/block/8:32/holders/: opendir failed: Not a directory >>>>> dev/block/8:16/holders/: opendir failed: Not a directory >>>>> dev/block/8:3/holders/: opendir failed: Not a directory >>>>> dev/block/8:5/holders/: opendir failed: Not a directory >>>>> dev/block/11:0/holders/: opendir failed: Not a directory >>>>> dev/block/8:1/holders/: opendir failed: Not a directory >>>>> dev/block/8:2/holders/: opendir failed: Not a directory >>>>> dev/block/8:4/holders/: opendir failed: Not a directory >>>>> dev/block/8:0/holders/: opendir failed: Not a directory >>>>> dev/block/1:7/holders/: opendir failed: Not a directory >>>>> dev/block/1:6/holders/: opendir failed: Not a directory >>>>> dev/block/1:9/holders/: opendir failed: Not a directory >>>>> dev/block/1:8/holders/: opendir failed: Not a directory >>>>> dev/block/1:5/holders/: opendir failed: Not a directory >>>>> dev/block/1:4/holders/: opendir failed: Not a directory >>>>> dev/block/1:10/holders/: opendir failed: Not a directory >>>>> dev/block/1:11/holders/: opendir failed: Not a directory >>>>> dev/block/1:3/holders/: opendir failed: Not a directory >>>>> dev/block/1:15/holders/: opendir failed: Not a directory >>>>> dev/block/1:2/holders/: opendir failed: Not a directory >>>>> dev/block/1:13/holders/: opendir failed: Not a directory >>>>> dev/block/1:14/holders/: opendir failed: Not a directory >>>>> dev/block/1:12/holders/: opendir failed: Not a directory >>>>> dev/block/1:0/holders/: opendir failed: Not a directory >>>>> dev/block/1:1/holders/: opendir failed: Not a directory >>>>> dev/block/7:0/holders/: opendir failed: Not a directory >>>>> dev/block/7:7/holders/: opendir failed: Not a directory >>>>> dev/block/7:1/holders/: opendir failed: Not a directory >>>>> dev/block/7:6/holders/: opendir failed: Not a directory >>>>> dev/block/7:5/holders/: opendir failed: Not a directory >>>>> dev/block/7:3/holders/: opendir failed: Not a directory >>>>> dev/block/7:4/holders/: opendir failed: Not a directory >>>>> dev/block/7:2/holders/: opendir failed: Not a directory >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> Failed to find sysfs mount point >>>>> WARNING: Failed to connect to lvmetad. Falling back to device >>>>> scanning. >>>>> dev/block/252:2/holders/: opendir failed: Not a directory >>>>> dev/block/252:1/holders/: opendir failed: Not a directory >>>>> dev/block/252:3/holders/: opendir failed: Not a directory >>>>> dev/block/252:0/holders/: opendir failed: Not a directory >>>>> dev/block/8:33/holders/: opendir failed: Not a directory >>>>> dev/block/8:32/holders/: opendir failed: Not a directory >>>>> dev/block/8:16/holders/: opendir failed: Not a directory >>>>> dev/block/8:3/holders/: opendir failed: Not a directory >>>>> dev/block/8:5/holders/: opendir failed: Not a directory >>>>> dev/block/11:0/holders/: opendir failed: Not a directory >>>>> dev/block/8:1/holders/: opendir failed: Not a directory >>>>> dev/block/8:2/holders/: opendir failed: Not a directory >>>>> dev/block/8:4/holders/: opendir failed: Not a directory >>>>> dev/block/8:0/holders/: opendir failed: Not a directory >>>>> dev/block/1:7/holders/: opendir failed: Not a directory >>>>> dev/block/1:6/holders/: opendir failed: Not a directory >>>>> dev/block/1:9/holders/: opendir failed: Not a directory >>>>> dev/block/1:8/holders/: opendir failed: Not a directory >>>>> dev/block/1:5/holders/: opendir failed: Not a directory >>>>> dev/block/1:4/holders/: opendir failed: Not a directory >>>>> dev/block/1:10/holders/: opendir failed: Not a directory >>>>> dev/block/1:11/holders/: opendir failed: Not a directory >>>>> dev/block/1:3/holders/: opendir failed: Not a directory >>>>> dev/block/1:15/holders/: opendir failed: Not a directory >>>>> dev/block/1:2/holders/: opendir failed: Not a directory >>>>> dev/block/1:13/holders/: opendir failed: Not a directory >>>>> dev/block/1:14/holders/: opendir failed: Not a directory >>>>> dev/block/1:12/holders/: opendir failed: Not a directory >>>>> dev/block/1:0/holders/: opendir failed: Not a directory >>>>> dev/block/1:1/holders/: opendir failed: Not a directory >>>>> dev/block/7:0/holders/: opendir failed: Not a directory >>>>> dev/block/7:7/holders/: opendir failed: Not a directory >>>>> dev/block/7:1/holders/: opendir failed: Not a directory >>>>> dev/block/7:6/holders/: opendir failed: Not a directory >>>>> dev/block/7:5/holders/: opendir failed: Not a directory >>>>> dev/block/7:3/holders/: opendir failed: Not a directory >>>>> dev/block/7:4/holders/: opendir failed: Not a directory >>>>> dev/block/7:2/holders/: opendir failed: Not a directory >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> device node not found >>>>> grub-install: error: attempt to install to encrypted disk without >>>>> cryptodisk enabled. Set `GRUB_ENABLE_CRYPTODISK=y' in file >>>>> `/etc/default/grub'. >>>>> root@mint:/# >>>>> >>>>> >>>>> Acabou não dando certo. >>>>> >>>>> Em 3 de setembro de 2017 23:07, <jmhenri...@yahoo.com.br> escreveu: >>>>> >>>>>> >>>>>> Olá, boa noite! >>>>>> >>>>>> Antes de dar o chroot, vc precisa: >>>>>> 1 - abrir a partição criptografada (vi que vc fez isso) >>>>>> 2 - verificar se o seu livecd tem o lvm instalado, se não tiver, >>>>>> instale >>>>>> 3 - ativar o lvm com vgscan e verificar com lvscan ; >>>>>> 4 - montar o raiz do lvm : >>>>>> mount /dev/mapper/seuraizlvm /mnt/suafakeroot >>>>>> 5 - montar o proc e o dev com : >>>>>> mount -o bind /dev/ /mnt/suafakeroot/dev >>>>>> mount -o bind /proc/ /mnt/suafakeroot/proc >>>>>> Só daí dar o chroot /mnt/suafakeroot, e instalar o grub normalmente. >>>>>> >>>>>> Deve funcionar sem maiores problemas. >>>>>> >>>>>> Abracos >>>>>> >>>>>> Henry >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> Enviado do meu smartphone BlackBerry 10. >>>>>> *De: *Luiz Carlos >>>>>> *Enviada: *domingo, 3 de setembro de 2017 18:47 >>>>>> *Para: *DUP >>>>>> *Assunto: *Re: Erro ao recuperar grub de um Debian com LVM >>>>>> Criptografado. >>>>>> >>>>>> # mount boot >>>>>> mount: can't find UUID=e7d99f42-7b2a-4afb-9a4a-009003c9f447 >>>>>> >>>>>> Ta foda. >>>>>> >>>>>> Em 3 de setembro de 2017 21:39, Luiz Carlos <lc94...@gmail.com> >>>>>> escreveu: >>>>>> >>>>>>> É computador, aqui eu estou tentando novamente: >>>>>>> root@mint:/# grub-install /dev/sda >>>>>>> Installing for i386-pc platform. >>>>>>> grub-install: error: cannot find a device for /boot/grub (is /dev >>>>>>> mounted?). >>>>>>> root@mint:/# mount /dev/sda2 /boot >>>>>>> mount: /boot: mount failed: Unknown error -1 >>>>>>> root@mint:/# mount /dev/sda2 /boot/ >>>>>>> mount: /boot: mount failed: Unknown error -1 >>>>>>> root@mint:/# mount /dev/sda2 /boot/ >>>>>>> mount: /boot: mount failed: Unknown error -1 >>>>>>> root@mint:/# >>>>>>> root@mint:/# mount /dev/sda2 /boot/ >>>>>>> mount: /boot: mount failed: Unknown error -1 >>>>>>> >>>>>>> >>>>>>> Em 3 de setembro de 2017 21:36, Rodolfo <rof20...@gmail.com> >>>>>>> escreveu: >>>>>>> >>>>>>>> Uma pergunta, é computador ou notebook? é novo? >>>>>>>> >>>>>>>> Tipo, quando comprei meu notebook pesquisei bem sobre a dificuldade >>>>>>>> de usar linux nele, porque justamente não queria ter problemas, eu >>>>>>>> decidi >>>>>>>> comprar um notebook que fosse compatível com linux(o que na minha >>>>>>>> opinião >>>>>>>> nem deveria existir, pra mim qualquer computador/notebook tem que ser >>>>>>>> compatível com qualquer sistema, na prática parece que isso não >>>>>>>> acontece). >>>>>>>> Enfim, dê uma pesquisada sobre isso também. >>>>>>>> >>>>>>>> Em 3 de setembro de 2017 17:28, Luiz Carlos <lc94...@gmail.com> >>>>>>>> escreveu: >>>>>>>> >>>>>>>>> A droga do Seven estava uma merda que tinha vezes que não >>>>>>>>> reconhecia o mouse e precisava ficar reiniciando toda pra isso >>>>>>>>> resolver, >>>>>>>>> por isso que tentei instalar o 10. >>>>>>>>> >>>>>>>>> Em 3 de setembro de 2017 21:27, Rodolfo <rof20...@gmail.com> >>>>>>>>> escreveu: >>>>>>>>> >>>>>>>>>> Eu uso aqui dual boot windows 7 + debian 9, só tenho windows pra >>>>>>>>>> jogar alguns jogos, hehehe. >>>>>>>>>> >>>>>>>>>> Em 3 de setembro de 2017 17:25, Luiz Carlos <lc94...@gmail.com> >>>>>>>>>> escreveu: >>>>>>>>>> >>>>>>>>>>> A real é que a Microsoft é um lixo em fazer esse tipo de >>>>>>>>>>> prática, pior que vou ter que instalar o Linux do zero pra ver se >>>>>>>>>>> resolve, >>>>>>>>>>> se não detectar o Windows 10, eu vou ter que voltar aquele dual >>>>>>>>>>> boot com o >>>>>>>>>>> seven como era antes. >>>>>>>>>>> Desativei a hibernação tbm e nada. >>>>>>>>>>> >>>>>>>>>>> Em 3 de setembro de 2017 20:51, Rodolfo <rof20...@gmail.com> >>>>>>>>>>> escreveu: >>>>>>>>>>> >>>>>>>>>>>> Isso, eu desativo esse secureboot. Bom, no seu caso você usa >>>>>>>>>>>> LVM, realmente pode ser algo que não conheço. >>>>>>>>>>>> >>>>>>>>>>>> Em 3 de setembro de 2017 16:46, Luiz Carlos <lc94...@gmail.com> >>>>>>>>>>>> escreveu: >>>>>>>>>>>> >>>>>>>>>>>>> Estou a ponto de desistir, acho que não tem jeito pra essa >>>>>>>>>>>>> merda. >>>>>>>>>>>>> >>>>>>>>>>>>> Em 3 de setembro de 2017 20:19, Luiz Carlos <lc94...@gmail.com >>>>>>>>>>>>> > escreveu: >>>>>>>>>>>>> >>>>>>>>>>>>>> Você fala de secureboot na UEFI né? Eu fui lá, de "Windows" >>>>>>>>>>>>>> marquei pra Other OS, mas mesmo assim não resolveu. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Antes disso eu já tentei o boot-repair, eles falam que >>>>>>>>>>>>>> restauram o sistema, mas na pratica instalam um grub sem nada, >>>>>>>>>>>>>> aqui está o >>>>>>>>>>>>>> log deles: >>>>>>>>>>>>>> http://paste.ubuntu.com/25460229/ >>>>>>>>>>>>>> >>>>>>>>>>>>>> 2017-09-03 19:00 GMT+00:00 Rodolfo <rof20...@gmail.com>: >>>>>>>>>>>>>> >>>>>>>>>>>>>>> Seu computador tem UEFI? Verifica isso também, no meu tive >>>>>>>>>>>>>>> que desabilitar na BIOS um negócio de safe lá. >>>>>>>>>>>>>>> >>>>>>>>>>>>>>> 2017-09-03 14:58 GMT-04:00 Luiz Carlos <lc94...@gmail.com>: >>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> Ele instala normalmente, mas ele não reconhece as partições. >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> 2017-09-03 18:55 GMT+00:00 Rodolfo <rof20...@gmail.com>: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Faz isso, remove o grub: >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> # apt-get remove --purge grub >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> depois >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> # apt-get install grub >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Obs.: Não lembro o nome do pacote do grub. >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> 2017-09-03 14:53 GMT-04:00 Luiz Carlos <lc94...@gmail.com> >>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Estou na live cd sim, saí do chroot e tentei o seguinte >>>>>>>>>>>>>>>>>> comando: >>>>>>>>>>>>>>>>>> mint mint # grub-install --root-directory=/media/linux >>>>>>>>>>>>>>>>>> /dev/sda >>>>>>>>>>>>>>>>>> grub-probe: error: failed to get canonical path of `/cow'. >>>>>>>>>>>>>>>>>> Installing for i386-pc platform. >>>>>>>>>>>>>>>>>> grub-install.real: error: attempt to install to encrypted >>>>>>>>>>>>>>>>>> disk without cryptodisk enabled. Set >>>>>>>>>>>>>>>>>> `GRUB_ENABLE_CRYPTODISK=1' in file >>>>>>>>>>>>>>>>>> `/etc/default/grub'.. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Ou seja, deu merda, acho que nem o Windows vai iniciar >>>>>>>>>>>>>>>>>> depois dessa. >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> Em 3 de setembro de 2017 18:46, Rodolfo < >>>>>>>>>>>>>>>>>> rof20...@gmail.com> escreveu: >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Você chegou a usar um live-cd? >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> Eu tive um problema parecido, entrei pelo live-cd(ou >>>>>>>>>>>>>>>>>>> pelo cd de instalação do Debian, pois tem uma parte que >>>>>>>>>>>>>>>>>>> consigo acessar a >>>>>>>>>>>>>>>>>>> instalação que tinha pelo terminal) e reinstalei o grub, >>>>>>>>>>>>>>>>>>> isso mesmo, >>>>>>>>>>>>>>>>>>> reinstalei, não fiz nenhum comando, só fiz reinstalar. >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> 2017-09-03 14:29 GMT-04:00 Luiz Carlos < >>>>>>>>>>>>>>>>>>> lc94...@gmail.com>: >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Eu desabilitei o fastboot do windows 10, mas mando >>>>>>>>>>>>>>>>>>>> esses comandos e simplesmente dá erro: >>>>>>>>>>>>>>>>>>>> mint@mint ~ $ sudo su >>>>>>>>>>>>>>>>>>>> mint mint # modprobe dm-crypt >>>>>>>>>>>>>>>>>>>> mint mint # cryptsetup luksOpen /dev/sda5 linux >>>>>>>>>>>>>>>>>>>> Enter passphrase for /dev/sda5: >>>>>>>>>>>>>>>>>>>> mint mint # mkdir /media/linux >>>>>>>>>>>>>>>>>>>> mint mint # mount /dev/lvmc/root /media/linux/ >>>>>>>>>>>>>>>>>>>> mint mint # chroot /media/linux /bin/bash >>>>>>>>>>>>>>>>>>>> root@mint:/# mount /dev/sda2 /boot >>>>>>>>>>>>>>>>>>>> mount: /boot: mount failed: Unknown error -1 >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> Se não consigo montar a droga da /boot não vou >>>>>>>>>>>>>>>>>>>> conseguir instalar o grub. >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> 2017-09-03 17:53 GMT+00:00 Rodolfo <rof20...@gmail.com> >>>>>>>>>>>>>>>>>>>> : >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> Tentou bootar via live-cd? >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> 2017-09-03 12:17 GMT-04:00 Luiz Carlos < >>>>>>>>>>>>>>>>>>>>> lc94...@gmail.com>: >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> Que desgraça de vida, horas no google pesquisando e >>>>>>>>>>>>>>>>>>>>>> não consigo resolver porra nenhuma, maldita hora que fui >>>>>>>>>>>>>>>>>>>>>> inventar de >>>>>>>>>>>>>>>>>>>>>> instalar Windows 10 e achar que ia conseguir recuperar o >>>>>>>>>>>>>>>>>>>>>> Grub. >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> 2017-09-03 14:19 GMT+00:00 Luiz Carlos < >>>>>>>>>>>>>>>>>>>>>> lc94...@gmail.com>: >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Estou até agora tentando, tentei o comando: >>>>>>>>>>>>>>>>>>>>>>> # grub-install --boot-directory=/boot /dev/sda >>>>>>>>>>>>>>>>>>>>>>> Installing for i386-pc platform. >>>>>>>>>>>>>>>>>>>>>>> grub-install.real: warning: Sector 32 is already in >>>>>>>>>>>>>>>>>>>>>>> use by the program `FlexNet'; avoiding it. This >>>>>>>>>>>>>>>>>>>>>>> software may cause boot or >>>>>>>>>>>>>>>>>>>>>>> other problems in future. Please ask its authors not >>>>>>>>>>>>>>>>>>>>>>> to store data in the >>>>>>>>>>>>>>>>>>>>>>> boot track. >>>>>>>>>>>>>>>>>>>>>>> Installation finished. No error reported. >>>>>>>>>>>>>>>>>>>>>>> mint mint # grub-install --boot-directory=/boot >>>>>>>>>>>>>>>>>>>>>>> /dev/sda2 >>>>>>>>>>>>>>>>>>>>>>> Installing for i386-pc platform. >>>>>>>>>>>>>>>>>>>>>>> grub-install.real: warning: File system `ntfs' >>>>>>>>>>>>>>>>>>>>>>> doesn't support embedding. >>>>>>>>>>>>>>>>>>>>>>> grub-install.real: warning: Embedding is not >>>>>>>>>>>>>>>>>>>>>>> possible. GRUB can only be installed in this setup by >>>>>>>>>>>>>>>>>>>>>>> using blocklists. >>>>>>>>>>>>>>>>>>>>>>> However, blocklists are UNRELIABLE and their use is >>>>>>>>>>>>>>>>>>>>>>> discouraged.. >>>>>>>>>>>>>>>>>>>>>>> grub-install.real: error: will not proceed with >>>>>>>>>>>>>>>>>>>>>>> blocklists. >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> Em 3 de setembro de 2017 06:03, Luiz Carlos < >>>>>>>>>>>>>>>>>>>>>>> lc94...@gmail.com> escreveu: >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Olá amigos, estou em desespero, agora mesmo estou >>>>>>>>>>>>>>>>>>>>>>>> numa live cd tentando recuperar o grub, eu havia >>>>>>>>>>>>>>>>>>>>>>>> instalado o WIndows 10, >>>>>>>>>>>>>>>>>>>>>>>> estou com o Debian criptografado, tentei recuperar com >>>>>>>>>>>>>>>>>>>>>>>> esses seguintes >>>>>>>>>>>>>>>>>>>>>>>> comandos: >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> # modprobe dm-crypt >>>>>>>>>>>>>>>>>>>>>>>> # cryptsetup luksOpen /dev/sda5 linux >>>>>>>>>>>>>>>>>>>>>>>> # mkdir /media/linux >>>>>>>>>>>>>>>>>>>>>>>> # mount /dev/lvmc/root /media/linux/ >>>>>>>>>>>>>>>>>>>>>>>> # chroot /media/linux /bin/bash >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Dai quando mando # grub-install /dev/sda >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Aparece: /dev/sda: Not found or not a block device. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Eu não sei mais o que faço, aqui na live CD eu >>>>>>>>>>>>>>>>>>>>>>>> consigo ver minhas partições e tudo mais. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>> Meu Debian é de 64 bits. >>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>> >>>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>>>> >>>>> >>>> >> >
