Systemrescuecd fsck12/2/2023 ![]() Once you boot with one of those cd/dvd and put the below text at the command prompt it presents: ![]() The first cd/dvd will do the job for us or get a systemrescuecd to do that. That we find out that root(/)partition of the filesystem gor corrupted due to some reasons.So we need to fix that issue to get back the system as soon as possible on the track.įor this kind of significant that on a mounted system you just cannot run fsck…as I said earlier.becauase it will corrupt the data on it.So we need a installation cd/dvd for our rescue. V-–> It will provide you the verbose explanation what that comming going through on the terminal screen. Y-> it will try to detect and fix any filesystem related corruption without manual intervention.į-–> this will force check even the system check says it’s clean. Ok.let me explain the flags or switch I passed with the fsck. Ok once you type init 1 at the terminal prompt you will be taken to the singe user mode.From there simply unmount the partions as show # init 1 -> this will bring to the single user # umount /dev/sda2 -> assuming this partion hold the /home section. Now, running fsck on other partition like /home,/var,/usr …įirst and foremost thing to be done is get into a single user mode.how do you do that? It is a bad idea and not recommended to run fsck(yes,this is the inbuilt tool you need to use)the mounted partition or drive.So don’t do that. Now filesystem can be corrupted in various ways.few common ways are :ġ) Not properly shutdown the server(although most of the cases journaling will do the healing)Ģ) Sudden power cut left your system down with lot of processing going onģ)Somebody has done something special(bad sense) to corrupt the data on that particular partition. So the first question come into the mind why the hell you need to check the filesystem? Specially the root(/) part of it…sound pretty dull and boring…huh.please don’t ignore this.You know ignorance is a sin…so do not commit it. I do not issue any guarantee that this will work for you. So without much ado lets play with it or let me show you the simple tricks. Being an GNU/Linux administrator/NOC/Ops one has to have the clear cut understanding what they are doing.Because handling the production box require lot of common sense and in depth knowlegde about the platform/OS. ![]() I think I am looking for something like that, which would be found in /etc/fstab of my file system, but I can't access that file.As it is an important issue to deal with low level thing in the server archtecture. ![]() I am on a liveCD so proc/mounts, will not give me the desired HD info. The information should be in /etc/fstab if I understand correctly, but I can't access that file on the filesystem on the hard drives or can I?Īny ideas on how to check my RAID virtual disks? dev/sda1 does exist, but is part of the raid system, so I need to find out, what the name of the virtual partitions is, right? (There are two, root and storage). Now I get an error: no such file or directory while opening /dev/sda1 Normally I would do something like this: # fsck.ext4 /dev/sda1 The main problem I have is I don't know what the names partitions of the virtual drives of the RAID are. The server has 4 HD using a hardware RAID5 system. I can boot into a systemRescueCD no problem. My Ubuntu 14.04 server won't boot properly and I want to check the hard drives with fsck to make sure everything is ok.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |