Tag Archives: Linux

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

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.

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:

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


It is often useful to be able to easily paste text to our Fedora Pastebin at and this simple script will do that and return the resulting URL so that people may examine the output. This can hopefully help folks who are for some reason stuck without X, working remotely, or any other reason they may be unable to paste something into the pastebin.

Applicable to Fedora Versions

1.All Fedora Versions

The script is a very simple bash script, the only real requirement is Curl. If curl is not installed, the script is kind enough to suggest how to install it, however it is installed by default.
1. Basic console/term skills
2. curl

Doing the Work
The script is very easy to use, and very simple in itself. It basically takes a filename as the only required argument and returns the resulting URL. This could be manually typed in, but this script simplifies uploading an arbitrary file/output to fpaste. The following examples are assuming you’re using the script in the same directory as the files you’re wanting to upload, so if they are not be sure to specify the full path. If you’re wanting to use the script more often, you could always chmod it and move it somewhere useful. Perhaps in the future this will get packaged, but for now I keep here on the Fedora Unity server for folks to grab.

1. First, get the script. Note that below, -O is a capital letter O, not a zero:

curl -O

2. Upload a specific file to fpaste, in this example, test.txt (which is in the current directory):

sh test.txt

3. Or, you may fpaste stdout data, such as the results of uname -a in this example:

uname -a | sh –

4. And when you’re done, you’ll get output such as this which you’ll tell whomever is looking at your paste:

Please tell us this resulting URL (may take a second):

Python Version

If you prefer, there is also a parallel version of this script written by zcat in Python. You could use this similarly to the shell script above, or perhaps integrate it into other Python projects, etc. How to get the script and a few examples are below.

1. First, get the script. Note that below, -O is a capital letter O, not a zero:

curl -O

2. Upload a specific file to fpaste, in this example, test.txt (which is in the current directory):

python file-to-paste.txt

3. Or, you may fpaste stdout data, such as the results of uname -a in this example:

uname -a | python

4. Or get extensive help from the tool itself:

python –help


CounterStrike and all mods based on Half-Life (1 or 2) are one of the most played games ever but, unfortunately, are designed for Windows and no Linux version has been developed so far. A lot of Linux users have saved a Windows partition just to boot from it when they feel like playing a game. What if that won’t be necessary anymore? What if you could run your favourite games directly for Linux? This is what we are trying to do with this article. First of all, I should warn you that this method isn’t official, nor does it guarantee a successful installation and run. As you probably already know, there is a Wine-based Linux software that was designed to run Windows games in Linux. It’s called �Cedega� and it costs money, which is a problem for many Open Source fans. In this guide, I’m going to use Wine, which is a free program that implements Windows software on Linux. Enough said, let’s begin. First of all, make sure your ATi or nVIDIA drivers are properly installed; otherwise, you will only get around 10 fps in the games, which you probably wouldn’t want to happen. Installing Wine Wine can be installed using one of the guides specific for your distribution that can be found here. If you run Fedora Core, simply execute this command as root:

# yum install wine


You can compile the latest source yourself by using the that can be downloaded from here. Simply, after download, run it from a root terminal:

# sh

Select a profile, follow the steps and with a little luck, you will have the latest version of wine installed and ready. Now, run wine with any small windows program (putty.exe for instance).

# wine putty.exe

When wine is run for the first time, it creates all necessary directories, including your fake C: drive, which is per default located in ~/.wine/drive_c.

Note: Steam requires font �tahoma� to be available in order to show the text in Steam and in the game, so either you follow the guide here to install Microsoft core fonts, or simply search for the font on Google, download it and save it into your ~/.wine/drive_c/windows/fonts directory.

Installing Steam

Simply download the SteamInstall.exe application, change the directory to where you downloaded it and run it with wine:

# wine SteamInstall.exe

It might take a lot of time to update itself, depending on your connection type. However, it might crash while updating with a �Sharing violation� error. To repair this, run the following command in the console:

# wine SteamTmp.exe SelfUpdate “/root/.wine/drive_c/Program Files/Steam/Steam.exe” 14

(substitute the path to steam executables with your path).

Don’t update any games for now. When you are sure Steam runs without any problems, close it and start it again with: #WINEDEBUG=”fixme-all” wine Steam.exe

This command will suppress all FIXME errors that Wine is printing in the console while running in the normal mode. This way, all the games will run a lot faster. Now, it’s time to login with your account. If you can’t type anything in the Login and Password fields, simply right-click one of the fields and then left click it again to make the cut, copy, paste etc menu disappear. Now, in order to run CS1.6, the easiest way is to create a .sh script which you’ll be running from the console. Open your favorite text editor, paste these lines and save the script as, for instance,

#!/bin/bash WINEDEBUG=fixme-all wine

C:/Program Files/Steam/Steam.exe -fullscreen

-width 1280 -height 1024 -applaunch 10

-heapsize 512000 +map_background none “$@”

Of course, you should edit the command line options to suit your system. For example, set the -width and -height to your desktop’s resolution. Next, set the -heapsize to half your computer’s RAM amount. If you have 1GB of RAM, it’s safe to leave 512000, otherwise modify that value. Through the applaunch command option, you can choose what game Steam should run. These all are few of the available options:

Half-Life Mods:


– applaunch 10 tfc

– applaunch 20 dod

– applaunch 30 dmc

– applaunch 40 op4

– applaunch 50 ricochet

– applaunch 60 valve

– applaunch 70 czero

– applaunch 80

Half-Life 2 Mods:


– applaunch 240 dod

– applaunch 300 hl2mp

– applaunch 320

There are still a large number of bugs that need to be fixed in order for Windows games launched on Linux to run smoothly and flawlessly. For instance, try not to minimize the Steam window as it will probably freeze your desktop environment. Good luck!

Another app is currently holding the yum lock; waiting for it to exit…
The other application is: yum
Memory : 15 M RSS ( 29 MB VSZ)
Started: Fri Aug 20 18:13:43 2010 – 11:02 ago
State : Sleeping, pid: 10537

This processes often occurs when there is already a yum process running in the background.
If you are getting this type of error then follow the following steps:

1.First,find out what’s locking the yum,try running
Type the following in the command line:
# ps aux | grep yum

# ps aux | grep yum
root 8657 0.1 0.5 29492 15000 ? S 17:25 0:05 /usr/bin/python /usr/bin/yum install update
root 10856 0.1 0.5 29876 15660 ? S 18:18 0:00 /usr/bin/python

here,8657 and 10856 is known as PID number.

2. Note the PID number and write the following command in the terminal to end the processes.

# kill <Insert ID Number>

Kill all the processes related to yum one by one and then try to start a new yum process.

%d bloggers like this: