Tell me more ×
Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems.. It's 100% free, no registration required.
up vote 0 down vote favorite 
Memory for crash kernel (0x0 to 0x0) notwithin permissible range
Red Hat nash version 5.1.19.6 starting
mount: could not find filesystem '/dev/root'
setuproot moving /dev failed: No such file or directory
setuproot: error mounting /proc: No such file or directory
setuproot: error mounting /sys: No such file or directory
switchroot: mount failed: No such file or directory
Kernel panic - not syncing: Attempted to kill init!

The file-system appears like this:

Filesystem            Size  Used Avail Use% Mounted on
/dev/cciss/c1d1p1     2.0T   84G  1.9T   5% /
/dev/cciss/c1d0p1     190M   12M  169M   7% /boot
tmpfs                  32G     0   32G   0% /dev/shm

There are two volumes created in the RAID One /dev/cciss/c1d0p1 only for the boot partition and second /dev/cciss/c1d1p1 for the rest of the Linux partition. This was created to overcome the Ext3 2TB limit issue.

and now i'm unable to access the terminal either from rescue media/ live OS (i'm getting "linux partition not found" error and i'm not getting any terminals for command executions). So i'm unable to execute the commands anywhere.

share|improve this question
That's a kernel panic.. You should be filing a bug report.. – darnir Aug 12 '12 at 18:08
what is the cause for it and can you suggest any solution for that ?since my server has a lot of confidential information. I need to rescue it as soon as possible. – Maniv Aug 12 '12 at 18:45
4  
Your kernel didn't find the root partition. It's impossible to help you without more information. Describe your disk setup as precisely as possible. Tell us how the system boots: what bootloader, what configuration. What changed since the last boot? Are the disks physically ok? Try booting from a rescue media to diagnose the system. Note that this question may be closed due to the lack of information; once you've edited your question to add enough information, reply to one of these comments to have it reopened. – Gilles Aug 12 '12 at 21:09
1  
@Maniv It looks like your disk is damaged. What is your disk setup (RAID, etc.)? From the rescue media, what does fdisk -l report? What partitions correspond to your installed system? If sdz99 is your root partition (replace z and 99 by the right letter and number), what does file - </dev/sdz99 show? What happens if you try to mount it? – Gilles Aug 13 '12 at 11:10
1  
@Maniv You wouldn't have /dev/sdz99, you need to replace z and 99 by the right letter and number. It could be /dev/sda1 or /dev/sdc3 or any other combination, or something like /dev/md0 if you have RAID. As I told you before, run fdisk -l to see the available partitions. Post at least that, and we can probably help you get further. – Gilles Aug 13 '12 at 11:49
show 10 more comments

closed as not a real question by Mat, Ulrich Dangel, Gilles, Renan, Stéphane Gimenez Aug 20 '12 at 16:27

It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, see the FAQ.

Browse other questions tagged or ask your own question.