Linux - DesktopThis forum is for the discussion of all Linux Software used in a desktop context.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a desktop computer with dual boot, using old OpenSUSE 11.4 and Windows 7.
Recently an automated scan disk in Opensuse, called Disk Utility or something like that, started to report errors on windows 7 system reserved partition. I am talking about small, 100MB partition that is used by windows system for boot loading data storage, or something like that and witch is by order placed first on hard disk.
The disk utility software reports a certain number of reallocated sectors, about 50 of them. On the other side, when I use windows 7 "CHKDSK" program to scan the 100MB partition, it doesn't report any kind of error in this volume.
The computer works fine and I don't have any kind of problems.
Should I ignore these warnings and continue to use this computer normally?
Have you Windows install or recovery media with activation code for this machine?
Do you have current backups of your data and third party software?
If the answer is yes, drive on.
Such reallocation is normal, but when it get excessive can be symptom of impending drive failure. As with any disk, yours may serve well for years or fail later today. Just be ready. Once you are ready for the event, plan to STAY ready and stop worrying.
If the answer is NO, then you are not ready for the event. Windows installs often come with a utility to burn the windows install to DVD media. Linux, you only need an install CD or DVD. In both cases those do NOT back up your data: make a backup of your data for both environments.
So, if I have understood your answer correctly,
this is something that can be repaired with system rinstallation and/or disk formatting.
Can I somehow format and reinstall only 100MB partition?
I've seen that there is a windows BOOTREC.EXE /FIXBOOT application but I suppose that it fixes MBR record only.
this is something that can be repaired with system rinstallation and/or disk formatting.
What is being suggested is it appears your drive is failing, no one knows when that may happens and wpeckham is suggesting you get backups.
The 100MB partition which you mention is in all likelihood your boot partition. Formatting it will render windows unbootable. If you reinstall the windows bootloader with the commands mentioned, you will then need to reinstall the Grub bootloader if you want to continue to use Opensuse. Get backups so you are ready for the eventual drive failure.
However I do not understand if I have to buy a new hard disk,
or this problematic condition can be fixed using reinstallation of Windows
(or reinstallation of boot partition only)??
If "Yes" is an answer I will easily reinstall Grub after Windows is fixed first.
You might run chkdsk from windows regularly as well as the Opensuse program and see if anything changes, more reallocated sectors. Just keep backups, it might continue to work for years.
I've done CHKDSK yesterday and it said that everything is OK! No bad sectors??!
And what about my question if reinstallation of windows can fix the problem?
It's easier for me to simply do that, then to live in fear of sudden fail,
no matter the drive could also work for years
Also, I do not understand which partitions are in danger?
Only windows C: partition, or whole hard disk?
Also, I do not understand which partitions are in danger?
Only windows C: partition, or whole hard disk?
You indicated in your initial post that you were getting these errors on the 100MB partition. That in all likelihood is the separate boot partition as that is the standard size for windows 7. It is not the "C:" partition, it is a separate partition and re-installing the already working boot partition isn't going to change anything or make bad sectors go away if in fact there are any.
Let me emphasize again: get backups of everything you do not want to lose.
Your drive MAY be fine and run for years, but if it fails there IS NO FIX. Failed hardware is failed, it makes a pretty good door stop. Your fix will be new drives and restore from backup, or do without.
IF you want not to do without, get backups.
Once you have backups, do not let the drive issue rule your life. If the drive firmware handles some minor block errors, that is what it is intended to do. If there is more failure than it can handle, you have your backups and life is GOOD!
Soon or later it WILL fail, all drives DO. With luck, it will be later. With regular backups, you are prepared for that day and can compute with confidence.
That is the answer that I was looking for
because it wasn't quite clear for me from your first post.
Need to get a new drive. No reinstallation/reformating can repair it.
Well, we got a little closer.
IF I meant "go out and buy a drive" I would have said so. Your drive may not be failing, yet. And buying a drive now may be YEARS premature. WHEN it fails, that will be the option, but by that time your drive options may be FAR faster, bigger, and cheaper. (Because that is the way drives have gone overall in the last 45 years.)
What I MEAN is, "get a backup and stop worrying about it" now. Worry about it when yoou have more symptoms and have to make a decision about buying a new drive, or a new machine.
Even if it IS starting to fail, the drive just MIGHT still outlast other components!
however, I use this computer for my work
and I need to fix this issue.
I understand that there is a large probability that the
drive can work for years and outlast other components...
However if there is any rational possibility of sudden failure
which can put me in the situation when I am
without computer and have a lot of work to do,
then the keeping of this hard drive doesn't sound good
I need at least 1-2 weeks to reinstall
both of the systems, all the programs, and other adjustments...
Therefore, I will get a new hard drive soon.
It is not only about the backups, I make them anyway.
Well, if that is what you want to do it is certainly your decision.
Part of what I am trying to say here is that drive firmware normally does some relocation to deal with bad blocks that may be present from the assembly line, and this drive may be perfectly normal. It is a pattern of increasing relocation (indicating damage or increasing failure zones) that indicates failure: an initial number of relocation blocks that do not change may be normal.
If, however, it is that critical it may make sense to take steps anyway.
You may want to purchase a replacement drive, and use clonezilla to make it a clone of your current drive. Instant snap-in replacement to get you up and going faster in the case of a drive failure. Even if the old drive never fails during the life of the machine, the peace of mind may be worth the cost.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.