udev rule triggers error âRead-only file systemâ

Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I created an udev rule that launches a shell script that creates a directory /media/my-disk when some specific USB HD is connected. It has been working many months, but after a reboot (probably some packages were updated) it shows the following message (in syslog) everytime I plug the drive in:
mkdir: cannot create directory '/media/my-disk': Read-only file system
I have added the following lines to the script:
whoami
mount
And the result is:
root
usb-mount.sh: /dev/mapper/sda3_crypt on / type btrfs (ro,relatime,ssd,space_cache,subvolid=257,subvol=/@)
So it seems udev is seeing the root filesystem as readonly, but if I execute sudo mount manually it shows it mounted as read/write:
/dev/mapper/sda3_crypt on / type btrfs (rw,relatime,ssd,space_cache,subvolid=257,subvol=/@)
I've searched on the Internet and I've found the same exact problem but without a solution:
https://www.raspberrypi.org/forums/viewtopic.php?t=210243
Restarting the udev service solves the problem until the next reboot.
What can I check solve it permanently?
NOTE: I am running Ubuntu 18.04.1 LTS
ubuntu udev
add a comment |Â
up vote
0
down vote
favorite
I created an udev rule that launches a shell script that creates a directory /media/my-disk when some specific USB HD is connected. It has been working many months, but after a reboot (probably some packages were updated) it shows the following message (in syslog) everytime I plug the drive in:
mkdir: cannot create directory '/media/my-disk': Read-only file system
I have added the following lines to the script:
whoami
mount
And the result is:
root
usb-mount.sh: /dev/mapper/sda3_crypt on / type btrfs (ro,relatime,ssd,space_cache,subvolid=257,subvol=/@)
So it seems udev is seeing the root filesystem as readonly, but if I execute sudo mount manually it shows it mounted as read/write:
/dev/mapper/sda3_crypt on / type btrfs (rw,relatime,ssd,space_cache,subvolid=257,subvol=/@)
I've searched on the Internet and I've found the same exact problem but without a solution:
https://www.raspberrypi.org/forums/viewtopic.php?t=210243
Restarting the udev service solves the problem until the next reboot.
What can I check solve it permanently?
NOTE: I am running Ubuntu 18.04.1 LTS
ubuntu udev
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I created an udev rule that launches a shell script that creates a directory /media/my-disk when some specific USB HD is connected. It has been working many months, but after a reboot (probably some packages were updated) it shows the following message (in syslog) everytime I plug the drive in:
mkdir: cannot create directory '/media/my-disk': Read-only file system
I have added the following lines to the script:
whoami
mount
And the result is:
root
usb-mount.sh: /dev/mapper/sda3_crypt on / type btrfs (ro,relatime,ssd,space_cache,subvolid=257,subvol=/@)
So it seems udev is seeing the root filesystem as readonly, but if I execute sudo mount manually it shows it mounted as read/write:
/dev/mapper/sda3_crypt on / type btrfs (rw,relatime,ssd,space_cache,subvolid=257,subvol=/@)
I've searched on the Internet and I've found the same exact problem but without a solution:
https://www.raspberrypi.org/forums/viewtopic.php?t=210243
Restarting the udev service solves the problem until the next reboot.
What can I check solve it permanently?
NOTE: I am running Ubuntu 18.04.1 LTS
ubuntu udev
I created an udev rule that launches a shell script that creates a directory /media/my-disk when some specific USB HD is connected. It has been working many months, but after a reboot (probably some packages were updated) it shows the following message (in syslog) everytime I plug the drive in:
mkdir: cannot create directory '/media/my-disk': Read-only file system
I have added the following lines to the script:
whoami
mount
And the result is:
root
usb-mount.sh: /dev/mapper/sda3_crypt on / type btrfs (ro,relatime,ssd,space_cache,subvolid=257,subvol=/@)
So it seems udev is seeing the root filesystem as readonly, but if I execute sudo mount manually it shows it mounted as read/write:
/dev/mapper/sda3_crypt on / type btrfs (rw,relatime,ssd,space_cache,subvolid=257,subvol=/@)
I've searched on the Internet and I've found the same exact problem but without a solution:
https://www.raspberrypi.org/forums/viewtopic.php?t=210243
Restarting the udev service solves the problem until the next reboot.
What can I check solve it permanently?
NOTE: I am running Ubuntu 18.04.1 LTS
ubuntu udev
ubuntu udev
asked Aug 16 at 17:52
Kilian
11
11
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f463031%2fudev-rule-triggers-error-read-only-file-system%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