Cannot mount drive under ubuntu server 18.04












1















I have upgraded my home server from ubuntu 12.04 to 18.04. The system holds 2 disks of 2.0TB in Raid 1. When I try to mount them on the 18.04 I get the following error.



mount -t ntfs /dev/md126 /mnt/media



I have also tries mount -t ntfs-3g without success.



NTFS signature is missing.
Failed to mount '/dev/md126': Invalid argument
The device '/dev/md126' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?


The ouput from fdisk -l /dev/md126 is



Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000136a9

Device Boot Start End Sectors Size Id Type
/dev/md126p1 63 3907023111 3907023049 1.8T 7 HPFS/NTFS/exFAT

Partition 1 does not start on physical sector boundary.


And the output of gdisk -l is



GPT fdisk (gdisk) version 1.0.3

Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************


Warning! Secondary partition table overlaps the last partition by
297 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/md126: 3907022848 sectors, 1.8 TiB
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): DC6C901E-C3A5-43C1-8C9E-8E6397C5F145
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 3907022814
Partitions will be aligned on 8-sector boundaries
Total free space is 29 sectors (14.5 KiB)

Number Start (sector) End (sector) Size Code Name
1 63 3907023111 1.8 TiB 0700 Microsoft basic data


And finally when i check the mdadm --detail /dev/m126 i get the following result



/dev/md126:
Container : /dev/md/imsm0, member 0
Raid Level : raid1
Array Size : 1953511424 (1863.01 GiB 2000.40 GB)
Used Dev Size : 1953511424 (1863.01 GiB 2000.40 GB)
Raid Devices : 2
Total Devices : 2

State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Consistency Policy : resync


UUID : 562a1dd0:13fa432c:bec8c322:89cbd43f
Number Major Minor RaidDevice State
1 8 0 0 active sync /dev/sda
0 8 16 1 active sync /dev/sdb


When I switch back to the 12.04 (I've installed 18.04 on a new disk) everything works fine.



Does anyone have an idea what is going wrong?



When I try to mount the partition I het a similar error
mount /dev/md126p1 -t ntfs-3g /mnt/media



Failed to read last sector (3907023047): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/md126p1': Invalid argument
The device '/dev/md126p1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?









share|improve this question

























  • In your first command you use /dev/mda126 - typo?

    – Jos
    Jan 4 at 14:56











  • @Jos that's a typo in my question, edited it.

    – Jeroen
    Jan 5 at 10:27











  • No need to add Solved and solution to the question. Accepting an answer is enough to mark your question as Solved :)

    – Kulfy
    Jan 5 at 11:16
















1















I have upgraded my home server from ubuntu 12.04 to 18.04. The system holds 2 disks of 2.0TB in Raid 1. When I try to mount them on the 18.04 I get the following error.



mount -t ntfs /dev/md126 /mnt/media



I have also tries mount -t ntfs-3g without success.



NTFS signature is missing.
Failed to mount '/dev/md126': Invalid argument
The device '/dev/md126' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?


The ouput from fdisk -l /dev/md126 is



Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000136a9

Device Boot Start End Sectors Size Id Type
/dev/md126p1 63 3907023111 3907023049 1.8T 7 HPFS/NTFS/exFAT

Partition 1 does not start on physical sector boundary.


And the output of gdisk -l is



GPT fdisk (gdisk) version 1.0.3

Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************


Warning! Secondary partition table overlaps the last partition by
297 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/md126: 3907022848 sectors, 1.8 TiB
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): DC6C901E-C3A5-43C1-8C9E-8E6397C5F145
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 3907022814
Partitions will be aligned on 8-sector boundaries
Total free space is 29 sectors (14.5 KiB)

Number Start (sector) End (sector) Size Code Name
1 63 3907023111 1.8 TiB 0700 Microsoft basic data


And finally when i check the mdadm --detail /dev/m126 i get the following result



/dev/md126:
Container : /dev/md/imsm0, member 0
Raid Level : raid1
Array Size : 1953511424 (1863.01 GiB 2000.40 GB)
Used Dev Size : 1953511424 (1863.01 GiB 2000.40 GB)
Raid Devices : 2
Total Devices : 2

State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Consistency Policy : resync


UUID : 562a1dd0:13fa432c:bec8c322:89cbd43f
Number Major Minor RaidDevice State
1 8 0 0 active sync /dev/sda
0 8 16 1 active sync /dev/sdb


When I switch back to the 12.04 (I've installed 18.04 on a new disk) everything works fine.



Does anyone have an idea what is going wrong?



When I try to mount the partition I het a similar error
mount /dev/md126p1 -t ntfs-3g /mnt/media



Failed to read last sector (3907023047): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/md126p1': Invalid argument
The device '/dev/md126p1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?









share|improve this question

























  • In your first command you use /dev/mda126 - typo?

    – Jos
    Jan 4 at 14:56











  • @Jos that's a typo in my question, edited it.

    – Jeroen
    Jan 5 at 10:27











  • No need to add Solved and solution to the question. Accepting an answer is enough to mark your question as Solved :)

    – Kulfy
    Jan 5 at 11:16














1












1








1








I have upgraded my home server from ubuntu 12.04 to 18.04. The system holds 2 disks of 2.0TB in Raid 1. When I try to mount them on the 18.04 I get the following error.



mount -t ntfs /dev/md126 /mnt/media



I have also tries mount -t ntfs-3g without success.



NTFS signature is missing.
Failed to mount '/dev/md126': Invalid argument
The device '/dev/md126' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?


The ouput from fdisk -l /dev/md126 is



Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000136a9

Device Boot Start End Sectors Size Id Type
/dev/md126p1 63 3907023111 3907023049 1.8T 7 HPFS/NTFS/exFAT

Partition 1 does not start on physical sector boundary.


And the output of gdisk -l is



GPT fdisk (gdisk) version 1.0.3

Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************


Warning! Secondary partition table overlaps the last partition by
297 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/md126: 3907022848 sectors, 1.8 TiB
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): DC6C901E-C3A5-43C1-8C9E-8E6397C5F145
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 3907022814
Partitions will be aligned on 8-sector boundaries
Total free space is 29 sectors (14.5 KiB)

Number Start (sector) End (sector) Size Code Name
1 63 3907023111 1.8 TiB 0700 Microsoft basic data


And finally when i check the mdadm --detail /dev/m126 i get the following result



/dev/md126:
Container : /dev/md/imsm0, member 0
Raid Level : raid1
Array Size : 1953511424 (1863.01 GiB 2000.40 GB)
Used Dev Size : 1953511424 (1863.01 GiB 2000.40 GB)
Raid Devices : 2
Total Devices : 2

State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Consistency Policy : resync


UUID : 562a1dd0:13fa432c:bec8c322:89cbd43f
Number Major Minor RaidDevice State
1 8 0 0 active sync /dev/sda
0 8 16 1 active sync /dev/sdb


When I switch back to the 12.04 (I've installed 18.04 on a new disk) everything works fine.



Does anyone have an idea what is going wrong?



When I try to mount the partition I het a similar error
mount /dev/md126p1 -t ntfs-3g /mnt/media



Failed to read last sector (3907023047): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/md126p1': Invalid argument
The device '/dev/md126p1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?









share|improve this question
















I have upgraded my home server from ubuntu 12.04 to 18.04. The system holds 2 disks of 2.0TB in Raid 1. When I try to mount them on the 18.04 I get the following error.



mount -t ntfs /dev/md126 /mnt/media



I have also tries mount -t ntfs-3g without success.



NTFS signature is missing.
Failed to mount '/dev/md126': Invalid argument
The device '/dev/md126' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?


The ouput from fdisk -l /dev/md126 is



Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x000136a9

Device Boot Start End Sectors Size Id Type
/dev/md126p1 63 3907023111 3907023049 1.8T 7 HPFS/NTFS/exFAT

Partition 1 does not start on physical sector boundary.


And the output of gdisk -l is



GPT fdisk (gdisk) version 1.0.3

Partition table scan:
MBR: MBR only
BSD: not present
APM: not present
GPT: not present


***************************************************************
Found invalid GPT and valid MBR; converting MBR to GPT format
in memory.
***************************************************************


Warning! Secondary partition table overlaps the last partition by
297 blocks!
You will need to delete this partition or resize it in another utility.
Disk /dev/md126: 3907022848 sectors, 1.8 TiB
Sector size (logical/physical): 512/4096 bytes
Disk identifier (GUID): DC6C901E-C3A5-43C1-8C9E-8E6397C5F145
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 3907022814
Partitions will be aligned on 8-sector boundaries
Total free space is 29 sectors (14.5 KiB)

Number Start (sector) End (sector) Size Code Name
1 63 3907023111 1.8 TiB 0700 Microsoft basic data


And finally when i check the mdadm --detail /dev/m126 i get the following result



/dev/md126:
Container : /dev/md/imsm0, member 0
Raid Level : raid1
Array Size : 1953511424 (1863.01 GiB 2000.40 GB)
Used Dev Size : 1953511424 (1863.01 GiB 2000.40 GB)
Raid Devices : 2
Total Devices : 2

State : clean
Active Devices : 2
Working Devices : 2
Failed Devices : 0
Spare Devices : 0

Consistency Policy : resync


UUID : 562a1dd0:13fa432c:bec8c322:89cbd43f
Number Major Minor RaidDevice State
1 8 0 0 active sync /dev/sda
0 8 16 1 active sync /dev/sdb


When I switch back to the 12.04 (I've installed 18.04 on a new disk) everything works fine.



Does anyone have an idea what is going wrong?



When I try to mount the partition I het a similar error
mount /dev/md126p1 -t ntfs-3g /mnt/media



Failed to read last sector (3907023047): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/md126p1': Invalid argument
The device '/dev/md126p1' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?






18.04 mount mdadm fdisk gdisk






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jan 5 at 11:15









Kulfy

4,43651542




4,43651542










asked Jan 4 at 14:01









JeroenJeroen

83




83













  • In your first command you use /dev/mda126 - typo?

    – Jos
    Jan 4 at 14:56











  • @Jos that's a typo in my question, edited it.

    – Jeroen
    Jan 5 at 10:27











  • No need to add Solved and solution to the question. Accepting an answer is enough to mark your question as Solved :)

    – Kulfy
    Jan 5 at 11:16



















  • In your first command you use /dev/mda126 - typo?

    – Jos
    Jan 4 at 14:56











  • @Jos that's a typo in my question, edited it.

    – Jeroen
    Jan 5 at 10:27











  • No need to add Solved and solution to the question. Accepting an answer is enough to mark your question as Solved :)

    – Kulfy
    Jan 5 at 11:16

















In your first command you use /dev/mda126 - typo?

– Jos
Jan 4 at 14:56





In your first command you use /dev/mda126 - typo?

– Jos
Jan 4 at 14:56













@Jos that's a typo in my question, edited it.

– Jeroen
Jan 5 at 10:27





@Jos that's a typo in my question, edited it.

– Jeroen
Jan 5 at 10:27













No need to add Solved and solution to the question. Accepting an answer is enough to mark your question as Solved :)

– Kulfy
Jan 5 at 11:16





No need to add Solved and solution to the question. Accepting an answer is enough to mark your question as Solved :)

– Kulfy
Jan 5 at 11:16










1 Answer
1






active

oldest

votes


















0














You attempt to mount the wrong device. You're trying to mount /dev/mda126, which is not the partition.



Replace /dev/mda126 with /dev/md126p1.






share|improve this answer
























  • Please update your question with exact command and exact error message.

    – vidarlo
    Jan 5 at 10:22











  • And as a sidenote: this is a very strange configuration. You have a MD array, which by default is only accessible on Linux, with a file system that only has a complete toolset available for Windows...

    – vidarlo
    Jan 5 at 10:23











  • I made this array a long time ago. I use the array as a samba share. Maybe it is a good idea to just backup the data and recreate the array then?

    – Jeroen
    Jan 5 at 10:26











  • Thanks, I was indeed mounting the wrong device. As a addition to the solution I had to run ntfsfix /dev/md126p1. Marked your answer as solution.

    – Jeroen
    Jan 5 at 10:34











  • As it is a device that can only be used on a Linux system, if possible, a Unix file system would be a better idea in my opinion. You have to weigh this against the cost of recreating the file system.

    – vidarlo
    Jan 5 at 10:41











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1106927%2fcannot-mount-drive-under-ubuntu-server-18-04%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























1 Answer
1






active

oldest

votes








1 Answer
1






active

oldest

votes









active

oldest

votes






active

oldest

votes









0














You attempt to mount the wrong device. You're trying to mount /dev/mda126, which is not the partition.



Replace /dev/mda126 with /dev/md126p1.






share|improve this answer
























  • Please update your question with exact command and exact error message.

    – vidarlo
    Jan 5 at 10:22











  • And as a sidenote: this is a very strange configuration. You have a MD array, which by default is only accessible on Linux, with a file system that only has a complete toolset available for Windows...

    – vidarlo
    Jan 5 at 10:23











  • I made this array a long time ago. I use the array as a samba share. Maybe it is a good idea to just backup the data and recreate the array then?

    – Jeroen
    Jan 5 at 10:26











  • Thanks, I was indeed mounting the wrong device. As a addition to the solution I had to run ntfsfix /dev/md126p1. Marked your answer as solution.

    – Jeroen
    Jan 5 at 10:34











  • As it is a device that can only be used on a Linux system, if possible, a Unix file system would be a better idea in my opinion. You have to weigh this against the cost of recreating the file system.

    – vidarlo
    Jan 5 at 10:41
















0














You attempt to mount the wrong device. You're trying to mount /dev/mda126, which is not the partition.



Replace /dev/mda126 with /dev/md126p1.






