pendrive is visible and 'read only' in DISKS and lsusb, but not visible in df -Th, lsblk and gparted. Thanks











up vote
0
down vote

favorite












from lsblk



root@vishnu:~# lsblk -m
NAME SIZE OWNER GROUP MODE
sr0 1024M root cdrom brw-rw----
sda 931.5G root disk brw-rw----
├─sda2 927.1G root disk brw-rw----
├─sda3 3.9G root disk brw-rw----
└─sda1 512M root disk brw-rw----

root@vishnu:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 05c8:038f Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp.
**Bus 001 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4**
Bus 001 Device 005: ID 04ca:009b Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


In disks, its visible as read only and /dev/sr0 (Read-Only) Not able to format










share|improve this question









New contributor




Vishnu Swarup is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1




    Unplug the "pendrive", type journalctl --follow, plug in the "pendrive". Read messages.
    – waltinator
    2 days ago










  • Thanks. following messages was received Nov 19 12:50:29 vishnu kernel: print_req_error: I/O error, dev sdb, sector 61457536 Nov 19 12:50:29 vishnu kernel: Buffer I/O error on dev sdb, logical block 7682192, async page read
    – Vishnu Swarup
    2 days ago








  • 1




    Either block 768192 is bad, or block number 768192 is out of range, and whichever file points to it is corrupt. Read man badblocks carefully. Beware! You are entering dangerous territory. Think twice before issuing any command.
    – waltinator
    2 days ago















up vote
0
down vote

favorite












from lsblk



root@vishnu:~# lsblk -m
NAME SIZE OWNER GROUP MODE
sr0 1024M root cdrom brw-rw----
sda 931.5G root disk brw-rw----
├─sda2 927.1G root disk brw-rw----
├─sda3 3.9G root disk brw-rw----
└─sda1 512M root disk brw-rw----

root@vishnu:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 05c8:038f Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp.
**Bus 001 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4**
Bus 001 Device 005: ID 04ca:009b Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


In disks, its visible as read only and /dev/sr0 (Read-Only) Not able to format










share|improve this question









New contributor




Vishnu Swarup is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
















  • 1




    Unplug the "pendrive", type journalctl --follow, plug in the "pendrive". Read messages.
    – waltinator
    2 days ago










  • Thanks. following messages was received Nov 19 12:50:29 vishnu kernel: print_req_error: I/O error, dev sdb, sector 61457536 Nov 19 12:50:29 vishnu kernel: Buffer I/O error on dev sdb, logical block 7682192, async page read
    – Vishnu Swarup
    2 days ago








  • 1




    Either block 768192 is bad, or block number 768192 is out of range, and whichever file points to it is corrupt. Read man badblocks carefully. Beware! You are entering dangerous territory. Think twice before issuing any command.
    – waltinator
    2 days ago













up vote
0
down vote

favorite









up vote
0
down vote

favorite











from lsblk



root@vishnu:~# lsblk -m
NAME SIZE OWNER GROUP MODE
sr0 1024M root cdrom brw-rw----
sda 931.5G root disk brw-rw----
├─sda2 927.1G root disk brw-rw----
├─sda3 3.9G root disk brw-rw----
└─sda1 512M root disk brw-rw----

root@vishnu:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 05c8:038f Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp.
**Bus 001 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4**
Bus 001 Device 005: ID 04ca:009b Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


In disks, its visible as read only and /dev/sr0 (Read-Only) Not able to format










share|improve this question









New contributor




Vishnu Swarup is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











from lsblk



root@vishnu:~# lsblk -m
NAME SIZE OWNER GROUP MODE
sr0 1024M root cdrom brw-rw----
sda 931.5G root disk brw-rw----
├─sda2 927.1G root disk brw-rw----
├─sda3 3.9G root disk brw-rw----
└─sda1 512M root disk brw-rw----

root@vishnu:~# lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 05c8:038f Cheng Uei Precision Industry Co., Ltd (Foxlink)
Bus 001 Device 003: ID 0bda:b008 Realtek Semiconductor Corp.
**Bus 001 Device 002: ID 0951:1666 Kingston Technology DataTraveler G4**
Bus 001 Device 005: ID 04ca:009b Lite-On Technology Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub


