Disk Crash Investigation

Last day, while copying some movies into the NTFS drive my laptop suffered a sudden shutdown.

After restart, I was unable to mount the drive in my Fedora box and it showed a creepy error instead.

Error mounting: mount exited with exit code 13: ntfs_attr_pread_i:
ntfs_pread failed: Input/output error
Failed to read NTFS $Bitmap: Input/output error
NTFS is either inconsistent, or there is a hardware fault, or it’s a
SoftRAID/FakeRAID hardware. In the first case run chkdsk /f on Windows
then reboot into Windows twice. The usage of the /f parameter is very
important! If the device is a SoftRAID/FakeRAID then first activate
it and mount a different device under the /dev/mapper/ directory, (e.g.
/dev/mapper/nvidia_eahaabcc1). Please see the ‘dmraid’ documentation
for more details

This was when ntfsfix came as knight to fight the battle.

ntfsfix sub-packaged under ntfsprogs is a really nice tool to solve NTFS problems in Linux.

Let’s say you need to recover /dev/sda6
Then run: sudo ntfsfix /dev/sda6

Celebrating dgplug’s Birthday.

On 8th September 2012, the day dgplug completed it’s eight successful years, we (Gaurav, Chandan, Biraj, Piyush, Souradeep, Apoorv and I thought of organizing a workshop for the students of our college. We mainly thought to enlighten the students with the ideas of using GNU/Linux. Then, they would be told on “How to install GNU/Linux”. We named the workshop as “Peeping Out of Windows, Looking into the world of Linux”.

We started off with our registration at 9:45am outside our P.G.Building Seminar Hall. At first, We thought there would be a handful participants but just few minutes later we were overwhelmed with interested participants. We had to close our registration because the hall had already ran out of capacity. We started off with the seminar at 10:30am with apoorv giving the opening speech. We had grouped up Apoorv, Souradeep, Piyush and Biraj to give the talk on “What are the benifits of using GNU/Linux”. After the seminar ended, it seemed that the participants were convinced with the idea. The seminar concluded with an Q/A session for the students enquire about the doubts they faced.

After the first seminar, the students enjoyed the tea-break. At around 11:30am, Chandan, Gaurav and I started with the second session on “How to install Linux(Fedora)”. We gave a slide followed by a live demostration on how to install dual-boot Fedora from the root level. Then we had an interactive session with the participants where their FAQs were co-heartedly invited and we tried our level best to solve out their queries keeping in mind our motto to make them well acqauinted with the very OS. We also informed them about the hands-on workshop that we planned to make the participants install the OS by themselves.

We began the “Hands-on session” at 2:30pm at our CS/IT Seminar Hall. The participants started out pouring a bit late. As the participants came, we divided them into groups and started out with the installation session. Some of them needed a fresh installation, some came out to upgrade their system and other queries. Meanwhile, the participants were served with refreshments.At the end we distributed the Fedora Live ISO, Full Installation ISO. We packed up at 5:30 pm and returned back to our nest tired and exhausted.

We are really thankful to Asst. Prof. Dinesh Pradhan and Pratap Sir and everyone who indirectly helped us out for the proper execution of the workshop. We are also planning to continue with this workshop at our college in near future.

This slideshow requires JavaScript.

Booting Problem

The system will not boot.
Instead it ends up with the message:
An error occured during file system check.

Dropping you to a shell.Give root password for maintenance or type Control-D to resume normal startup

1.First,type in your root password and press to get the prompt shown below.
(repair filesystem) 1#

2.Type the following command:
fsck -y /

The system may warn about the potential risk of further file system damage when running the test on a
mounted file system.
The system will then check for file system errors and fix them if possible. When finished a new prompt
appears. Do a reboot and hope for the best.

If only a few seconds passes before the new prompt appears the system was probably not able or willing
to check the / partition. It may also refer to a journal saying the / partition was “clean”. Try running the
check on the /home partition instead:

fsck -y /home

If the check will not run when issuing the above commands, try using the physical device names instead
of their mount points.

fsck -y [physical device name, for example /dev/sda1]

To find the physical device name try performing the command:
df

which will return a partition table listing both the device names as well as their mount points. Look for
the “/” and “/home” partitions.

Reference:ftp://www.olex.no