Cryptmount-setup is not working
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
When I tried to set up encryption using cryptmount-setup, it just returns without any feedback. It did not even created the crypto.fs file. I ran the commands: cryptmount nextcloud_data and cryptmount -l to show that the creation of the target was clearly unsuccessful, as follows.
------------------------------
Your filing system is now ready to be built - this will involve:
- Creating the directory "/media/nextcloud_data"
- Creating a 2700000MB file, "/media/hdd_3tb/crypto.fs"
- Adding an extra entry ("nextcloud_data") in /etc/cryptmount/cmtab
- Creating a key-file ("/etc/cryptmount/nextcloud_data.key")
- Creating an ext3 filingsystem on "/media/hdd_3tb/crypto.fs"
If you do not wish to proceed, no changes will be made to your system.
Please confirm that you want to proceed (enter "yes")
[no]: yes
Making mount-point (/media/nextcloud_data)... done
Creating filesystem container (/media/hdd_3tb/crypto.fs)...~ $
~ $
~ $
~ $ cryptmount nextcloud_data
Target name "nextcloud_data" is not recognized
~ $ cryptmount -l
~ $
I already reduced the size of the crypto-file, to make sure that is not the problem. Any ideas about this issue?
mount disk-encryption cryptsetup dm-crypt
edited Sep 16 at 15:23
Goro
5,75252662
asked Sep 16 at 11:04
user6105651
104
add a comment |Â
up vote
0
down vote
favorite
When I tried to set up encryption using cryptmount-setup, it just returns without any feedback. It did not even created the crypto.fs file. I ran the commands: cryptmount nextcloud_data and cryptmount -l to show that the creation of the target was clearly unsuccessful, as follows.
------------------------------
Your filing system is now ready to be built - this will involve:
- Creating the directory "/media/nextcloud_data"
- Creating a 2700000MB file, "/media/hdd_3tb/crypto.fs"
- Adding an extra entry ("nextcloud_data") in /etc/cryptmount/cmtab
- Creating a key-file ("/etc/cryptmount/nextcloud_data.key")
- Creating an ext3 filingsystem on "/media/hdd_3tb/crypto.fs"
If you do not wish to proceed, no changes will be made to your system.
Please confirm that you want to proceed (enter "yes")
[no]: yes
Making mount-point (/media/nextcloud_data)... done
Creating filesystem container (/media/hdd_3tb/crypto.fs)...~ $
~ $
~ $
~ $ cryptmount nextcloud_data
Target name "nextcloud_data" is not recognized
~ $ cryptmount -l
~ $
I already reduced the size of the crypto-file, to make sure that is not the problem. Any ideas about this issue?
mount disk-encryption cryptsetup dm-crypt
edited Sep 16 at 15:23
Goro
5,75252662
asked Sep 16 at 11:04
user6105651
104
Would you please care to expand in the question. not in comments, why the error that you have got in your own pasted text is not a valid feedback?
– Rui F Ribeiro
Sep 16 at 11:06
Was theCreating filesystem containercommand interrupted or die separately? It didn’t end the line on its own.
– Jeff Schaller
Sep 17 at 12:49
It died on it's own. The reason for the is that I tried to write to a partition as read-only, as you can see in my answer below. I just can't accept it as the solution yet.
– user6105651
Sep 17 at 12:53
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When I tried to set up encryption using cryptmount-setup, it just returns without any feedback. It did not even created the crypto.fs file. I ran the commands: cryptmount nextcloud_data and cryptmount -l to show that the creation of the target was clearly unsuccessful, as follows.
------------------------------
Your filing system is now ready to be built - this will involve:
- Creating the directory "/media/nextcloud_data"
- Creating a 2700000MB file, "/media/hdd_3tb/crypto.fs"
- Adding an extra entry ("nextcloud_data") in /etc/cryptmount/cmtab
- Creating a key-file ("/etc/cryptmount/nextcloud_data.key")
- Creating an ext3 filingsystem on "/media/hdd_3tb/crypto.fs"
If you do not wish to proceed, no changes will be made to your system.
Please confirm that you want to proceed (enter "yes")
[no]: yes
Making mount-point (/media/nextcloud_data)... done
Creating filesystem container (/media/hdd_3tb/crypto.fs)...~ $
~ $
~ $
~ $ cryptmount nextcloud_data
Target name "nextcloud_data" is not recognized
~ $ cryptmount -l
~ $
I already reduced the size of the crypto-file, to make sure that is not the problem. Any ideas about this issue?
mount disk-encryption cryptsetup dm-crypt
edited Sep 16 at 15:23
Goro
5,75252662
asked Sep 16 at 11:04
user6105651
104
When I tried to set up encryption using cryptmount-setup, it just returns without any feedback. It did not even created the crypto.fs file. I ran the commands: cryptmount nextcloud_data and cryptmount -l to show that the creation of the target was clearly unsuccessful, as follows.
------------------------------
Your filing system is now ready to be built - this will involve:
- Creating the directory "/media/nextcloud_data"
- Creating a 2700000MB file, "/media/hdd_3tb/crypto.fs"
- Adding an extra entry ("nextcloud_data") in /etc/cryptmount/cmtab
- Creating a key-file ("/etc/cryptmount/nextcloud_data.key")
- Creating an ext3 filingsystem on "/media/hdd_3tb/crypto.fs"
If you do not wish to proceed, no changes will be made to your system.
Please confirm that you want to proceed (enter "yes")
[no]: yes
Making mount-point (/media/nextcloud_data)... done
Creating filesystem container (/media/hdd_3tb/crypto.fs)...~ $
~ $
~ $
~ $ cryptmount nextcloud_data
Target name "nextcloud_data" is not recognized
~ $ cryptmount -l
~ $
I already reduced the size of the crypto-file, to make sure that is not the problem. Any ideas about this issue?
mount disk-encryption cryptsetup dm-crypt
mount disk-encryption cryptsetup dm-crypt
edited Sep 16 at 15:23
Goro
5,75252662
asked Sep 16 at 11:04
user6105651
104
edited Sep 16 at 15:23
Goro
5,75252662
asked Sep 16 at 11:04
user6105651
104
edited Sep 16 at 15:23
Goro
5,75252662
edited Sep 16 at 15:23
Goro
5,75252662
edited Sep 16 at 15:23
Goro
5,75252662
5,75252662
asked Sep 16 at 11:04
user6105651
104
asked Sep 16 at 11:04
user6105651
104
asked Sep 16 at 11:04
user6105651
104
104
Would you please care to expand in the question. not in comments, why the error that you have got in your own pasted text is not a valid feedback?
– Rui F Ribeiro
Sep 16 at 11:06
Was theCreating filesystem containercommand interrupted or die separately? It didn’t end the line on its own.
– Jeff Schaller
Sep 17 at 12:49
It died on it's own. The reason for the is that I tried to write to a partition as read-only, as you can see in my answer below. I just can't accept it as the solution yet.
– user6105651
Sep 17 at 12:53
add a comment |Â
Would you please care to expand in the question. not in comments, why the error that you have got in your own pasted text is not a valid feedback?
– Rui F Ribeiro
Sep 16 at 11:06
Was theCreating filesystem containercommand interrupted or die separately? It didn’t end the line on its own.
– Jeff Schaller
Sep 17 at 12:49
It died on it's own. The reason for the is that I tried to write to a partition as read-only, as you can see in my answer below. I just can't accept it as the solution yet.
– user6105651
Sep 17 at 12:53
Would you please care to expand in the question. not in comments, why the error that you have got in your own pasted text is not a valid feedback?
– Rui F Ribeiro
Sep 16 at 11:06
Would you please care to expand in the question. not in comments, why the error that you have got in your own pasted text is not a valid feedback?
– Rui F Ribeiro
Sep 16 at 11:06
Was the
Creating filesystem container command interrupted or die separately? It didn’t end the line on its own.– Jeff Schaller
Sep 17 at 12:49
Was the
Creating filesystem container command interrupted or die separately? It didn’t end the line on its own.– Jeff Schaller
Sep 17 at 12:49
It died on it's own. The reason for the is that I tried to write to a partition as read-only, as you can see in my answer below. I just can't accept it as the solution yet.
– user6105651
Sep 17 at 12:53
It died on it's own. The reason for the is that I tried to write to a partition as read-only, as you can see in my answer below. I just can't accept it as the solution yet.
– user6105651
Sep 17 at 12:53
add a comment |Â
1 Answer
1
active
oldest
votes
up vote
0
down vote
accepted
Cryptmount-setup tries to write to a partition that is mounted in read-only mode, that is why the command exits unexpectedly.
answered Sep 17 at 11:18
user6105651
104
This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review
– Romeo Ninov
Sep 17 at 12:41
Thanks for your feedback, I'm new to StackExchange. However I'm not sure how to improve my answer. I'm the author of the question and discovered that I tried to write to a partition that is mounted in read only mode, that is why the cryptmount-setup tool exits.
– user6105651
Sep 17 at 12:49
add a comment |Â
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
accepted
Cryptmount-setup tries to write to a partition that is mounted in read-only mode, that is why the command exits unexpectedly.
answered Sep 17 at 11:18
user6105651
104
This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review
– Romeo Ninov
Sep 17 at 12:41
Thanks for your feedback, I'm new to StackExchange. However I'm not sure how to improve my answer. I'm the author of the question and discovered that I tried to write to a partition that is mounted in read only mode, that is why the cryptmount-setup tool exits.
– user6105651
Sep 17 at 12:49
add a comment |Â
up vote
0
down vote
accepted
Cryptmount-setup tries to write to a partition that is mounted in read-only mode, that is why the command exits unexpectedly.
answered Sep 17 at 11:18
user6105651
104
This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review
– Romeo Ninov
Sep 17 at 12:41
Thanks for your feedback, I'm new to StackExchange. However I'm not sure how to improve my answer. I'm the author of the question and discovered that I tried to write to a partition that is mounted in read only mode, that is why the cryptmount-setup tool exits.
– user6105651
Sep 17 at 12:49
add a comment |Â
up vote
0
down vote
accepted
up vote
0
down vote
accepted
Cryptmount-setup tries to write to a partition that is mounted in read-only mode, that is why the command exits unexpectedly.
answered Sep 17 at 11:18
user6105651
104
Cryptmount-setup tries to write to a partition that is mounted in read-only mode, that is why the command exits unexpectedly.
answered Sep 17 at 11:18
user6105651
104
edited Sep 17 at 12:50
answered Sep 17 at 11:18
user6105651
104
answered Sep 17 at 11:18
user6105651
104
answered Sep 17 at 11:18
user6105651
104
104
This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review
– Romeo Ninov
Sep 17 at 12:41
Thanks for your feedback, I'm new to StackExchange. However I'm not sure how to improve my answer. I'm the author of the question and discovered that I tried to write to a partition that is mounted in read only mode, that is why the cryptmount-setup tool exits.
– user6105651
Sep 17 at 12:49
add a comment |Â
This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review
– Romeo Ninov
Sep 17 at 12:41
Thanks for your feedback, I'm new to StackExchange. However I'm not sure how to improve my answer. I'm the author of the question and discovered that I tried to write to a partition that is mounted in read only mode, that is why the cryptmount-setup tool exits.
– user6105651
Sep 17 at 12:49
This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review
– Romeo Ninov
Sep 17 at 12:41
This does not provide an answer to the question. To critique or request clarification from an author, leave a comment below their post. - From Review
– Romeo Ninov
Sep 17 at 12:41
Thanks for your feedback, I'm new to StackExchange. However I'm not sure how to improve my answer. I'm the author of the question and discovered that I tried to write to a partition that is mounted in read only mode, that is why the cryptmount-setup tool exits.
– user6105651
Sep 17 at 12:49
Thanks for your feedback, I'm new to StackExchange. However I'm not sure how to improve my answer. I'm the author of the question and discovered that I tried to write to a partition that is mounted in read only mode, that is why the cryptmount-setup tool exits.
– user6105651
Sep 17 at 12:49
add a comment |Â
Â
draft saved
draft discarded
Â
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f469363%2fcryptmount-setup-is-not-working%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Would you please care to expand in the question. not in comments, why the error that you have got in your own pasted text is not a valid feedback?
– Rui F Ribeiro
Sep 16 at 11:06
Was the
Creating filesystem containercommand interrupted or die separately? It didn’t end the line on its own.– Jeff Schaller
Sep 17 at 12:49
It died on it's own. The reason for the is that I tried to write to a partition as read-only, as you can see in my answer below. I just can't accept it as the solution yet.
– user6105651
Sep 17 at 12:53