The file casper/filesystem.squashfs is corrupt
I tried burning Lubuntu 12.04 to a CD-RW with Xfburn and braseo, but it keeps be corrupted. I tried to check my hashes but:
Lubuntu 12.04 i386$ md5sum -c md5sum.txt | grep -v "OK$"
md5sum: ./casper/filesystem.squashfs: Input/output error
./casper/filesystem.squashfs: FAILED open or read
md5sum: WARNING: 1 listed file could not be read
My disc has enough room. Also, the iso's checksum is fine.
~/Desktop$ md5sum -c MD5SUMS.txt
md5sum: lubuntu-12.04-alternate-amd64+mac.iso: No such file or directory
lubuntu-12.04-alternate-amd64+mac.iso: FAILED open or read
md5sum: lubuntu-12.04-alternate-amd64.iso: No such file or directory
lubuntu-12.04-alternate-amd64.iso: FAILED open or read
md5sum: lubuntu-12.04-alternate-i386.iso: No such file or directory
lubuntu-12.04-alternate-i386.iso: FAILED open or read
md5sum: lubuntu-12.04-alternate-powerpc.iso: No such file or directory
lubuntu-12.04-alternate-powerpc.iso: FAILED open or read
md5sum: lubuntu-12.04-desktop-amd64+mac.iso: No such file or directory
lubuntu-12.04-desktop-amd64+mac.iso: FAILED open or read
md5sum: lubuntu-12.04-desktop-amd64.iso: No such file or directory
lubuntu-12.04-desktop-amd64.iso: FAILED open or read
lubuntu-12.04-desktop-i386.iso: OK <--------------------------------This is the file
md5sum: lubuntu-12.04-desktop-powerpc.iso: No such file or directory
lubuntu-12.04-desktop-powerpc.iso: FAILED open or read
md5sum: WARNING: 7 listed files could not be read
What is going on?
iso
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I tried burning Lubuntu 12.04 to a CD-RW with Xfburn and braseo, but it keeps be corrupted. I tried to check my hashes but:
Lubuntu 12.04 i386$ md5sum -c md5sum.txt | grep -v "OK$"
md5sum: ./casper/filesystem.squashfs: Input/output error
./casper/filesystem.squashfs: FAILED open or read
md5sum: WARNING: 1 listed file could not be read
My disc has enough room. Also, the iso's checksum is fine.
~/Desktop$ md5sum -c MD5SUMS.txt
md5sum: lubuntu-12.04-alternate-amd64+mac.iso: No such file or directory
lubuntu-12.04-alternate-amd64+mac.iso: FAILED open or read
md5sum: lubuntu-12.04-alternate-amd64.iso: No such file or directory
lubuntu-12.04-alternate-amd64.iso: FAILED open or read
md5sum: lubuntu-12.04-alternate-i386.iso: No such file or directory
lubuntu-12.04-alternate-i386.iso: FAILED open or read
md5sum: lubuntu-12.04-alternate-powerpc.iso: No such file or directory
lubuntu-12.04-alternate-powerpc.iso: FAILED open or read
md5sum: lubuntu-12.04-desktop-amd64+mac.iso: No such file or directory
lubuntu-12.04-desktop-amd64+mac.iso: FAILED open or read
md5sum: lubuntu-12.04-desktop-amd64.iso: No such file or directory
lubuntu-12.04-desktop-amd64.iso: FAILED open or read
lubuntu-12.04-desktop-i386.iso: OK <--------------------------------This is the file
md5sum: lubuntu-12.04-desktop-powerpc.iso: No such file or directory
lubuntu-12.04-desktop-powerpc.iso: FAILED open or read
md5sum: WARNING: 7 listed files could not be read
What is going on?
iso
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I tried burning Lubuntu 12.04 to a CD-RW with Xfburn and braseo, but it keeps be corrupted. I tried to check my hashes but:
Lubuntu 12.04 i386$ md5sum -c md5sum.txt | grep -v "OK$"
md5sum: ./casper/filesystem.squashfs: Input/output error
./casper/filesystem.squashfs: FAILED open or read
md5sum: WARNING: 1 listed file could not be read
My disc has enough room. Also, the iso's checksum is fine.
~/Desktop$ md5sum -c MD5SUMS.txt
md5sum: lubuntu-12.04-alternate-amd64+mac.iso: No such file or directory
lubuntu-12.04-alternate-amd64+mac.iso: FAILED open or read
md5sum: lubuntu-12.04-alternate-amd64.iso: No such file or directory
lubuntu-12.04-alternate-amd64.iso: FAILED open or read
md5sum: lubuntu-12.04-alternate-i386.iso: No such file or directory
lubuntu-12.04-alternate-i386.iso: FAILED open or read
md5sum: lubuntu-12.04-alternate-powerpc.iso: No such file or directory
lubuntu-12.04-alternate-powerpc.iso: FAILED open or read
md5sum: lubuntu-12.04-desktop-amd64+mac.iso: No such file or directory
lubuntu-12.04-desktop-amd64+mac.iso: FAILED open or read
md5sum: lubuntu-12.04-desktop-amd64.iso: No such file or directory
lubuntu-12.04-desktop-amd64.iso: FAILED open or read
lubuntu-12.04-desktop-i386.iso: OK <--------------------------------This is the file
md5sum: lubuntu-12.04-desktop-powerpc.iso: No such file or directory
lubuntu-12.04-desktop-powerpc.iso: FAILED open or read
md5sum: WARNING: 7 listed files could not be read
What is going on?
iso
I tried burning Lubuntu 12.04 to a CD-RW with Xfburn and braseo, but it keeps be corrupted. I tried to check my hashes but:
Lubuntu 12.04 i386$ md5sum -c md5sum.txt | grep -v "OK$"
md5sum: ./casper/filesystem.squashfs: Input/output error
./casper/filesystem.squashfs: FAILED open or read
md5sum: WARNING: 1 listed file could not be read
My disc has enough room. Also, the iso's checksum is fine.
~/Desktop$ md5sum -c MD5SUMS.txt
md5sum: lubuntu-12.04-alternate-amd64+mac.iso: No such file or directory
lubuntu-12.04-alternate-amd64+mac.iso: FAILED open or read
md5sum: lubuntu-12.04-alternate-amd64.iso: No such file or directory
lubuntu-12.04-alternate-amd64.iso: FAILED open or read
md5sum: lubuntu-12.04-alternate-i386.iso: No such file or directory
lubuntu-12.04-alternate-i386.iso: FAILED open or read
md5sum: lubuntu-12.04-alternate-powerpc.iso: No such file or directory
lubuntu-12.04-alternate-powerpc.iso: FAILED open or read
md5sum: lubuntu-12.04-desktop-amd64+mac.iso: No such file or directory
lubuntu-12.04-desktop-amd64+mac.iso: FAILED open or read
md5sum: lubuntu-12.04-desktop-amd64.iso: No such file or directory
lubuntu-12.04-desktop-amd64.iso: FAILED open or read
lubuntu-12.04-desktop-i386.iso: OK <--------------------------------This is the file
md5sum: lubuntu-12.04-desktop-powerpc.iso: No such file or directory
lubuntu-12.04-desktop-powerpc.iso: FAILED open or read
md5sum: WARNING: 7 listed files could not be read
What is going on?
iso
iso
edited Jan 20 '14 at 13:53
Braiam
52.4k20138223
52.4k20138223
asked Jan 20 '14 at 13:46
PyRulezPyRulez
149423
149423
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 1 hour ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Input/output error is not uncommon at the very end of a CD.
(Caused often by write type "TAO", which creates two non-data blocks
at the end of the range, which the drive advertises as readable.
Aka "Read-ahead bug". Traditionally made harmless by 300 kB of padding.
It should not happen if you have chosen write type "SAO".)
Make sure that you try to read only as many bytes from the CD
as are stored in the original .iso image file.
The size of an ISO image is supposed to be integer divisible by 2048.
E.g. if your .iso file has a size of 4,581,523,456 bytes, then it
has 2,237,072 blocks. So use
dd if=/dev/sr0 bs=2048 count=2237072 | md5sum
(assuming your CD drive has address /dev/sr0)
When the reading is done (hopefully without i/o error), then
lookup the resulting MD5 checksum in your file "md5sums.txt".
E.g. "a87d2796b7acf90fbe48dcaeb27dc7cc"
Command line example for writing CD with write type SAO:
xorriso -as cdrecord -v /dev/sr0 -sao -eject lubuntu-12.04-desktop-i386.iso
The same option will also work with programs cdrecord or wodim,
instead of "xorriso -as cdrecord".
Actually, I think it was a disc scratch. I new CD-R fixed it.
– PyRulez
Jan 25 '14 at 13:42
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%2f408224%2fthe-file-casper-filesystem-squashfs-is-corrupt%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
Input/output error is not uncommon at the very end of a CD.
(Caused often by write type "TAO", which creates two non-data blocks
at the end of the range, which the drive advertises as readable.
Aka "Read-ahead bug". Traditionally made harmless by 300 kB of padding.
It should not happen if you have chosen write type "SAO".)
Make sure that you try to read only as many bytes from the CD
as are stored in the original .iso image file.
The size of an ISO image is supposed to be integer divisible by 2048.
E.g. if your .iso file has a size of 4,581,523,456 bytes, then it
has 2,237,072 blocks. So use
dd if=/dev/sr0 bs=2048 count=2237072 | md5sum
(assuming your CD drive has address /dev/sr0)
When the reading is done (hopefully without i/o error), then
lookup the resulting MD5 checksum in your file "md5sums.txt".
E.g. "a87d2796b7acf90fbe48dcaeb27dc7cc"
Command line example for writing CD with write type SAO:
xorriso -as cdrecord -v /dev/sr0 -sao -eject lubuntu-12.04-desktop-i386.iso
The same option will also work with programs cdrecord or wodim,
instead of "xorriso -as cdrecord".
Actually, I think it was a disc scratch. I new CD-R fixed it.
– PyRulez
Jan 25 '14 at 13:42
add a comment |
Input/output error is not uncommon at the very end of a CD.
(Caused often by write type "TAO", which creates two non-data blocks
at the end of the range, which the drive advertises as readable.
Aka "Read-ahead bug". Traditionally made harmless by 300 kB of padding.
It should not happen if you have chosen write type "SAO".)
Make sure that you try to read only as many bytes from the CD
as are stored in the original .iso image file.
The size of an ISO image is supposed to be integer divisible by 2048.
E.g. if your .iso file has a size of 4,581,523,456 bytes, then it
has 2,237,072 blocks. So use
dd if=/dev/sr0 bs=2048 count=2237072 | md5sum
(assuming your CD drive has address /dev/sr0)
When the reading is done (hopefully without i/o error), then
lookup the resulting MD5 checksum in your file "md5sums.txt".
E.g. "a87d2796b7acf90fbe48dcaeb27dc7cc"
Command line example for writing CD with write type SAO:
xorriso -as cdrecord -v /dev/sr0 -sao -eject lubuntu-12.04-desktop-i386.iso
The same option will also work with programs cdrecord or wodim,
instead of "xorriso -as cdrecord".
Actually, I think it was a disc scratch. I new CD-R fixed it.
– PyRulez
Jan 25 '14 at 13:42
add a comment |
Input/output error is not uncommon at the very end of a CD.
(Caused often by write type "TAO", which creates two non-data blocks
at the end of the range, which the drive advertises as readable.
Aka "Read-ahead bug". Traditionally made harmless by 300 kB of padding.
It should not happen if you have chosen write type "SAO".)
Make sure that you try to read only as many bytes from the CD
as are stored in the original .iso image file.
The size of an ISO image is supposed to be integer divisible by 2048.
E.g. if your .iso file has a size of 4,581,523,456 bytes, then it
has 2,237,072 blocks. So use
dd if=/dev/sr0 bs=2048 count=2237072 | md5sum
(assuming your CD drive has address /dev/sr0)
When the reading is done (hopefully without i/o error), then
lookup the resulting MD5 checksum in your file "md5sums.txt".
E.g. "a87d2796b7acf90fbe48dcaeb27dc7cc"
Command line example for writing CD with write type SAO:
xorriso -as cdrecord -v /dev/sr0 -sao -eject lubuntu-12.04-desktop-i386.iso
The same option will also work with programs cdrecord or wodim,
instead of "xorriso -as cdrecord".
Input/output error is not uncommon at the very end of a CD.
(Caused often by write type "TAO", which creates two non-data blocks
at the end of the range, which the drive advertises as readable.
Aka "Read-ahead bug". Traditionally made harmless by 300 kB of padding.
It should not happen if you have chosen write type "SAO".)
Make sure that you try to read only as many bytes from the CD
as are stored in the original .iso image file.
The size of an ISO image is supposed to be integer divisible by 2048.
E.g. if your .iso file has a size of 4,581,523,456 bytes, then it
has 2,237,072 blocks. So use
dd if=/dev/sr0 bs=2048 count=2237072 | md5sum
(assuming your CD drive has address /dev/sr0)
When the reading is done (hopefully without i/o error), then
lookup the resulting MD5 checksum in your file "md5sums.txt".
E.g. "a87d2796b7acf90fbe48dcaeb27dc7cc"
Command line example for writing CD with write type SAO:
xorriso -as cdrecord -v /dev/sr0 -sao -eject lubuntu-12.04-desktop-i386.iso
The same option will also work with programs cdrecord or wodim,
instead of "xorriso -as cdrecord".
answered Jan 25 '14 at 10:41
Thomas SchmittThomas Schmitt
68135
68135
Actually, I think it was a disc scratch. I new CD-R fixed it.
– PyRulez
Jan 25 '14 at 13:42
add a comment |
Actually, I think it was a disc scratch. I new CD-R fixed it.
– PyRulez
Jan 25 '14 at 13:42
Actually, I think it was a disc scratch. I new CD-R fixed it.
– PyRulez
Jan 25 '14 at 13:42
Actually, I think it was a disc scratch. I new CD-R fixed it.
– PyRulez
Jan 25 '14 at 13:42
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%2f408224%2fthe-file-casper-filesystem-squashfs-is-corrupt%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