Results 1 to 8 of 8
when i restart the system get error messages
Mounting local filesystems: mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In ...
- 09-30-2010 #1
boot messages mount: wrong fs type
when i restart the system get error messages
Mounting local filesystems: mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so [FAILED]
- 09-30-2010 #2Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
It sounds like something has either corrupted /dev/sda1 or the device names have changed (possible of you added/removed a disc). To check, boot from a liveCd or recovery disc and run the command: fdisk -l
In the case when something has reordered the device names you can fix that by changing /etc/fstab to use either labels or UUIDs instead of /dev/sd..Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 10-01-2010 #3
i solved this problem first delete this portion then get free space about 48 GB then i creat it again then and formate as ext3 file system then now i got only 41GB space what about 7GB SPACE ?
THANKS
- 10-01-2010 #4
Post the output of fdisk -l command here.
It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 10-01-2010 #5Linux Guru
- Join Date
- Apr 2009
- Location
- I can be found either 40 miles west of Chicago, or in a galaxy far, far away.
- Posts
- 8,974
If it was some type other than ext3 before, such as ext2, then some of the missing space is due to transaction logging requirements - ext3 is a transaction-oriented logging database. That makes it more reliable from the context of recovery after a system crash, power failure, etc.
Sometimes, real fast is almost as good as real time.
Just remember, Semper Gumbi - always be flexible!
- 10-01-2010 #6Code:
[root@localhost ved]# fdisk -l Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disk identifier: 0xa8a8a8a8 Device Boot Start End Blocks Id System /dev/sda1 3918 9729 46684890 83 Linux /dev/sda2 1 1913 15358976 83 Linux Partition 2 does not end on cylinder boundary. /dev/sda3 1913 3655 13998080 83 Linux Partition 3 does not end on cylinder boundary. /dev/sda4 3655 3917 2098176 82 Linux swap / Solaris Partition 4 does not end on cylinder boundary. Partition table entries are not in disk order
- 10-01-2010 #7
That's a incorrect partition table. Look at start/end cylinders of each partition. /dev/sda2 and sda3 are overlapping and device name sda2 has been assigned to first partition.
I would suggest you to backup data, if any and recreate partition table from scratch.
Edit : Just now I noticed that you have installed Linux OS in this Hard disk. Could you post the contents of its /etc/fstab file here?It is amazing what you can accomplish if you do not care who gets the credit.
New Users: Read This First
- 10-01-2010 #8
what i have to do i just send the details of fstab
Code:[root@localhost ved]# cat /etc/fstab # # /etc/fstab # Created by anaconda on Sun Sep 26 20:15:37 2010 # # Accessible filesystems, by reference, are maintained under '/dev/disk' # See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info # UUID=4c2c8f4c-d9e1-4d51-a8f8-f506285b9a41 / ext3 defaults 1 1 UUID=a82d6358-40e0-4460-adfc-c94d90ac1edd swap swap defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts gid=5,mode=620 0 0 sysfs /sys sysfs defaults 0 0 proc /proc proc defaults 0 0 /dev/sda3 /home/ ext3 /dev/sda4 / swap /dev/sda1 /media/sda1 ext3


Reply With Quote