Removing write protection on udf usb drive
I like many other have this question and can't believe no one has found a way around this.
I have a usb drive that is a UDF format and can not format it was given to me by my company and said i may do with it what i want after i installed the software on my pc.
I have read all the forums possible and cannot find a answer.
I have tried everything I could find on the net...
Only going to paste a few stuff so you guys can have one more go at this.
Device info
>
[ 4328.431126] usb 1-8: Manufacturer: SMI Corporation
[ 4328.431417] usb 1-8: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 4328.431427] usb 1-8: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 4328.432091] usb-storage 1-8:1.0: USB Mass Storage device detected
[ 4328.432520] scsi host7: usb-storage 1-8:1.0
[ 4329.703063] scsi 7:0:0:0: CD-ROM SMI USB DISK 1100 PQ: 0 ANSI: 2
[ 4329.704295] sr 7:0:0:0: [sr1] scsi3-mmc drive: 0x/0x caddy
[ 4329.704616] sr 7:0:0:0: Attached scsi CD-ROM sr1
[ 4329.704777] sr 7:0:0:0: Attached scsi generic sg2 type 5
[ 4329.898756] UDF-fs: INFO Mounting volume 'company app', timestamp 2015/04/02 11:22 (1078)
>
>
>
>
> root@TriGz:/home/trigz# hdparm -r0 /dev/sr1
/dev/sr1:
setting readonly to 0 (off)
readonly = 0 (off)
root@TriGz:/home/trigz# mkdosfs -F 32 -I /dev/sr1
mkfs.fat 3.0.27 (2014-11-12)
mkdosfs: unable to open /dev/sr1: Read-only file system
root@TriGz:/home/trigz# mkfs -t vfat /dev/sr1
mkfs.fat 3.0.27 (2014-11-12)
mkfs.vfat: unable to open /dev/sr1: Read-only file system
root@TriGz:/home/trigz# mkudffs --media-type=hd --blocksize=512 /dev/sr1
Error opening device: Read-only file system
Would be really nice if someone has a way around this issue!
usb format read-only
edited Aug 24 '15 at 13:29
TheWanderer
16.1k113657
asked Aug 24 '15 at 12:57
TriGzTriGz
62
add a comment |
I like many other have this question and can't believe no one has found a way around this.
I have a usb drive that is a UDF format and can not format it was given to me by my company and said i may do with it what i want after i installed the software on my pc.
I have read all the forums possible and cannot find a answer.
I have tried everything I could find on the net...
Only going to paste a few stuff so you guys can have one more go at this.
Device info
>
[ 4328.431126] usb 1-8: Manufacturer: SMI Corporation
[ 4328.431417] usb 1-8: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 4328.431427] usb 1-8: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 4328.432091] usb-storage 1-8:1.0: USB Mass Storage device detected
[ 4328.432520] scsi host7: usb-storage 1-8:1.0
[ 4329.703063] scsi 7:0:0:0: CD-ROM SMI USB DISK 1100 PQ: 0 ANSI: 2
[ 4329.704295] sr 7:0:0:0: [sr1] scsi3-mmc drive: 0x/0x caddy
[ 4329.704616] sr 7:0:0:0: Attached scsi CD-ROM sr1
[ 4329.704777] sr 7:0:0:0: Attached scsi generic sg2 type 5
[ 4329.898756] UDF-fs: INFO Mounting volume 'company app', timestamp 2015/04/02 11:22 (1078)
>
>
>
>
> root@TriGz:/home/trigz# hdparm -r0 /dev/sr1
/dev/sr1:
setting readonly to 0 (off)
readonly = 0 (off)
root@TriGz:/home/trigz# mkdosfs -F 32 -I /dev/sr1
mkfs.fat 3.0.27 (2014-11-12)
mkdosfs: unable to open /dev/sr1: Read-only file system
root@TriGz:/home/trigz# mkfs -t vfat /dev/sr1
mkfs.fat 3.0.27 (2014-11-12)
mkfs.vfat: unable to open /dev/sr1: Read-only file system
root@TriGz:/home/trigz# mkudffs --media-type=hd --blocksize=512 /dev/sr1
Error opening device: Read-only file system
Would be really nice if someone has a way around this issue!
usb format read-only
edited Aug 24 '15 at 13:29
TheWanderer
16.1k113657
asked Aug 24 '15 at 12:57
TriGzTriGz
62
please refr here
– Ravan
Aug 24 '15 at 13:09
add a comment |
I like many other have this question and can't believe no one has found a way around this.
I have a usb drive that is a UDF format and can not format it was given to me by my company and said i may do with it what i want after i installed the software on my pc.
I have read all the forums possible and cannot find a answer.
I have tried everything I could find on the net...
Only going to paste a few stuff so you guys can have one more go at this.
Device info
>
[ 4328.431126] usb 1-8: Manufacturer: SMI Corporation
[ 4328.431417] usb 1-8: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 4328.431427] usb 1-8: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 4328.432091] usb-storage 1-8:1.0: USB Mass Storage device detected
[ 4328.432520] scsi host7: usb-storage 1-8:1.0
[ 4329.703063] scsi 7:0:0:0: CD-ROM SMI USB DISK 1100 PQ: 0 ANSI: 2
[ 4329.704295] sr 7:0:0:0: [sr1] scsi3-mmc drive: 0x/0x caddy
[ 4329.704616] sr 7:0:0:0: Attached scsi CD-ROM sr1
[ 4329.704777] sr 7:0:0:0: Attached scsi generic sg2 type 5
[ 4329.898756] UDF-fs: INFO Mounting volume 'company app', timestamp 2015/04/02 11:22 (1078)
>
>
>
>
> root@TriGz:/home/trigz# hdparm -r0 /dev/sr1
/dev/sr1:
setting readonly to 0 (off)
readonly = 0 (off)
root@TriGz:/home/trigz# mkdosfs -F 32 -I /dev/sr1
mkfs.fat 3.0.27 (2014-11-12)
mkdosfs: unable to open /dev/sr1: Read-only file system
root@TriGz:/home/trigz# mkfs -t vfat /dev/sr1
mkfs.fat 3.0.27 (2014-11-12)
mkfs.vfat: unable to open /dev/sr1: Read-only file system
root@TriGz:/home/trigz# mkudffs --media-type=hd --blocksize=512 /dev/sr1
Error opening device: Read-only file system
Would be really nice if someone has a way around this issue!
usb format read-only
edited Aug 24 '15 at 13:29
TheWanderer
16.1k113657
asked Aug 24 '15 at 12:57
TriGzTriGz
62
I like many other have this question and can't believe no one has found a way around this.
I have a usb drive that is a UDF format and can not format it was given to me by my company and said i may do with it what i want after i installed the software on my pc.
I have read all the forums possible and cannot find a answer.
I have tried everything I could find on the net...
Only going to paste a few stuff so you guys can have one more go at this.
Device info
>
[ 4328.431126] usb 1-8: Manufacturer: SMI Corporation
[ 4328.431417] usb 1-8: ep 0x81 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 4328.431427] usb 1-8: ep 0x2 - rounding interval to 128 microframes, ep desc says 255 microframes
[ 4328.432091] usb-storage 1-8:1.0: USB Mass Storage device detected
[ 4328.432520] scsi host7: usb-storage 1-8:1.0
[ 4329.703063] scsi 7:0:0:0: CD-ROM SMI USB DISK 1100 PQ: 0 ANSI: 2
[ 4329.704295] sr 7:0:0:0: [sr1] scsi3-mmc drive: 0x/0x caddy
[ 4329.704616] sr 7:0:0:0: Attached scsi CD-ROM sr1
[ 4329.704777] sr 7:0:0:0: Attached scsi generic sg2 type 5
[ 4329.898756] UDF-fs: INFO Mounting volume 'company app', timestamp 2015/04/02 11:22 (1078)
>
>
>
>
> root@TriGz:/home/trigz# hdparm -r0 /dev/sr1
/dev/sr1:
setting readonly to 0 (off)
readonly = 0 (off)
root@TriGz:/home/trigz# mkdosfs -F 32 -I /dev/sr1
mkfs.fat 3.0.27 (2014-11-12)
mkdosfs: unable to open /dev/sr1: Read-only file system
root@TriGz:/home/trigz# mkfs -t vfat /dev/sr1
mkfs.fat 3.0.27 (2014-11-12)
mkfs.vfat: unable to open /dev/sr1: Read-only file system
root@TriGz:/home/trigz# mkudffs --media-type=hd --blocksize=512 /dev/sr1
Error opening device: Read-only file system
Would be really nice if someone has a way around this issue!
usb format read-only
usb format read-only
edited Aug 24 '15 at 13:29
TheWanderer
16.1k113657
asked Aug 24 '15 at 12:57
TriGzTriGz
62
edited Aug 24 '15 at 13:29
TheWanderer
16.1k113657
asked Aug 24 '15 at 12:57
TriGzTriGz
62
edited Aug 24 '15 at 13:29
TheWanderer
16.1k113657
edited Aug 24 '15 at 13:29
TheWanderer
16.1k113657
edited Aug 24 '15 at 13:29
TheWanderer
16.1k113657
16.1k113657
asked Aug 24 '15 at 12:57
TriGzTriGz
62
asked Aug 24 '15 at 12:57
TriGzTriGz
62
asked Aug 24 '15 at 12:57
TriGzTriGz
62
62
please refr here
– Ravan
Aug 24 '15 at 13:09
add a comment |
please refr here
– Ravan
Aug 24 '15 at 13:09
please refr here
– Ravan
Aug 24 '15 at 13:09
please refr here
– Ravan
Aug 24 '15 at 13:09
add a comment |
1 Answer
1
active
oldest
votes
Think about it for a minute. When the system has a device mounted (UDF-fs: INFO Mounting volume 'company app', timestamp 2015/04/02 11:22 (1078)). the (in this case) UDF filesystem code reads file indexes, brings the structure of the device into memory, and gets ready to mediate requests for the data. Now, if you format the device, the in-memory copy of UDF metadata is trashed on the "disk" but "valid" in memory. Bad scene!
The simple answer is to umount the USB key first.
answered Aug 24 '15 at 13:35
waltinatorwaltinator
22.6k74169
root@TriGz:~# umount /dev/sr1 umount: /dev/sr1: not mounted root@TriGz:~# fdisk -b 512 /dev/sr1 Welcome to fdisk (util-linux 2.25.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. fdisk: cannot open /dev/sr1: Read-only file system I know it should be unmounted... the write protection is strong with this one... Any other ideas ? Thanks
– TriGz
Aug 25 '15 at 13:22
add a comment |
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',
autoActivateHeartbeat: false,
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
});
}
});
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%2faskubuntu.com%2fquestions%2f665193%2fremoving-write-protection-on-udf-usb-drive%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
Think about it for a minute. When the system has a device mounted (UDF-fs: INFO Mounting volume 'company app', timestamp 2015/04/02 11:22 (1078)). the (in this case) UDF filesystem code reads file indexes, brings the structure of the device into memory, and gets ready to mediate requests for the data. Now, if you format the device, the in-memory copy of UDF metadata is trashed on the "disk" but "valid" in memory. Bad scene!
The simple answer is to umount the USB key first.
answered Aug 24 '15 at 13:35
waltinatorwaltinator
22.6k74169
root@TriGz:~# umount /dev/sr1 umount: /dev/sr1: not mounted root@TriGz:~# fdisk -b 512 /dev/sr1 Welcome to fdisk (util-linux 2.25.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. fdisk: cannot open /dev/sr1: Read-only file system I know it should be unmounted... the write protection is strong with this one... Any other ideas ? Thanks
– TriGz
Aug 25 '15 at 13:22
add a comment |
Think about it for a minute. When the system has a device mounted (UDF-fs: INFO Mounting volume 'company app', timestamp 2015/04/02 11:22 (1078)). the (in this case) UDF filesystem code reads file indexes, brings the structure of the device into memory, and gets ready to mediate requests for the data. Now, if you format the device, the in-memory copy of UDF metadata is trashed on the "disk" but "valid" in memory. Bad scene!
The simple answer is to umount the USB key first.
answered Aug 24 '15 at 13:35
waltinatorwaltinator
22.6k74169
root@TriGz:~# umount /dev/sr1 umount: /dev/sr1: not mounted root@TriGz:~# fdisk -b 512 /dev/sr1 Welcome to fdisk (util-linux 2.25.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. fdisk: cannot open /dev/sr1: Read-only file system I know it should be unmounted... the write protection is strong with this one... Any other ideas ? Thanks
– TriGz
Aug 25 '15 at 13:22
add a comment |
Think about it for a minute. When the system has a device mounted (UDF-fs: INFO Mounting volume 'company app', timestamp 2015/04/02 11:22 (1078)). the (in this case) UDF filesystem code reads file indexes, brings the structure of the device into memory, and gets ready to mediate requests for the data. Now, if you format the device, the in-memory copy of UDF metadata is trashed on the "disk" but "valid" in memory. Bad scene!
The simple answer is to umount the USB key first.
answered Aug 24 '15 at 13:35
waltinatorwaltinator
22.6k74169
Think about it for a minute. When the system has a device mounted (UDF-fs: INFO Mounting volume 'company app', timestamp 2015/04/02 11:22 (1078)). the (in this case) UDF filesystem code reads file indexes, brings the structure of the device into memory, and gets ready to mediate requests for the data. Now, if you format the device, the in-memory copy of UDF metadata is trashed on the "disk" but "valid" in memory. Bad scene!
The simple answer is to umount the USB key first.
answered Aug 24 '15 at 13:35
waltinatorwaltinator
22.6k74169
answered Aug 24 '15 at 13:35
waltinatorwaltinator
22.6k74169
answered Aug 24 '15 at 13:35
waltinatorwaltinator
22.6k74169
answered Aug 24 '15 at 13:35
waltinatorwaltinator
22.6k74169
22.6k74169
root@TriGz:~# umount /dev/sr1 umount: /dev/sr1: not mounted root@TriGz:~# fdisk -b 512 /dev/sr1 Welcome to fdisk (util-linux 2.25.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. fdisk: cannot open /dev/sr1: Read-only file system I know it should be unmounted... the write protection is strong with this one... Any other ideas ? Thanks
– TriGz
Aug 25 '15 at 13:22
add a comment |
root@TriGz:~# umount /dev/sr1 umount: /dev/sr1: not mounted root@TriGz:~# fdisk -b 512 /dev/sr1 Welcome to fdisk (util-linux 2.25.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. fdisk: cannot open /dev/sr1: Read-only file system I know it should be unmounted... the write protection is strong with this one... Any other ideas ? Thanks
– TriGz
Aug 25 '15 at 13:22
root@TriGz:~# umount /dev/sr1 umount: /dev/sr1: not mounted root@TriGz:~# fdisk -b 512 /dev/sr1 Welcome to fdisk (util-linux 2.25.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. fdisk: cannot open /dev/sr1: Read-only file system I know it should be unmounted... the write protection is strong with this one... Any other ideas ? Thanks
– TriGz
Aug 25 '15 at 13:22
root@TriGz:~# umount /dev/sr1 umount: /dev/sr1: not mounted root@TriGz:~# fdisk -b 512 /dev/sr1 Welcome to fdisk (util-linux 2.25.2). Changes will remain in memory only, until you decide to write them. Be careful before using the write command. fdisk: cannot open /dev/sr1: Read-only file system I know it should be unmounted... the write protection is strong with this one... Any other ideas ? Thanks
– TriGz
Aug 25 '15 at 13:22
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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.
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%2faskubuntu.com%2fquestions%2f665193%2fremoving-write-protection-on-udf-usb-drive%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
please refr here
– Ravan
Aug 24 '15 at 13:09