Pages: [1]   Go Down
Print
Author Topic: Segmentation fault (core dumped)  (Read 445 times)
3kb6vs9b1
Full Member
**
Offline Offline

Posts: 111


media eater


« on: March 29, 2011, 09:23:30 pm »

Please advise

Code:
mede8er login: root
warning: cannot change to home directory


BusyBox v1.1.3 (2010.07.12-08:31+0000) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/ # e2fsck -y /dev/sda3
e2fsck 1.38 (30-Jun-2005)
e2fsck: while trying to open /dev/sda3

The superblock could not be read or does not describe a correct ext2
filesystem.  If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
    e2fsck -b 8193 <device>

e2fsck: Segmentation fault (core dumped)
/ #
Logged
Maasbommel
Global Moder8or
Hero Member
*****
Offline Offline

Posts: 6 874



« Reply #1 on: March 30, 2011, 08:00:44 am »

Can you post the output of the following command:

fdisk -l
Logged

3kb6vs9b1
Full Member
**
Offline Offline

Posts: 111


media eater


« Reply #2 on: March 30, 2011, 06:01:24 pm »

Code:
Disk /dev/sdc: 750.1 GB, 750156374016 bytes
255 heads, 63 sectors/track, 91201 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot    Start       End    Blocks   Id  System
/dev/sdc1               2       91141   732082050    7  HPFS/NTFS
/dev/sdc2           91142       91161      160650   82  Linux swap
/dev/sdc3           91162       91181      160650   83  Linux
Logged
Maasbommel
Global Moder8or
Hero Member
*****
Offline Offline

Posts: 6 874



« Reply #3 on: March 30, 2011, 06:06:20 pm »

Strange that you have sdc names and not sda.
When you run the command, were there any other disks attached on usb?

In this case you need to run:
e2fsck -y /dev/sdc3

But... Why do you want to run this, do you have some kind of issues or expect to have?

I advise not to mess on the linux prompt if you don't know what you are doing or when it is not advised to do.....

In this case you got the error because you were running the command on a wrong device file name.
Logged

3kb6vs9b1
Full Member
**
Offline Offline

Posts: 111


media eater


« Reply #4 on: March 30, 2011, 06:30:21 pm »

I don't mess with it, I just was reading through forum and wanted to see if disc is OK.
No discs attached except original USB cable with nothing attached to it.
Correct command returned
Code:
/dev/sdc3: recovering journal
/dev/sdc3: clean, 11/40320 files, 9220/160648 blocks
Logged
Maasbommel
Global Moder8or
Hero Member
*****
Offline Offline

Posts: 6 874



« Reply #5 on: March 30, 2011, 08:45:42 pm »

That looks good.
Logged

3kb6vs9b1
Full Member
**
Offline Offline

Posts: 111


media eater


« Reply #6 on: March 30, 2011, 09:10:44 pm »

Cheers.
Logged
Pages: [1]   Go Up
Print
Jump to: