Still celebrating National IT Professionals Day with 3 months of free Premium Membership. Use Code ITDAY17

x
?
Solved

Momentary power outtage causes error message in file /scsi/sg.o

Posted on 2006-10-23
3
Medium Priority
?
245 Views
Last Modified: 2013-12-16
I'm supporting a Debian box running 2.4.27-2-386

A momentary power outtage caused the file to get corrupted or become unreadable somehow and now the machine won't boot. The error is below.


insmod: /lib/modules/2.4.27-2-386/kernel/drivers/scsi/sg.o: No such file or directory
insmod: insmod sg failed

SCSI subsystem driver Revision: 1.00
Journalled Block Device Driver loaded
pivot_root: No such file or directory
/sbin/init: 432: cannot open dev/console: No such file
Kernel panic: Attempted to kill init!


I've booted with a knoppix bootable CD, but can't see many of the files on the ext2 and jfs file systems due to permissions problems. I have the root password for debian, but cannot seem to use it to modify the files.

I have a few questions, sorry if these are basic

1) How can I force the file system to allow me to access the files? I can probably do a side-install of another linux OS and use chmod/chown but I'm not sure that's the easiest and most effective way to do it.

2) Can I just recompile the kernel or use another method to recreate the damaged file? It seems like a simple SCSI device driver.

Thanks for your time.
0
Comment
Question by:EvilOtto
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
3 Comments
 
LVL 2

Author Comment

by:EvilOtto
ID: 17792869
I do not have a rescue CD as they recommend on the debian forums, nor do I have the OS CD, but I'm sure I can obtain the OS cd somehow.
0
 
LVL 30

Accepted Solution

by:
Kerem ERSOY earned 2000 total points
ID: 17799837
Hi,

sg.o is the genereic scsi driver. This is normal for your linux not boot becaue it can no longer access your boot volume.
In this case what you will do is :

fsck -y /dev/sdaX  (X tands for your drive letter)

This may fix the problem with your File Allocation Blocks and you can boot.

You can get this verison rpm vity yast2 tool and copy the same version sg.o to /lib/modules/2.4.27-2-386/kernel/drivers/scsi.

If you can't find a similar version you may try to recompile the source obtained from http://www.kernel.org archives.

You don't need a rescue disk knoppix is OK. In fact the rescue disk you'd obtain from the debian site will most probably include a 2.6.x kernel.

I hope this helps.

Cheers,
K.




0

Featured Post

Learn Veeam advantages over legacy backup

Every day, more and more legacy backup customers switch to Veeam. Technologies designed for the client-server era cannot restore any IT service running in the hybrid cloud within seconds. Learn top Veeam advantages over legacy backup and get Veeam for the price of your renewal

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Over the last ten+ years I have seen Linux configuration tools come and go. In the early days there was the tried-and-true, all-powerful linuxconf that many thought would remain the one and only Linux configuration tool until the end of times. Well,…
The purpose of this article is to demonstrate how we can use conditional statements using Python.
Learn several ways to interact with files and get file information from the bash shell. ls lists the contents of a directory: Using the -a flag displays hidden files: Using the -l flag formats the output in a long list: The file command gives us mor…
Connecting to an Amazon Linux EC2 Instance from Windows Using PuTTY.
Suggested Courses

715 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question