In disks, its visible as read only and /dev/sr0 (Read-Only) Not able to format







usb format






share|improve this question









New contributor




Vishnu Swarup is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question









New contributor




Vishnu Swarup is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question








edited 2 days ago









waltinator

21.6k74169




21.6k74169






New contributor




Vishnu Swarup is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 2 days ago









Vishnu Swarup

1




1




New contributor




Vishnu Swarup is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Vishnu Swarup is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Vishnu Swarup is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.








  • 1




    Unplug the "pendrive", type journalctl --follow, plug in the "pendrive". Read messages.
    – waltinator
    2 days ago










  • Thanks. following messages was received Nov 19 12:50:29 vishnu kernel: print_req_error: I/O error, dev sdb, sector 61457536 Nov 19 12:50:29 vishnu kernel: Buffer I/O error on dev sdb, logical block 7682192, async page read
    – Vishnu Swarup
    2 days ago








  • 1




    Either block 768192 is bad, or block number 768192 is out of range, and whichever file points to it is corrupt. Read man badblocks carefully. Beware! You are entering dangerous territory. Think twice before issuing any command.
    – waltinator
    2 days ago














  • 1




    Unplug the "pendrive", type journalctl --follow, plug in the "pendrive". Read messages.
    – waltinator
    2 days ago










  • Thanks. following messages was received Nov 19 12:50:29 vishnu kernel: print_req_error: I/O error, dev sdb, sector 61457536 Nov 19 12:50:29 vishnu kernel: Buffer I/O error on dev sdb, logical block 7682192, async page read
    – Vishnu Swarup
    2 days ago








  • 1




    Either block 768192 is bad, or block number 768192 is out of range, and whichever file points to it is corrupt. Read man badblocks carefully. Beware! You are entering dangerous territory. Think twice before issuing any command.
    – waltinator
    2 days ago








1




1




Unplug the "pendrive", type journalctl --follow, plug in the "pendrive". Read messages.
– waltinator
2 days ago




Unplug the "pendrive", type journalctl --follow, plug in the "pendrive". Read messages.
– waltinator
2 days ago












Thanks. following messages was received Nov 19 12:50:29 vishnu kernel: print_req_error: I/O error, dev sdb, sector 61457536 Nov 19 12:50:29 vishnu kernel: Buffer I/O error on dev sdb, logical block 7682192, async page read
– Vishnu Swarup
2 days ago






Thanks. following messages was received Nov 19 12:50:29 vishnu kernel: print_req_error: I/O error, dev sdb, sector 61457536 Nov 19 12:50:29 vishnu kernel: Buffer I/O error on dev sdb, logical block 7682192, async page read
– Vishnu Swarup
2 days ago






1




1




Either block 768192 is bad, or block number 768192 is out of range, and whichever file points to it is corrupt. Read man badblocks carefully. Beware! You are entering dangerous territory. Think twice before issuing any command.
– waltinator
2 days ago




Either block 768192 is bad, or block number 768192 is out of range, and whichever file points to it is corrupt. Read man badblocks carefully. Beware! You are entering dangerous territory. Think twice before issuing any command.
– waltinator
2 days ago















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});


}
});






Vishnu Swarup is a new contributor. Be nice, and check out our Code of Conduct.










 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1094140%2fpendrive-is-visible-and-read-only-in-disks-and-lsusb-but-not-visible-in-df-t%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes








Vishnu Swarup is a new contributor. Be nice, and check out our Code of Conduct.










 

draft saved


draft discarded


















Vishnu Swarup is a new contributor. Be nice, and check out our Code of Conduct.













Vishnu Swarup is a new contributor. Be nice, and check out our Code of Conduct.












Vishnu Swarup is a new contributor. Be nice, and check out our Code of Conduct.















 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1094140%2fpendrive-is-visible-and-read-only-in-disks-and-lsusb-but-not-visible-in-df-t%23new-answer', 'question_page');
}
);

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







Popular posts from this blog

flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

Mangá

 ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