GeneralThis forum is for non-technical general discussion which can include both Linux and non-Linux topics. Have fun!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
My w2k3 server suddenly starts slowing down tremendously, infact it takes hours to boot up, lounching applications and other activities take a very long time to execute. client workstations also take much time to authenticate.
when i looked at the event viewer it says:
The device, \Decice\Harddisk0, has a bad block.
also the error ID says 7
the problem is that this is a domain controller (AD) and i'm worried of loosing my AD database.
how do i peacefully solve this issue?
please note, i'm not exactly sure if the bad block is the cause of it or something else.
Do you have a raid config? If you can hot swap a drive, then do that.
Otherwise I would start digging deep into information about backing up your AD database and how to restore it to another computer.
Does the bad block error get reported a lot? Or just once. If it is reported several times, then yes it is the problem.....
Is there excessive memory use? Is there something using a lot of the processor? More info would help. Are you sure the network settings are correct on the clients and server? Possibly bad memory? You can download something to test your memory with something like memtest86+. What kind of harddrive do you have. Just about every vendor provides tools to check out the integrity of the drive.
after a number of options including chddsk /c it now improves a bit in speed . but the problem now is that i want to back up but the server simply cannot. each time i attempt to back up (while its backing up) the server suddenly shut down for reason i dont know. i'm using veritas backup ( also tried using windows built in backup.exe) the same result
whats the fix for this?
yeah Kimvatte, i'm now sure the real problem is bad sector. you see; i try to use GParted to copy the content of w2k3 harddisk to new harddisk and its reporting an error saying that 7 bad sectors are discovered in the w2k3 drive. and the main problem here is that GParted could not continue the hard disk copy 'cos of the bad sector.
on the other hand even if w2k3 server can boot up (and still slow), i cannot use Veritas to back up, ('cos on my observation) when the veritas initialises the back up process and goes on backing up, once it comes accross the bad sector on the disk the entire machine immediately shuts down - i've tried this over and over!
i'm just stucked now!
MY PROBLEM IS TO MOVE THE CONTENT OF THIS W2K3 DISK TO NEW DISK (using GParted or any other software), OR SUCCESFULLY BACK IT UP AND START WITH NEW DISK.
any help please?
Modern hard disks automatically detect and reallocate bad sectors to a reserved area. This is completely transparent to the OS. Only once this reserved area fills up will you even see a bad block (if not using SMART tools that is.) So by the time the OS itself reports any you're already in deep crapolla.
I second Crito's suggestion. Everyth8ing can be replicated over to the new domain server relatively easy.
If you have another server what I would do is use dcpromo to promote the other one to the domain master, migrate any other services over manually, remove the disks from the old server and install new disks. KEEP the old disks in storage in case you need to recover data off of them later.
A crude way will be using dd.
U can take an entire disk to disk back-up [even if its got some bad sectors] and start off with the new disk.
But u need a hard disk of the same size [or more] and a linux system :-)
if u can get this then use dd command to rescue the server