| Disk /dev/sda: 223.6 GiB, 240057409536 bytes, 468862128 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: 342F4205-E187-4976-8FB4-263112C3B282 | |
| Device Start End Sectors Size Type | |
| /dev/sda1 2048 1050623 1048576 512M EFI System | |
| /dev/sda2 1050624 435396607 434345984 207.1G Linux filesystem | |
| /dev/sda3 435396608 468860927 33464320 16G Linux swap | |
| Disk /dev/sdb: 465.8 GiB, 500107862016 bytes, 976773168 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: F645F422-1246-4DA5-A150-6E2BE0FFC69B | |
| Device Start End Sectors Size Type | |
| /dev/sdb1 2048 34815 32768 16M Microsoft reserved | |
| /dev/sdb2 34816 956415 921600 450M Windows recovery environment | |
| /dev/sdb3 956416 1161215 204800 100M EFI System | |
| /dev/sdb4 1161216 976773119 975611904 465.2G Microsoft basic data |
Silvian
commented
Sep 3, 2017
|
open /etc/fstab in your favourite text editor and make sure you add this line at the very end: |
|
|
Silvian
commented
Sep 3, 2017
|
Run these commands to install and execute the grub recovery tool: |
|
Unable to detect file system! Possible reasons are:
sda1 |
|
Unable to read the contents of this file system! sda4 |
|
ntfs-3g: No device is specified. ntfs-3g 2015.3.14AR.1 integrated FUSE 28 - Third Generation NTFS Driver Copyright (C) 2005-2007 Yura Pakhuchiy Usage: ntfs-3g [-o option[,...]] <device|image_file> <mount_point> Options: ro (read-only mount), windows_names, uid=, gid=, Example: ntfs-3g /dev/sda1 /mnt/windows News, support and information: http://tuxera.com |
|
ntfs_mst_post_read_fixup_warn: magic: 0xffffffff size: 4096 usa_ofs: 65535 usa_count: 65534: Invalid argument |
/etc/fstab: static file system information.Use 'blkid' to print the universally unique identifier for adevice; this may be used with UUID= as a more robust way to name devicesthat works even if disks are added and removed. See fstab(5)./ was on /dev/sdb2 during installationUUID=9f8bf9a3-0b4c-4e1f-bc4c-25cdedbcb9e0 / ext4 errors=remount-ro 0 1 /boot/efi was on /dev/sdb1 during installationUUID=CCCA-2C5C /boot/efi vfat umask=0077 0 1 swap was on /dev/sdb3 during installationUUID=027ff38a-8979-4554-8151-9bfa924ceb9f none swap sw 0 0 |
|
|
|
|
|
|
|
|
|
|
Zman94 commentedSep 3, 2017
Error mounting /dev/sdb4 at /media/zach/32644B54644B19CD: Command-linemount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000" "/dev/sdb4" "/media/zach/32644B54644B19CD"' exited with non-zero exit status 13: ntfs_mst_post_read_fixup_warn: magic: 0xffffffff size: 4096 usa_ofs: 65535 usa_count: 65534: Invalid argumentActual VCN (0xffffffffffffffff) of index buffer is different from expected VCN (0x0).
Failed to mount '/dev/sdb4': Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it's a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the 'dmraid' documentation
for more details.`