Mounting SD card on Linux Mint => “mount: special device does not exist”
0
Trying to mount an SD card connected via a USB SD-card reader.
dmesg shows that the USB device is connected and the card is detected
[ 84.696147] usb 1-3.2: new high-speed USB device number 7 using ehci-pci
[ 84.791437] usb 1-3.2: New USB device found, idVendor=8564, idProduct=4000
[ 84.791443] usb 1-3.2: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[ 84.791446] usb 1-3.2: Product: Transcend
[ 84.791450] usb 1-3.2: Manufacturer: TS-RDF5
[ 84.791452] usb 1-3.2: SerialNumber: 000000000039
[ 85.060511] usb-storage 1-3.2:1.0: USB Mass Storage device detected
[ 85.060953] scsi6 : usb-storage 1-3.2:1.0
[ 85.061055] usbcore: registered new interface driver usb-storage
[ 85.089647] usbcore: registered new interface driver uas
[ 86.061604] scsi 6:0:0:0: Direct-Access TS-RDF5 SD Transcend TS37 PQ: 0 ANSI: 6
[ 86.061964] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 86.575707] sd 6:0:0:0: [sdb] 61896704 512-byte logical blocks: (31.6 GB/29.5 GiB)
[ 86.576965] sd 6:0:0:0: [sdb] Write Protect is off
[ 86.576970] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 86.578223] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 86.585246] sdb: [CUMANA/ADFS] sdb1 [ADFS] sdb1
[ 86.590856] sd 6:0:0:0: [sdb] Attached SCSI removable disk
fdisk shows that it is connected, although it complains about some invalid argument:
$ sudo fdisk -l
Disk /dev/sdb: 31.7 GB, 31691112448 bytes
64 heads, 32 sectors/track, 30223 cylinders, total 61896704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00006f83
Device Boot Start End Blocks Id System
/dev/sdb1 2048 2474609 1236281 e W95 FAT16 (LBA)
/dev/sdb2 2482176 61896703 29707264 85 Linux extended
/dev/sdb5 2490368 2605055 57344 c W95 FAT32 (LBA)
/dev/sdb6 2607104 11855871 4624384 83 Linux
/dev/sdb7 11857920 61396991 24769536 83 Linux
fdisk: unable to seek on /dev/sdb1: Invalid argument
When trying to mount, I get the "special device does not exist" message:
$ sudo mount /dev/sdb2 /mnt -v
mount: you didn't specify a filesystem type for /dev/sdb2
I will try all types mentioned in /etc/filesystems or /proc/filesystems
Trying ext3
mount: special device /dev/sdb2 does not exist
Any idea?
linux-mint mount
asked Oct 28 '16 at 21:40
Zoltan FedorZoltan Fedor
1116
add a comment |
0
Trying to mount an SD card connected via a USB SD-card reader.
dmesg shows that the USB device is connected and the card is detected
[ 84.696147] usb 1-3.2: new high-speed USB device number 7 using ehci-pci
[ 84.791437] usb 1-3.2: New USB device found, idVendor=8564, idProduct=4000
[ 84.791443] usb 1-3.2: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[ 84.791446] usb 1-3.2: Product: Transcend
[ 84.791450] usb 1-3.2: Manufacturer: TS-RDF5
[ 84.791452] usb 1-3.2: SerialNumber: 000000000039
[ 85.060511] usb-storage 1-3.2:1.0: USB Mass Storage device detected
[ 85.060953] scsi6 : usb-storage 1-3.2:1.0
[ 85.061055] usbcore: registered new interface driver usb-storage
[ 85.089647] usbcore: registered new interface driver uas
[ 86.061604] scsi 6:0:0:0: Direct-Access TS-RDF5 SD Transcend TS37 PQ: 0 ANSI: 6
[ 86.061964] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 86.575707] sd 6:0:0:0: [sdb] 61896704 512-byte logical blocks: (31.6 GB/29.5 GiB)
[ 86.576965] sd 6:0:0:0: [sdb] Write Protect is off
[ 86.576970] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 86.578223] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 86.585246] sdb: [CUMANA/ADFS] sdb1 [ADFS] sdb1
[ 86.590856] sd 6:0:0:0: [sdb] Attached SCSI removable disk
fdisk shows that it is connected, although it complains about some invalid argument:
$ sudo fdisk -l
Disk /dev/sdb: 31.7 GB, 31691112448 bytes
64 heads, 32 sectors/track, 30223 cylinders, total 61896704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00006f83
Device Boot Start End Blocks Id System
/dev/sdb1 2048 2474609 1236281 e W95 FAT16 (LBA)
/dev/sdb2 2482176 61896703 29707264 85 Linux extended
/dev/sdb5 2490368 2605055 57344 c W95 FAT32 (LBA)
/dev/sdb6 2607104 11855871 4624384 83 Linux
/dev/sdb7 11857920 61396991 24769536 83 Linux
fdisk: unable to seek on /dev/sdb1: Invalid argument
When trying to mount, I get the "special device does not exist" message:
$ sudo mount /dev/sdb2 /mnt -v
mount: you didn't specify a filesystem type for /dev/sdb2
I will try all types mentioned in /etc/filesystems or /proc/filesystems
Trying ext3
mount: special device /dev/sdb2 does not exist
Any idea?
linux-mint mount
asked Oct 28 '16 at 21:40
Zoltan FedorZoltan Fedor
1116
The kernel logs are inconsistent with the fdisk output: they only listsdbas a partition. Are there any more logs about this device, maybe some read errors? Can you try it in another reader?
– Gilles
Oct 29 '16 at 21:18
add a comment |
0
0
0
Trying to mount an SD card connected via a USB SD-card reader.
dmesg shows that the USB device is connected and the card is detected
[ 84.696147] usb 1-3.2: new high-speed USB device number 7 using ehci-pci
[ 84.791437] usb 1-3.2: New USB device found, idVendor=8564, idProduct=4000
[ 84.791443] usb 1-3.2: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[ 84.791446] usb 1-3.2: Product: Transcend
[ 84.791450] usb 1-3.2: Manufacturer: TS-RDF5
[ 84.791452] usb 1-3.2: SerialNumber: 000000000039
[ 85.060511] usb-storage 1-3.2:1.0: USB Mass Storage device detected
[ 85.060953] scsi6 : usb-storage 1-3.2:1.0
[ 85.061055] usbcore: registered new interface driver usb-storage
[ 85.089647] usbcore: registered new interface driver uas
[ 86.061604] scsi 6:0:0:0: Direct-Access TS-RDF5 SD Transcend TS37 PQ: 0 ANSI: 6
[ 86.061964] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 86.575707] sd 6:0:0:0: [sdb] 61896704 512-byte logical blocks: (31.6 GB/29.5 GiB)
[ 86.576965] sd 6:0:0:0: [sdb] Write Protect is off
[ 86.576970] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 86.578223] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 86.585246] sdb: [CUMANA/ADFS] sdb1 [ADFS] sdb1
[ 86.590856] sd 6:0:0:0: [sdb] Attached SCSI removable disk
fdisk shows that it is connected, although it complains about some invalid argument:
$ sudo fdisk -l
Disk /dev/sdb: 31.7 GB, 31691112448 bytes
64 heads, 32 sectors/track, 30223 cylinders, total 61896704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00006f83
Device Boot Start End Blocks Id System
/dev/sdb1 2048 2474609 1236281 e W95 FAT16 (LBA)
/dev/sdb2 2482176 61896703 29707264 85 Linux extended
/dev/sdb5 2490368 2605055 57344 c W95 FAT32 (LBA)
/dev/sdb6 2607104 11855871 4624384 83 Linux
/dev/sdb7 11857920 61396991 24769536 83 Linux
fdisk: unable to seek on /dev/sdb1: Invalid argument
When trying to mount, I get the "special device does not exist" message:
$ sudo mount /dev/sdb2 /mnt -v
mount: you didn't specify a filesystem type for /dev/sdb2
I will try all types mentioned in /etc/filesystems or /proc/filesystems
Trying ext3
mount: special device /dev/sdb2 does not exist
Any idea?
linux-mint mount
asked Oct 28 '16 at 21:40
Zoltan FedorZoltan Fedor
1116
Trying to mount an SD card connected via a USB SD-card reader.
dmesg shows that the USB device is connected and the card is detected
[ 84.696147] usb 1-3.2: new high-speed USB device number 7 using ehci-pci
[ 84.791437] usb 1-3.2: New USB device found, idVendor=8564, idProduct=4000
[ 84.791443] usb 1-3.2: New USB device strings: Mfr=3, Product=4, SerialNumber=5
[ 84.791446] usb 1-3.2: Product: Transcend
[ 84.791450] usb 1-3.2: Manufacturer: TS-RDF5
[ 84.791452] usb 1-3.2: SerialNumber: 000000000039
[ 85.060511] usb-storage 1-3.2:1.0: USB Mass Storage device detected
[ 85.060953] scsi6 : usb-storage 1-3.2:1.0
[ 85.061055] usbcore: registered new interface driver usb-storage
[ 85.089647] usbcore: registered new interface driver uas
[ 86.061604] scsi 6:0:0:0: Direct-Access TS-RDF5 SD Transcend TS37 PQ: 0 ANSI: 6
[ 86.061964] sd 6:0:0:0: Attached scsi generic sg2 type 0
[ 86.575707] sd 6:0:0:0: [sdb] 61896704 512-byte logical blocks: (31.6 GB/29.5 GiB)
[ 86.576965] sd 6:0:0:0: [sdb] Write Protect is off
[ 86.576970] sd 6:0:0:0: [sdb] Mode Sense: 23 00 00 00
[ 86.578223] sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA
[ 86.585246] sdb: [CUMANA/ADFS] sdb1 [ADFS] sdb1
[ 86.590856] sd 6:0:0:0: [sdb] Attached SCSI removable disk
fdisk shows that it is connected, although it complains about some invalid argument:
$ sudo fdisk -l
Disk /dev/sdb: 31.7 GB, 31691112448 bytes
64 heads, 32 sectors/track, 30223 cylinders, total 61896704 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00006f83
Device Boot Start End Blocks Id System
/dev/sdb1 2048 2474609 1236281 e W95 FAT16 (LBA)
/dev/sdb2 2482176 61896703 29707264 85 Linux extended
/dev/sdb5 2490368 2605055 57344 c W95 FAT32 (LBA)
/dev/sdb6 2607104 11855871 4624384 83 Linux
/dev/sdb7 11857920 61396991 24769536 83 Linux
fdisk: unable to seek on /dev/sdb1: Invalid argument
When trying to mount, I get the "special device does not exist" message:
$ sudo mount /dev/sdb2 /mnt -v
mount: you didn't specify a filesystem type for /dev/sdb2
I will try all types mentioned in /etc/filesystems or /proc/filesystems
Trying ext3
mount: special device /dev/sdb2 does not exist
Any idea?
linux-mint mount
linux-mint mount
asked Oct 28 '16 at 21:40
Zoltan FedorZoltan Fedor
1116
asked Oct 28 '16 at 21:40
Zoltan FedorZoltan Fedor
1116
asked Oct 28 '16 at 21:40
Zoltan FedorZoltan Fedor
1116
asked Oct 28 '16 at 21:40
Zoltan FedorZoltan Fedor
1116
asked Oct 28 '16 at 21:40
Zoltan FedorZoltan Fedor
1116
1116
The kernel logs are inconsistent with the fdisk output: they only listsdbas a partition. Are there any more logs about this device, maybe some read errors? Can you try it in another reader?
– Gilles
Oct 29 '16 at 21:18
add a comment |
The kernel logs are inconsistent with the fdisk output: they only listsdbas a partition. Are there any more logs about this device, maybe some read errors? Can you try it in another reader?
– Gilles
Oct 29 '16 at 21:18
The kernel logs are inconsistent with the fdisk output: they only list
sdb as a partition. Are there any more logs about this device, maybe some read errors? Can you try it in another reader?– Gilles
Oct 29 '16 at 21:18
The kernel logs are inconsistent with the fdisk output: they only list
sdb as a partition. Are there any more logs about this device, maybe some read errors? Can you try it in another reader?– Gilles
Oct 29 '16 at 21:18
add a comment |
1 Answer
1
active
oldest
votes
0
The extended partition sdb2 contains partitions 5 and up. So try mounting the other partitions instead (sdb1 and sdb5 if labelled correctly are FAT / msdos, sdb6 and sdb7 are linux, possibly ext3/4).
answered Oct 28 '16 at 21:55
bertlindnerbertlindner
113
I have also tried for sdb6 and sdb7, but they got the same.
– Zoltan Fedor
Oct 28 '16 at 22:08
Are you positive there are valid filesystems on there? It seems an atypical partition layout for a USB stick - maybe it has just been someones fdisk experiment? The symptoms might fit with partitions that were created but without creating a filesystem on there.
– bertlindner
Oct 28 '16 at 22:15
The filesystem certainly was there, as this SD card was used in a raspberry pi earlier, but it is possible that it got damaged. That is exactly what I am trying to figure out. Basically what I would need to know whether there is any other explanation to this mounting error other than the SD card being damaged.
– Zoltan Fedor
Oct 28 '16 at 22:50
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%2f319637%2fmounting-sd-card-on-linux-mint-mount-special-device-does-not-exist%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
The extended partition sdb2 contains partitions 5 and up. So try mounting the other partitions instead (sdb1 and sdb5 if labelled correctly are FAT / msdos, sdb6 and sdb7 are linux, possibly ext3/4).
answered Oct 28 '16 at 21:55
bertlindnerbertlindner
113
I have also tried for sdb6 and sdb7, but they got the same.
– Zoltan Fedor
Oct 28 '16 at 22:08
Are you positive there are valid filesystems on there? It seems an atypical partition layout for a USB stick - maybe it has just been someones fdisk experiment? The symptoms might fit with partitions that were created but without creating a filesystem on there.
– bertlindner
Oct 28 '16 at 22:15
The filesystem certainly was there, as this SD card was used in a raspberry pi earlier, but it is possible that it got damaged. That is exactly what I am trying to figure out. Basically what I would need to know whether there is any other explanation to this mounting error other than the SD card being damaged.
– Zoltan Fedor
Oct 28 '16 at 22:50
add a comment |
0
The extended partition sdb2 contains partitions 5 and up. So try mounting the other partitions instead (sdb1 and sdb5 if labelled correctly are FAT / msdos, sdb6 and sdb7 are linux, possibly ext3/4).
answered Oct 28 '16 at 21:55
bertlindnerbertlindner
113
I have also tried for sdb6 and sdb7, but they got the same.
– Zoltan Fedor
Oct 28 '16 at 22:08
Are you positive there are valid filesystems on there? It seems an atypical partition layout for a USB stick - maybe it has just been someones fdisk experiment? The symptoms might fit with partitions that were created but without creating a filesystem on there.
– bertlindner
Oct 28 '16 at 22:15
The filesystem certainly was there, as this SD card was used in a raspberry pi earlier, but it is possible that it got damaged. That is exactly what I am trying to figure out. Basically what I would need to know whether there is any other explanation to this mounting error other than the SD card being damaged.
– Zoltan Fedor
Oct 28 '16 at 22:50
add a comment |
0
0
0
The extended partition sdb2 contains partitions 5 and up. So try mounting the other partitions instead (sdb1 and sdb5 if labelled correctly are FAT / msdos, sdb6 and sdb7 are linux, possibly ext3/4).
answered Oct 28 '16 at 21:55
bertlindnerbertlindner
113
The extended partition sdb2 contains partitions 5 and up. So try mounting the other partitions instead (sdb1 and sdb5 if labelled correctly are FAT / msdos, sdb6 and sdb7 are linux, possibly ext3/4).
answered Oct 28 '16 at 21:55
bertlindnerbertlindner
113
answered Oct 28 '16 at 21:55
bertlindnerbertlindner
113
answered Oct 28 '16 at 21:55
bertlindnerbertlindner
113
answered Oct 28 '16 at 21:55
bertlindnerbertlindner
113
113
I have also tried for sdb6 and sdb7, but they got the same.
– Zoltan Fedor
Oct 28 '16 at 22:08
Are you positive there are valid filesystems on there? It seems an atypical partition layout for a USB stick - maybe it has just been someones fdisk experiment? The symptoms might fit with partitions that were created but without creating a filesystem on there.
– bertlindner
Oct 28 '16 at 22:15
The filesystem certainly was there, as this SD card was used in a raspberry pi earlier, but it is possible that it got damaged. That is exactly what I am trying to figure out. Basically what I would need to know whether there is any other explanation to this mounting error other than the SD card being damaged.
– Zoltan Fedor
Oct 28 '16 at 22:50
add a comment |
I have also tried for sdb6 and sdb7, but they got the same.
– Zoltan Fedor
Oct 28 '16 at 22:08
Are you positive there are valid filesystems on there? It seems an atypical partition layout for a USB stick - maybe it has just been someones fdisk experiment? The symptoms might fit with partitions that were created but without creating a filesystem on there.
– bertlindner
Oct 28 '16 at 22:15
The filesystem certainly was there, as this SD card was used in a raspberry pi earlier, but it is possible that it got damaged. That is exactly what I am trying to figure out. Basically what I would need to know whether there is any other explanation to this mounting error other than the SD card being damaged.
– Zoltan Fedor
Oct 28 '16 at 22:50
I have also tried for sdb6 and sdb7, but they got the same.
– Zoltan Fedor
Oct 28 '16 at 22:08
I have also tried for sdb6 and sdb7, but they got the same.
– Zoltan Fedor
Oct 28 '16 at 22:08
Are you positive there are valid filesystems on there? It seems an atypical partition layout for a USB stick - maybe it has just been someones fdisk experiment? The symptoms might fit with partitions that were created but without creating a filesystem on there.
– bertlindner
Oct 28 '16 at 22:15
Are you positive there are valid filesystems on there? It seems an atypical partition layout for a USB stick - maybe it has just been someones fdisk experiment? The symptoms might fit with partitions that were created but without creating a filesystem on there.
– bertlindner
Oct 28 '16 at 22:15
The filesystem certainly was there, as this SD card was used in a raspberry pi earlier, but it is possible that it got damaged. That is exactly what I am trying to figure out. Basically what I would need to know whether there is any other explanation to this mounting error other than the SD card being damaged.
– Zoltan Fedor
Oct 28 '16 at 22:50
The filesystem certainly was there, as this SD card was used in a raspberry pi earlier, but it is possible that it got damaged. That is exactly what I am trying to figure out. Basically what I would need to know whether there is any other explanation to this mounting error other than the SD card being damaged.
– Zoltan Fedor
Oct 28 '16 at 22:50
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.
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%2f319637%2fmounting-sd-card-on-linux-mint-mount-special-device-does-not-exist%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
The kernel logs are inconsistent with the fdisk output: they only list
sdbas a partition. Are there any more logs about this device, maybe some read errors? Can you try it in another reader?– Gilles
Oct 29 '16 at 21:18