share|improve this answer
























  • Please update your question with exact command and exact error message.

    – vidarlo
    Jan 5 at 10:22











  • And as a sidenote: this is a very strange configuration. You have a MD array, which by default is only accessible on Linux, with a file system that only has a complete toolset available for Windows...

    – vidarlo
    Jan 5 at 10:23











  • I made this array a long time ago. I use the array as a samba share. Maybe it is a good idea to just backup the data and recreate the array then?

    – Jeroen
    Jan 5 at 10:26











  • Thanks, I was indeed mounting the wrong device. As a addition to the solution I had to run ntfsfix /dev/md126p1. Marked your answer as solution.

    – Jeroen
    Jan 5 at 10:34











  • As it is a device that can only be used on a Linux system, if possible, a Unix file system would be a better idea in my opinion. You have to weigh this against the cost of recreating the file system.

    – vidarlo
    Jan 5 at 10:41














0












0








0







You attempt to mount the wrong device. You're trying to mount /dev/mda126, which is not the partition.



Replace /dev/mda126 with /dev/md126p1.






share|improve this answer













You attempt to mount the wrong device. You're trying to mount /dev/mda126, which is not the partition.



Replace /dev/mda126 with /dev/md126p1.







share|improve this answer












share|improve this answer



share|improve this answer










answered Jan 4 at 15:51









vidarlovidarlo

10.3k52447




10.3k52447













  • Please update your question with exact command and exact error message.

    – vidarlo
    Jan 5 at 10:22











  • And as a sidenote: this is a very strange configuration. You have a MD array, which by default is only accessible on Linux, with a file system that only has a complete toolset available for Windows...

    – vidarlo
    Jan 5 at 10:23











  • I made this array a long time ago. I use the array as a samba share. Maybe it is a good idea to just backup the data and recreate the array then?

    – Jeroen
    Jan 5 at 10:26











  • Thanks, I was indeed mounting the wrong device. As a addition to the solution I had to run ntfsfix /dev/md126p1. Marked your answer as solution.

    – Jeroen
    Jan 5 at 10:34











  • As it is a device that can only be used on a Linux system, if possible, a Unix file system would be a better idea in my opinion. You have to weigh this against the cost of recreating the file system.

    – vidarlo
    Jan 5 at 10:41



















  • Please update your question with exact command and exact error message.

    – vidarlo
    Jan 5 at 10:22











  • And as a sidenote: this is a very strange configuration. You have a MD array, which by default is only accessible on Linux, with a file system that only has a complete toolset available for Windows...

    – vidarlo
    Jan 5 at 10:23











  • I made this array a long time ago. I use the array as a samba share. Maybe it is a good idea to just backup the data and recreate the array then?

    – Jeroen
    Jan 5 at 10:26











  • Thanks, I was indeed mounting the wrong device. As a addition to the solution I had to run ntfsfix /dev/md126p1. Marked your answer as solution.

    – Jeroen
    Jan 5 at 10:34











  • As it is a device that can only be used on a Linux system, if possible, a Unix file system would be a better idea in my opinion. You have to weigh this against the cost of recreating the file system.

    – vidarlo
    Jan 5 at 10:41

















Please update your question with exact command and exact error message.

– vidarlo
Jan 5 at 10:22





Please update your question with exact command and exact error message.

– vidarlo
Jan 5 at 10:22













And as a sidenote: this is a very strange configuration. You have a MD array, which by default is only accessible on Linux, with a file system that only has a complete toolset available for Windows...

– vidarlo
Jan 5 at 10:23





And as a sidenote: this is a very strange configuration. You have a MD array, which by default is only accessible on Linux, with a file system that only has a complete toolset available for Windows...

– vidarlo
Jan 5 at 10:23













I made this array a long time ago. I use the array as a samba share. Maybe it is a good idea to just backup the data and recreate the array then?

– Jeroen
Jan 5 at 10:26





I made this array a long time ago. I use the array as a samba share. Maybe it is a good idea to just backup the data and recreate the array then?

– Jeroen
Jan 5 at 10:26













Thanks, I was indeed mounting the wrong device. As a addition to the solution I had to run ntfsfix /dev/md126p1. Marked your answer as solution.

– Jeroen
Jan 5 at 10:34





Thanks, I was indeed mounting the wrong device. As a addition to the solution I had to run ntfsfix /dev/md126p1. Marked your answer as solution.

– Jeroen
Jan 5 at 10:34













As it is a device that can only be used on a Linux system, if possible, a Unix file system would be a better idea in my opinion. You have to weigh this against the cost of recreating the file system.

– vidarlo
Jan 5 at 10:41





As it is a device that can only be used on a Linux system, if possible, a Unix file system would be a better idea in my opinion. You have to weigh this against the cost of recreating the file system.

– vidarlo
Jan 5 at 10:41


















draft saved

draft discarded




















































Thanks for contributing an answer to Ask Ubuntu!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1106927%2fcannot-mount-drive-under-ubuntu-server-18-04%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

Biblatex bibliography style without URLs when DOI exists (in Overleaf with Zotero bibliography)

ComboBox Display Member on multiple fields

Is it possible to collect Nectar points via Trainline?