/dev/sr0 (live DVD) turns into /dev/sr1 when inserting periphials
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
On a live Linux session, inserting a keyboard or mouse via USB onto the computer causes /dev/sr0 to be remapped as /dev/sr1, which makes the live system unable to access the DVD.
sudo rename /dev/sr1 /dev/sr0
does rename the device file but running lsblk
still shows the DVD drive as sr1.
Additionally, sudo mount /dev/sr1 /cdrom
-o noatime` (default mounting options) do not fix the Input/Output errors from loop0, which represents the SquashFS.
Even after that, I still get an Input/Output errors and SquashFS errors, because SquashFS memorizes unreadable sectors, which causes them even to be inaccessible, despite the DVD is mounted correctly and available again.
How can I make SquashFS read from the DVD again and reset the errors?
devices block-device livecd squashfs
add a comment |Â
up vote
0
down vote
favorite
On a live Linux session, inserting a keyboard or mouse via USB onto the computer causes /dev/sr0 to be remapped as /dev/sr1, which makes the live system unable to access the DVD.
sudo rename /dev/sr1 /dev/sr0
does rename the device file but running lsblk
still shows the DVD drive as sr1.
Additionally, sudo mount /dev/sr1 /cdrom
-o noatime` (default mounting options) do not fix the Input/Output errors from loop0, which represents the SquashFS.
Even after that, I still get an Input/Output errors and SquashFS errors, because SquashFS memorizes unreadable sectors, which causes them even to be inaccessible, despite the DVD is mounted correctly and available again.
How can I make SquashFS read from the DVD again and reset the errors?
devices block-device livecd squashfs
2
Which live system (distribution, version)? Is the DVD a USB peripheral? It would help to post the kernel logs (all the kernel logs starting when you insert the USB peripheral that messes up the DVD access). Post logs from a session where you don't try to rename the device file, because that can't help but could add problems of its own.
â Gilles
May 2 at 17:29
@Gilles It is Ubuntu Studio 16.04.2 LTS, and the DVD is internal, but it also happens on a different laptop where the DVD drive is an external one with USB. I will post the kernel logs the next time it happens.
â neverMind9
May 3 at 13:50
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
On a live Linux session, inserting a keyboard or mouse via USB onto the computer causes /dev/sr0 to be remapped as /dev/sr1, which makes the live system unable to access the DVD.
sudo rename /dev/sr1 /dev/sr0
does rename the device file but running lsblk
still shows the DVD drive as sr1.
Additionally, sudo mount /dev/sr1 /cdrom
-o noatime` (default mounting options) do not fix the Input/Output errors from loop0, which represents the SquashFS.
Even after that, I still get an Input/Output errors and SquashFS errors, because SquashFS memorizes unreadable sectors, which causes them even to be inaccessible, despite the DVD is mounted correctly and available again.
How can I make SquashFS read from the DVD again and reset the errors?
devices block-device livecd squashfs
On a live Linux session, inserting a keyboard or mouse via USB onto the computer causes /dev/sr0 to be remapped as /dev/sr1, which makes the live system unable to access the DVD.
sudo rename /dev/sr1 /dev/sr0
does rename the device file but running lsblk
still shows the DVD drive as sr1.
Additionally, sudo mount /dev/sr1 /cdrom
-o noatime` (default mounting options) do not fix the Input/Output errors from loop0, which represents the SquashFS.
Even after that, I still get an Input/Output errors and SquashFS errors, because SquashFS memorizes unreadable sectors, which causes them even to be inaccessible, despite the DVD is mounted correctly and available again.
How can I make SquashFS read from the DVD again and reset the errors?
devices block-device livecd squashfs
asked May 2 at 17:23
neverMind9
22110
22110
2
Which live system (distribution, version)? Is the DVD a USB peripheral? It would help to post the kernel logs (all the kernel logs starting when you insert the USB peripheral that messes up the DVD access). Post logs from a session where you don't try to rename the device file, because that can't help but could add problems of its own.
â Gilles
May 2 at 17:29
@Gilles It is Ubuntu Studio 16.04.2 LTS, and the DVD is internal, but it also happens on a different laptop where the DVD drive is an external one with USB. I will post the kernel logs the next time it happens.
â neverMind9
May 3 at 13:50
add a comment |Â
2
Which live system (distribution, version)? Is the DVD a USB peripheral? It would help to post the kernel logs (all the kernel logs starting when you insert the USB peripheral that messes up the DVD access). Post logs from a session where you don't try to rename the device file, because that can't help but could add problems of its own.
â Gilles
May 2 at 17:29
@Gilles It is Ubuntu Studio 16.04.2 LTS, and the DVD is internal, but it also happens on a different laptop where the DVD drive is an external one with USB. I will post the kernel logs the next time it happens.
â neverMind9
May 3 at 13:50
2
2
Which live system (distribution, version)? Is the DVD a USB peripheral? It would help to post the kernel logs (all the kernel logs starting when you insert the USB peripheral that messes up the DVD access). Post logs from a session where you don't try to rename the device file, because that can't help but could add problems of its own.
â Gilles
May 2 at 17:29
Which live system (distribution, version)? Is the DVD a USB peripheral? It would help to post the kernel logs (all the kernel logs starting when you insert the USB peripheral that messes up the DVD access). Post logs from a session where you don't try to rename the device file, because that can't help but could add problems of its own.
â Gilles
May 2 at 17:29
@Gilles It is Ubuntu Studio 16.04.2 LTS, and the DVD is internal, but it also happens on a different laptop where the DVD drive is an external one with USB. I will post the kernel logs the next time it happens.
â neverMind9
May 3 at 13:50
@Gilles It is Ubuntu Studio 16.04.2 LTS, and the DVD is internal, but it also happens on a different laptop where the DVD drive is an external one with USB. I will post the kernel logs the next time it happens.
â neverMind9
May 3 at 13:50
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%2f441368%2fdev-sr0-live-dvd-turns-into-dev-sr1-when-inserting-periphials%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
2
Which live system (distribution, version)? Is the DVD a USB peripheral? It would help to post the kernel logs (all the kernel logs starting when you insert the USB peripheral that messes up the DVD access). Post logs from a session where you don't try to rename the device file, because that can't help but could add problems of its own.
â Gilles
May 2 at 17:29
@Gilles It is Ubuntu Studio 16.04.2 LTS, and the DVD is internal, but it also happens on a different laptop where the DVD drive is an external one with USB. I will post the kernel logs the next time it happens.
â neverMind9
May 3 at 13:50