Can't mount device
1
I can't mount my e-reader. Here's what I tried:
I connected my e-reader to the computer via usb. dmesg tells me the OS (debian 9) recognized the device and assigned /dev/sdb and /dev/sdc to it:
usb 1-6: new high-speed USB device number 6 using ehci-pci
[ 2023.922301] usb 1-6: New USB device found, idVendor=15a2, idProduct=0c01
[ 2023.922306] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2023.922309] usb 1-6: Product: 623
[ 2023.922312] usb 1-6: Manufacturer: Papyre
[ 2023.922315] usb 1-6: SerialNumber: 0123456789ABCDEF
[ 2023.930149] usb-storage 1-6:1.0: USB Mass Storage device detected
[ 2023.930323] scsi host4: usb-storage 1-6:1.0
[ 2024.961442] scsi 4:0:0:0: Direct-Access Papyre 623 0100 PQ: 0 ANSI: 2
[ 2024.963410] scsi 4:0:0:1: Direct-Access Papyre 623 0100 PQ: 0 ANSI: 2
[ 2024.964818] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 2024.966505] sd 4:0:0:1: Attached scsi generic sg3 type 0
[ 2025.001429] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 2025.035684] sd 4:0:0:1: [sdc] Attached SCSI removable disk
I tried to mount /dev/sdb with mount /dev/sdb /media/ereader getting this error:
mount: no se ha encontrado ningún medio en /dev/sdb
Which roughly translates to:
mount: no medium found in /dev/sdb
I also tried with the -t vfat option, and repeated the process with /dev/sdc, with the same result.
In case you ask, here's the output of sg_map:
/dev/sg2 /dev/sdb
/dev/sg3 /dev/sdc
And fdisk -l /dev/sdb (my own translation):
fdisk: can't open /dev/sdb: Medium not found
Output from lsblk -f:
NAME FSTYPE LABEL UUID MOUNTPOINT
fd0
sda
├─sda1 ext4 8110f71a-b0eb-4968-bdf2-2c398a4e056c /
├─sda2 ext4 09be5f99-740b-4892-8607-a87d27953110
├─sda3 ext4 linux_archivos 16a84f16-bca0-42e6-810e-34851fbcb0a1 /media/linux_archivos
└─sda4 swap ea2997b9-6401-424b-a5ea-487f6996c56f [SWAP]
sr0
Output from file /dev/sdb:
/dev/sdb: block special (8/16)
Output from file /dev/sdc:
/dev/sdc: block special (8/32)
Output from file -s /dev/sdb:
/dev/sdb: writable, no read permission
Output from file -s /dev/sdc:
/dev/sdc: writable, no read permission
debian mount usb-device
asked Nov 12 '17 at 22:01
nico
63
add a comment |
1
I can't mount my e-reader. Here's what I tried:
I connected my e-reader to the computer via usb. dmesg tells me the OS (debian 9) recognized the device and assigned /dev/sdb and /dev/sdc to it:
usb 1-6: new high-speed USB device number 6 using ehci-pci
[ 2023.922301] usb 1-6: New USB device found, idVendor=15a2, idProduct=0c01
[ 2023.922306] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2023.922309] usb 1-6: Product: 623
[ 2023.922312] usb 1-6: Manufacturer: Papyre
[ 2023.922315] usb 1-6: SerialNumber: 0123456789ABCDEF
[ 2023.930149] usb-storage 1-6:1.0: USB Mass Storage device detected
[ 2023.930323] scsi host4: usb-storage 1-6:1.0
[ 2024.961442] scsi 4:0:0:0: Direct-Access Papyre 623 0100 PQ: 0 ANSI: 2
[ 2024.963410] scsi 4:0:0:1: Direct-Access Papyre 623 0100 PQ: 0 ANSI: 2
[ 2024.964818] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 2024.966505] sd 4:0:0:1: Attached scsi generic sg3 type 0
[ 2025.001429] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 2025.035684] sd 4:0:0:1: [sdc] Attached SCSI removable disk
I tried to mount /dev/sdb with mount /dev/sdb /media/ereader getting this error:
mount: no se ha encontrado ningún medio en /dev/sdb
Which roughly translates to:
mount: no medium found in /dev/sdb
I also tried with the -t vfat option, and repeated the process with /dev/sdc, with the same result.
In case you ask, here's the output of sg_map:
/dev/sg2 /dev/sdb
/dev/sg3 /dev/sdc
And fdisk -l /dev/sdb (my own translation):
fdisk: can't open /dev/sdb: Medium not found
Output from lsblk -f:
NAME FSTYPE LABEL UUID MOUNTPOINT
fd0
sda
├─sda1 ext4 8110f71a-b0eb-4968-bdf2-2c398a4e056c /
├─sda2 ext4 09be5f99-740b-4892-8607-a87d27953110
├─sda3 ext4 linux_archivos 16a84f16-bca0-42e6-810e-34851fbcb0a1 /media/linux_archivos
└─sda4 swap ea2997b9-6401-424b-a5ea-487f6996c56f [SWAP]
sr0
Output from file /dev/sdb:
/dev/sdb: block special (8/16)
Output from file /dev/sdc:
/dev/sdc: block special (8/32)
Output from file -s /dev/sdb:
/dev/sdb: writable, no read permission
Output from file -s /dev/sdc:
/dev/sdc: writable, no read permission
debian mount usb-device
asked Nov 12 '17 at 22:01
nico
63
So you get two USB storage devices, but no partition table, and Linux can't identify any file system. Please edit question with output offile /dev/sdbandfile /dev/sdc(sometimesfilecan recognize formats the kernel can't). Last resort ishexdump -C /dev/sdb | less(orsdc), and see if you can make sense of it.
– dirkt
Nov 13 '17 at 7:49
What doeslsblk -fgive you?
– Mioriin
Nov 13 '17 at 17:02
Please add the-soption to your file calls, likefile -s /dev/sdc. You may need to run this as root, depending on permissions. Doesn't your ereader device export its empty memory card slot assdb? That would explain the "no medium" error messages.
– Ferenc Wágner
Nov 22 '17 at 23:37
add a comment |
1
1
1
I can't mount my e-reader. Here's what I tried:
I connected my e-reader to the computer via usb. dmesg tells me the OS (debian 9) recognized the device and assigned /dev/sdb and /dev/sdc to it:
usb 1-6: new high-speed USB device number 6 using ehci-pci
[ 2023.922301] usb 1-6: New USB device found, idVendor=15a2, idProduct=0c01
[ 2023.922306] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2023.922309] usb 1-6: Product: 623
[ 2023.922312] usb 1-6: Manufacturer: Papyre
[ 2023.922315] usb 1-6: SerialNumber: 0123456789ABCDEF
[ 2023.930149] usb-storage 1-6:1.0: USB Mass Storage device detected
[ 2023.930323] scsi host4: usb-storage 1-6:1.0
[ 2024.961442] scsi 4:0:0:0: Direct-Access Papyre 623 0100 PQ: 0 ANSI: 2
[ 2024.963410] scsi 4:0:0:1: Direct-Access Papyre 623 0100 PQ: 0 ANSI: 2
[ 2024.964818] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 2024.966505] sd 4:0:0:1: Attached scsi generic sg3 type 0
[ 2025.001429] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 2025.035684] sd 4:0:0:1: [sdc] Attached SCSI removable disk
I tried to mount /dev/sdb with mount /dev/sdb /media/ereader getting this error:
mount: no se ha encontrado ningún medio en /dev/sdb
Which roughly translates to:
mount: no medium found in /dev/sdb
I also tried with the -t vfat option, and repeated the process with /dev/sdc, with the same result.
In case you ask, here's the output of sg_map:
/dev/sg2 /dev/sdb
/dev/sg3 /dev/sdc
And fdisk -l /dev/sdb (my own translation):
fdisk: can't open /dev/sdb: Medium not found
Output from lsblk -f:
NAME FSTYPE LABEL UUID MOUNTPOINT
fd0
sda
├─sda1 ext4 8110f71a-b0eb-4968-bdf2-2c398a4e056c /
├─sda2 ext4 09be5f99-740b-4892-8607-a87d27953110
├─sda3 ext4 linux_archivos 16a84f16-bca0-42e6-810e-34851fbcb0a1 /media/linux_archivos
└─sda4 swap ea2997b9-6401-424b-a5ea-487f6996c56f [SWAP]
sr0
Output from file /dev/sdb:
/dev/sdb: block special (8/16)
Output from file /dev/sdc:
/dev/sdc: block special (8/32)
Output from file -s /dev/sdb:
/dev/sdb: writable, no read permission
Output from file -s /dev/sdc:
/dev/sdc: writable, no read permission
debian mount usb-device
asked Nov 12 '17 at 22:01
nico
63
I can't mount my e-reader. Here's what I tried:
I connected my e-reader to the computer via usb. dmesg tells me the OS (debian 9) recognized the device and assigned /dev/sdb and /dev/sdc to it:
usb 1-6: new high-speed USB device number 6 using ehci-pci
[ 2023.922301] usb 1-6: New USB device found, idVendor=15a2, idProduct=0c01
[ 2023.922306] usb 1-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2023.922309] usb 1-6: Product: 623
[ 2023.922312] usb 1-6: Manufacturer: Papyre
[ 2023.922315] usb 1-6: SerialNumber: 0123456789ABCDEF
[ 2023.930149] usb-storage 1-6:1.0: USB Mass Storage device detected
[ 2023.930323] scsi host4: usb-storage 1-6:1.0
[ 2024.961442] scsi 4:0:0:0: Direct-Access Papyre 623 0100 PQ: 0 ANSI: 2
[ 2024.963410] scsi 4:0:0:1: Direct-Access Papyre 623 0100 PQ: 0 ANSI: 2
[ 2024.964818] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 2024.966505] sd 4:0:0:1: Attached scsi generic sg3 type 0
[ 2025.001429] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 2025.035684] sd 4:0:0:1: [sdc] Attached SCSI removable disk
I tried to mount /dev/sdb with mount /dev/sdb /media/ereader getting this error:
mount: no se ha encontrado ningún medio en /dev/sdb
Which roughly translates to:
mount: no medium found in /dev/sdb
I also tried with the -t vfat option, and repeated the process with /dev/sdc, with the same result.
In case you ask, here's the output of sg_map:
/dev/sg2 /dev/sdb
/dev/sg3 /dev/sdc
And fdisk -l /dev/sdb (my own translation):
fdisk: can't open /dev/sdb: Medium not found
Output from lsblk -f:
NAME FSTYPE LABEL UUID MOUNTPOINT
fd0
sda
├─sda1 ext4 8110f71a-b0eb-4968-bdf2-2c398a4e056c /
├─sda2 ext4 09be5f99-740b-4892-8607-a87d27953110
├─sda3 ext4 linux_archivos 16a84f16-bca0-42e6-810e-34851fbcb0a1 /media/linux_archivos
└─sda4 swap ea2997b9-6401-424b-a5ea-487f6996c56f [SWAP]
sr0
Output from file /dev/sdb:
/dev/sdb: block special (8/16)
Output from file /dev/sdc:
/dev/sdc: block special (8/32)
Output from file -s /dev/sdb:
/dev/sdb: writable, no read permission
Output from file -s /dev/sdc:
/dev/sdc: writable, no read permission
debian mount usb-device
debian mount usb-device
asked Nov 12 '17 at 22:01
nico
63
asked Nov 12 '17 at 22:01
nico
63
edited Nov 26 '17 at 18:33
asked Nov 12 '17 at 22:01
nico
63
asked Nov 12 '17 at 22:01
nico
63
asked Nov 12 '17 at 22:01
nico
63
63
So you get two USB storage devices, but no partition table, and Linux can't identify any file system. Please edit question with output offile /dev/sdbandfile /dev/sdc(sometimesfilecan recognize formats the kernel can't). Last resort ishexdump -C /dev/sdb | less(orsdc), and see if you can make sense of it.
– dirkt
Nov 13 '17 at 7:49
What doeslsblk -fgive you?
– Mioriin
Nov 13 '17 at 17:02
Please add the-soption to your file calls, likefile -s /dev/sdc. You may need to run this as root, depending on permissions. Doesn't your ereader device export its empty memory card slot assdb? That would explain the "no medium" error messages.
– Ferenc Wágner
Nov 22 '17 at 23:37
add a comment |
So you get two USB storage devices, but no partition table, and Linux can't identify any file system. Please edit question with output offile /dev/sdbandfile /dev/sdc(sometimesfilecan recognize formats the kernel can't). Last resort ishexdump -C /dev/sdb | less(orsdc), and see if you can make sense of it.
– dirkt
Nov 13 '17 at 7:49
What doeslsblk -fgive you?
– Mioriin
Nov 13 '17 at 17:02
Please add the-soption to your file calls, likefile -s /dev/sdc. You may need to run this as root, depending on permissions. Doesn't your ereader device export its empty memory card slot assdb? That would explain the "no medium" error messages.
– Ferenc Wágner
Nov 22 '17 at 23:37
So you get two USB storage devices, but no partition table, and Linux can't identify any file system. Please edit question with output of
file /dev/sdb and file /dev/sdc (sometimes file can recognize formats the kernel can't). Last resort is hexdump -C /dev/sdb | less (or sdc), and see if you can make sense of it.– dirkt
Nov 13 '17 at 7:49
So you get two USB storage devices, but no partition table, and Linux can't identify any file system. Please edit question with output of
file /dev/sdb and file /dev/sdc (sometimes file can recognize formats the kernel can't). Last resort is hexdump -C /dev/sdb | less (or sdc), and see if you can make sense of it.– dirkt
Nov 13 '17 at 7:49
What does
lsblk -f give you?– Mioriin
Nov 13 '17 at 17:02
What does
lsblk -f give you?– Mioriin
Nov 13 '17 at 17:02
Please add the
-s option to your file calls, like file -s /dev/sdc. You may need to run this as root, depending on permissions. Doesn't your ereader device export its empty memory card slot as sdb? That would explain the "no medium" error messages.– Ferenc Wágner
Nov 22 '17 at 23:37
Please add the
-s option to your file calls, like file -s /dev/sdc. You may need to run this as root, depending on permissions. Doesn't your ereader device export its empty memory card slot as sdb? That would explain the "no medium" error messages.– Ferenc Wágner
Nov 22 '17 at 23:37
add a comment |
2 Answers
2
active
oldest
votes
0
- check common fdisk -l
- what about sdc ?
- don't forget to check device status simultaneously on you e-reader itself (e.g. Data transfer/Charging/Media Access or so).
- needless to say root privilege is required
answered Nov 12 '17 at 22:48
Dr. Alexander
8113
fdisk -ldoesn't mention sdb nor sdc. Tried commands in the question for sdc, same results. All commands were run with root privilege. The e-reader seems to be stuck, can't even turn it off.
– nico
Nov 12 '17 at 23:14
add a comment |
0
I had the same problem. At the end I discovered I was connecting my old e-reader to the SS-USB port. I changed it to the only simple USB port my laptop has and it worked like a charm!
Hope this helps.
answered Dec 20 '18 at 15:59
Felipe BM
1
1
Welcome to U&L! This doesn't sound like it would fix the problem described, but without knowing the exact hardware it's difficult to be certain. Were you definitely getting the same symptoms that the OP had (devices created OK, then the "no medium found" error) before applying this fix?
– JigglyNaga
Dec 20 '18 at 16:49
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f404120%2fcant-mount-device%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
0
- check common fdisk -l
- what about sdc ?
- don't forget to check device status simultaneously on you e-reader itself (e.g. Data transfer/Charging/Media Access or so).
- needless to say root privilege is required
answered Nov 12 '17 at 22:48
Dr. Alexander
8113
fdisk -ldoesn't mention sdb nor sdc. Tried commands in the question for sdc, same results. All commands were run with root privilege. The e-reader seems to be stuck, can't even turn it off.
– nico
Nov 12 '17 at 23:14
add a comment |
0
- check common fdisk -l
- what about sdc ?
- don't forget to check device status simultaneously on you e-reader itself (e.g. Data transfer/Charging/Media Access or so).
- needless to say root privilege is required
answered Nov 12 '17 at 22:48
Dr. Alexander
8113
fdisk -ldoesn't mention sdb nor sdc. Tried commands in the question for sdc, same results. All commands were run with root privilege. The e-reader seems to be stuck, can't even turn it off.
– nico
Nov 12 '17 at 23:14
add a comment |
0
0
0
- check common fdisk -l
- what about sdc ?
- don't forget to check device status simultaneously on you e-reader itself (e.g. Data transfer/Charging/Media Access or so).
- needless to say root privilege is required
answered Nov 12 '17 at 22:48
Dr. Alexander
8113
- check common fdisk -l
- what about sdc ?
- don't forget to check device status simultaneously on you e-reader itself (e.g. Data transfer/Charging/Media Access or so).
- needless to say root privilege is required
answered Nov 12 '17 at 22:48
Dr. Alexander
8113
edited Nov 12 '17 at 22:56
answered Nov 12 '17 at 22:48
Dr. Alexander
8113
answered Nov 12 '17 at 22:48
Dr. Alexander
8113
answered Nov 12 '17 at 22:48
Dr. Alexander
8113
8113
fdisk -ldoesn't mention sdb nor sdc. Tried commands in the question for sdc, same results. All commands were run with root privilege. The e-reader seems to be stuck, can't even turn it off.
– nico
Nov 12 '17 at 23:14
add a comment |
fdisk -ldoesn't mention sdb nor sdc. Tried commands in the question for sdc, same results. All commands were run with root privilege. The e-reader seems to be stuck, can't even turn it off.
– nico
Nov 12 '17 at 23:14
fdisk -l doesn't mention sdb nor sdc. Tried commands in the question for sdc, same results. All commands were run with root privilege. The e-reader seems to be stuck, can't even turn it off.– nico
Nov 12 '17 at 23:14
fdisk -l doesn't mention sdb nor sdc. Tried commands in the question for sdc, same results. All commands were run with root privilege. The e-reader seems to be stuck, can't even turn it off.– nico
Nov 12 '17 at 23:14
add a comment |
0
I had the same problem. At the end I discovered I was connecting my old e-reader to the SS-USB port. I changed it to the only simple USB port my laptop has and it worked like a charm!
Hope this helps.
answered Dec 20 '18 at 15:59
Felipe BM
1
1
Welcome to U&L! This doesn't sound like it would fix the problem described, but without knowing the exact hardware it's difficult to be certain. Were you definitely getting the same symptoms that the OP had (devices created OK, then the "no medium found" error) before applying this fix?
– JigglyNaga
Dec 20 '18 at 16:49
add a comment |
0
I had the same problem. At the end I discovered I was connecting my old e-reader to the SS-USB port. I changed it to the only simple USB port my laptop has and it worked like a charm!
Hope this helps.
answered Dec 20 '18 at 15:59
Felipe BM
1
1
Welcome to U&L! This doesn't sound like it would fix the problem described, but without knowing the exact hardware it's difficult to be certain. Were you definitely getting the same symptoms that the OP had (devices created OK, then the "no medium found" error) before applying this fix?
– JigglyNaga
Dec 20 '18 at 16:49
add a comment |
0
0
0
I had the same problem. At the end I discovered I was connecting my old e-reader to the SS-USB port. I changed it to the only simple USB port my laptop has and it worked like a charm!
Hope this helps.
answered Dec 20 '18 at 15:59
Felipe BM
1
I had the same problem. At the end I discovered I was connecting my old e-reader to the SS-USB port. I changed it to the only simple USB port my laptop has and it worked like a charm!
Hope this helps.
answered Dec 20 '18 at 15:59
Felipe BM
1
answered Dec 20 '18 at 15:59
Felipe BM
1
answered Dec 20 '18 at 15:59
Felipe BM
1
answered Dec 20 '18 at 15:59
Felipe BM
1
1
1
Welcome to U&L! This doesn't sound like it would fix the problem described, but without knowing the exact hardware it's difficult to be certain. Were you definitely getting the same symptoms that the OP had (devices created OK, then the "no medium found" error) before applying this fix?
– JigglyNaga
Dec 20 '18 at 16:49
add a comment |
1
Welcome to U&L! This doesn't sound like it would fix the problem described, but without knowing the exact hardware it's difficult to be certain. Were you definitely getting the same symptoms that the OP had (devices created OK, then the "no medium found" error) before applying this fix?
– JigglyNaga
Dec 20 '18 at 16:49
1
1
Welcome to U&L! This doesn't sound like it would fix the problem described, but without knowing the exact hardware it's difficult to be certain. Were you definitely getting the same symptoms that the OP had (devices created OK, then the "no medium found" error) before applying this fix?
– JigglyNaga
Dec 20 '18 at 16:49
Welcome to U&L! This doesn't sound like it would fix the problem described, but without knowing the exact hardware it's difficult to be certain. Were you definitely getting the same symptoms that the OP had (devices created OK, then the "no medium found" error) before applying this fix?
– JigglyNaga
Dec 20 '18 at 16:49
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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
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
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f404120%2fcant-mount-device%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
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
Required, but never shown
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
Required, but never shown
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
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
So you get two USB storage devices, but no partition table, and Linux can't identify any file system. Please edit question with output of
file /dev/sdbandfile /dev/sdc(sometimesfilecan recognize formats the kernel can't). Last resort ishexdump -C /dev/sdb | less(orsdc), and see if you can make sense of it.– dirkt
Nov 13 '17 at 7:49
What does
lsblk -fgive you?– Mioriin
Nov 13 '17 at 17:02
Please add the
-soption to your file calls, likefile -s /dev/sdc. You may need to run this as root, depending on permissions. Doesn't your ereader device export its empty memory card slot assdb? That would explain the "no medium" error messages.– Ferenc Wágner
Nov 22 '17 at 23:37