Wrong logical/physical sector size can lead to file corruption?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I'm experiencing continuous file corruption problems so I have to run fsck almost every time I start Ubuntu 16.04. :( :( :(
Recently, I bought a second new 1TB hard disk and reinstalled everything. After few days the problem was again there... the system boots but is not usable (today I've got a lot of folders mounted in read-only mode...)
I've made all the checks trying to detect an hardware problem (memtest, prime95, Gsmartcontrol, BIOS upgrade, etc) but I didn't find any fault. Also the temperature of the CPU is quite stable.
Could the adopted partitioning be the problem?
Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x583cc96a
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 7999487 7997440 3,8G 82 Linux swap / Solaris
/dev/sda2 8001534 1953523711 1945522178 927,7G 5 Extended
/dev/sda5 8001536 47060991 39059456 18,6G 83 Linux
/dev/sda6 47063040 1953523711 1906460672 909,1G 83 Linux
Partition 2 does not start on physical sector boundary.
I read that a misaligned logical/physical sector size can only impact
the performance. Nevertheless I read also some case of PCs not booting at all. Which is true?
Should I not waste further time and buy a new PC? :( :( :(
partitioning hard-drive
edited Mar 24 at 12:17
anonymous2
3,38242149
asked Nov 13 '16 at 15:00
gimpogimpo
2617
add a comment |
I'm experiencing continuous file corruption problems so I have to run fsck almost every time I start Ubuntu 16.04. :( :( :(
Recently, I bought a second new 1TB hard disk and reinstalled everything. After few days the problem was again there... the system boots but is not usable (today I've got a lot of folders mounted in read-only mode...)
I've made all the checks trying to detect an hardware problem (memtest, prime95, Gsmartcontrol, BIOS upgrade, etc) but I didn't find any fault. Also the temperature of the CPU is quite stable.
Could the adopted partitioning be the problem?
Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x583cc96a
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 7999487 7997440 3,8G 82 Linux swap / Solaris
/dev/sda2 8001534 1953523711 1945522178 927,7G 5 Extended
/dev/sda5 8001536 47060991 39059456 18,6G 83 Linux
/dev/sda6 47063040 1953523711 1906460672 909,1G 83 Linux
Partition 2 does not start on physical sector boundary.
I read that a misaligned logical/physical sector size can only impact
the performance. Nevertheless I read also some case of PCs not booting at all. Which is true?
Should I not waste further time and buy a new PC? :( :( :(
partitioning hard-drive
edited Mar 24 at 12:17
anonymous2
3,38242149
asked Nov 13 '16 at 15:00
gimpogimpo
2617
No, thePartition 2 does not start on physical sector boundarywarning is harmless for an extended partition type; ignore it. My guess is you've got a bad cable, flaky disk controller hardware on the motherboard, or some other hardware problem. Another possibility is that you're not shutting down properly; you should always use a proper shutdown command, not just hit the computer's power button.
– Rod Smith
Nov 13 '16 at 15:43
@RodSmith - Hi Rod. I've checked visually the motherboard (ASRock N68-GS4 FX) and I didn't find any problem. I will do a double check now. I always shutdown the machine by using the proper command on the Ubuntu main menu.
– gimpo
Nov 13 '16 at 15:54
1
A visual check most likely won't detect a voltage fluctuation, microscopic fracture of a critical trace, failing chip, etc. It might or might not detect a poorly-seated connector, failing cable etc.
– Rod Smith
Nov 13 '16 at 16:11
@RodSmith - yeah, you're right. Now I've got the root partition in read-only mode... great day is today for me! There should be an error on boot record (fsck skips the root partition as a zero-length one). I've no other choice than buying a new PC, even if it is not an happy period for me from an economical point of view... :( :( :(
– gimpo
Nov 13 '16 at 17:47
add a comment |
I'm experiencing continuous file corruption problems so I have to run fsck almost every time I start Ubuntu 16.04. :( :( :(
Recently, I bought a second new 1TB hard disk and reinstalled everything. After few days the problem was again there... the system boots but is not usable (today I've got a lot of folders mounted in read-only mode...)
I've made all the checks trying to detect an hardware problem (memtest, prime95, Gsmartcontrol, BIOS upgrade, etc) but I didn't find any fault. Also the temperature of the CPU is quite stable.
Could the adopted partitioning be the problem?
Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x583cc96a
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 7999487 7997440 3,8G 82 Linux swap / Solaris
/dev/sda2 8001534 1953523711 1945522178 927,7G 5 Extended
/dev/sda5 8001536 47060991 39059456 18,6G 83 Linux
/dev/sda6 47063040 1953523711 1906460672 909,1G 83 Linux
Partition 2 does not start on physical sector boundary.
I read that a misaligned logical/physical sector size can only impact
the performance. Nevertheless I read also some case of PCs not booting at all. Which is true?
Should I not waste further time and buy a new PC? :( :( :(
partitioning hard-drive
edited Mar 24 at 12:17
anonymous2
3,38242149
asked Nov 13 '16 at 15:00
gimpogimpo
2617
I'm experiencing continuous file corruption problems so I have to run fsck almost every time I start Ubuntu 16.04. :( :( :(
Recently, I bought a second new 1TB hard disk and reinstalled everything. After few days the problem was again there... the system boots but is not usable (today I've got a lot of folders mounted in read-only mode...)
I've made all the checks trying to detect an hardware problem (memtest, prime95, Gsmartcontrol, BIOS upgrade, etc) but I didn't find any fault. Also the temperature of the CPU is quite stable.
Could the adopted partitioning be the problem?
Disk /dev/sda: 931,5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: dos
Disk identifier: 0x583cc96a
Device Boot Start End Sectors Size Id Type
/dev/sda1 * 2048 7999487 7997440 3,8G 82 Linux swap / Solaris
/dev/sda2 8001534 1953523711 1945522178 927,7G 5 Extended
/dev/sda5 8001536 47060991 39059456 18,6G 83 Linux
/dev/sda6 47063040 1953523711 1906460672 909,1G 83 Linux
Partition 2 does not start on physical sector boundary.
I read that a misaligned logical/physical sector size can only impact
the performance. Nevertheless I read also some case of PCs not booting at all. Which is true?
Should I not waste further time and buy a new PC? :( :( :(
partitioning hard-drive
partitioning hard-drive
edited Mar 24 at 12:17
anonymous2
3,38242149
asked Nov 13 '16 at 15:00
gimpogimpo
2617
edited Mar 24 at 12:17
anonymous2
3,38242149
asked Nov 13 '16 at 15:00
gimpogimpo
2617
edited Mar 24 at 12:17
anonymous2
3,38242149
edited Mar 24 at 12:17
anonymous2
3,38242149
edited Mar 24 at 12:17
anonymous2
3,38242149
3,38242149
asked Nov 13 '16 at 15:00
gimpogimpo
2617
asked Nov 13 '16 at 15:00
gimpogimpo
2617
asked Nov 13 '16 at 15:00
gimpogimpo
2617
2617
No, thePartition 2 does not start on physical sector boundarywarning is harmless for an extended partition type; ignore it. My guess is you've got a bad cable, flaky disk controller hardware on the motherboard, or some other hardware problem. Another possibility is that you're not shutting down properly; you should always use a proper shutdown command, not just hit the computer's power button.
– Rod Smith
Nov 13 '16 at 15:43
@RodSmith - Hi Rod. I've checked visually the motherboard (ASRock N68-GS4 FX) and I didn't find any problem. I will do a double check now. I always shutdown the machine by using the proper command on the Ubuntu main menu.
– gimpo
Nov 13 '16 at 15:54
1
A visual check most likely won't detect a voltage fluctuation, microscopic fracture of a critical trace, failing chip, etc. It might or might not detect a poorly-seated connector, failing cable etc.
– Rod Smith
Nov 13 '16 at 16:11
@RodSmith - yeah, you're right. Now I've got the root partition in read-only mode... great day is today for me! There should be an error on boot record (fsck skips the root partition as a zero-length one). I've no other choice than buying a new PC, even if it is not an happy period for me from an economical point of view... :( :( :(
– gimpo
Nov 13 '16 at 17:47
add a comment |
No, thePartition 2 does not start on physical sector boundarywarning is harmless for an extended partition type; ignore it. My guess is you've got a bad cable, flaky disk controller hardware on the motherboard, or some other hardware problem. Another possibility is that you're not shutting down properly; you should always use a proper shutdown command, not just hit the computer's power button.
– Rod Smith
Nov 13 '16 at 15:43
@RodSmith - Hi Rod. I've checked visually the motherboard (ASRock N68-GS4 FX) and I didn't find any problem. I will do a double check now. I always shutdown the machine by using the proper command on the Ubuntu main menu.
– gimpo
Nov 13 '16 at 15:54
1
A visual check most likely won't detect a voltage fluctuation, microscopic fracture of a critical trace, failing chip, etc. It might or might not detect a poorly-seated connector, failing cable etc.
– Rod Smith
Nov 13 '16 at 16:11
@RodSmith - yeah, you're right. Now I've got the root partition in read-only mode... great day is today for me! There should be an error on boot record (fsck skips the root partition as a zero-length one). I've no other choice than buying a new PC, even if it is not an happy period for me from an economical point of view... :( :( :(
– gimpo
Nov 13 '16 at 17:47
No, the
Partition 2 does not start on physical sector boundary warning is harmless for an extended partition type; ignore it. My guess is you've got a bad cable, flaky disk controller hardware on the motherboard, or some other hardware problem. Another possibility is that you're not shutting down properly; you should always use a proper shutdown command, not just hit the computer's power button.– Rod Smith
Nov 13 '16 at 15:43
No, the
Partition 2 does not start on physical sector boundary warning is harmless for an extended partition type; ignore it. My guess is you've got a bad cable, flaky disk controller hardware on the motherboard, or some other hardware problem. Another possibility is that you're not shutting down properly; you should always use a proper shutdown command, not just hit the computer's power button.– Rod Smith
Nov 13 '16 at 15:43
@RodSmith - Hi Rod. I've checked visually the motherboard (ASRock N68-GS4 FX) and I didn't find any problem. I will do a double check now. I always shutdown the machine by using the proper command on the Ubuntu main menu.
– gimpo
Nov 13 '16 at 15:54
@RodSmith - Hi Rod. I've checked visually the motherboard (ASRock N68-GS4 FX) and I didn't find any problem. I will do a double check now. I always shutdown the machine by using the proper command on the Ubuntu main menu.
– gimpo
Nov 13 '16 at 15:54
1
1
A visual check most likely won't detect a voltage fluctuation, microscopic fracture of a critical trace, failing chip, etc. It might or might not detect a poorly-seated connector, failing cable etc.
– Rod Smith
Nov 13 '16 at 16:11
A visual check most likely won't detect a voltage fluctuation, microscopic fracture of a critical trace, failing chip, etc. It might or might not detect a poorly-seated connector, failing cable etc.
– Rod Smith
Nov 13 '16 at 16:11
@RodSmith - yeah, you're right. Now I've got the root partition in read-only mode... great day is today for me! There should be an error on boot record (fsck skips the root partition as a zero-length one). I've no other choice than buying a new PC, even if it is not an happy period for me from an economical point of view... :( :( :(
– gimpo
Nov 13 '16 at 17:47
@RodSmith - yeah, you're right. Now I've got the root partition in read-only mode... great day is today for me! There should be an error on boot record (fsck skips the root partition as a zero-length one). I've no other choice than buying a new PC, even if it is not an happy period for me from an economical point of view... :( :( :(
– gimpo
Nov 13 '16 at 17:47
add a comment |
0
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',
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%2f848957%2fwrong-logical-physical-sector-size-can-lead-to-file-corruption%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f848957%2fwrong-logical-physical-sector-size-can-lead-to-file-corruption%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
No, the
Partition 2 does not start on physical sector boundarywarning is harmless for an extended partition type; ignore it. My guess is you've got a bad cable, flaky disk controller hardware on the motherboard, or some other hardware problem. Another possibility is that you're not shutting down properly; you should always use a proper shutdown command, not just hit the computer's power button.– Rod Smith
Nov 13 '16 at 15:43
@RodSmith - Hi Rod. I've checked visually the motherboard (ASRock N68-GS4 FX) and I didn't find any problem. I will do a double check now. I always shutdown the machine by using the proper command on the Ubuntu main menu.
– gimpo
Nov 13 '16 at 15:54
1
A visual check most likely won't detect a voltage fluctuation, microscopic fracture of a critical trace, failing chip, etc. It might or might not detect a poorly-seated connector, failing cable etc.
– Rod Smith
Nov 13 '16 at 16:11
@RodSmith - yeah, you're right. Now I've got the root partition in read-only mode... great day is today for me! There should be an error on boot record (fsck skips the root partition as a zero-length one). I've no other choice than buying a new PC, even if it is not an happy period for me from an economical point of view... :( :( :(
– gimpo
Nov 13 '16 at 17:47