Alan McKinnon píše v Út 23. 01. 2007 v 16:39 +0100:
> On Tuesday 23 January 2007 13:11, jcd wrote:
> > Hi.
> > I'm in bad situation. I have two physical disks. First (DiskA) have
> > 200GB and second (DiskB) have 160GB capacity. On DiskB I have Linux
> > partitions and some data partitions. On DiskA I had had 40GB NTFS
> > (Windows) and 160GB NTFS partitions (data), but I already deleted
> > Windows partition. So, I copied data from 160GB partition on DiskA to
> > temporary space on DiskB, then I deleted remaining NTFS partition on
> > DiskA and created one 200GB ext3 partition (I think so. In cfdsik I
> > chose partition type '83 Linux') and then formatted it 'mke2fs
> > -j /dev/sdb1'. Then I copied (moved :( ) all the data back to DiskA
> > and everuthing was fine. It was yesterday. Today I started PC and at
> > startup init said "Some local filesystems failed to mount". OK, in
> > /etc/fstab I have "/dev/sdb1 /mnt/zaloha ext3 noatime 0 2" ... it
> > seems to be good. I also tried to change ext2, but with both 'mount
> > -a' says:
> > mount: wrong fs type, bad option, bad superblock on /dev/sdb1,
> >        missing codepage or other error
> >        In some cases useful info is found in syslog - try
> >        dmesg | tail  or so.
> > In /var/log/messages I found just "VFS: Can't find ext3 filesystem on
> > dev sdb1" :((. When I try just 'mount /dev/sdb1 /mnt/zaloha',
> > at /mnt/zaloha I have mounted that old Windows partition that I
> > already deleted. Do you know any solution how can I get back my ext3
> > partition to get back my data please? And what could be cause of this
> > problem or when I can find what is the cause? Thanks very very much.
> 
> You've given lots of words, but very very little information, not even 
> the commands you used to perform these actions. Without this info it 
> becomes very hard to help you out.
> 
> Meantime, please provide the output of the following commands:
> 
> fdisk -l
> fsck /dev/sdb1
> mount /dev/sdb1 /some/mount/point
> 
> and we'll take it from there
> 
> alan
> 

OK. Here it is (I confused First disk capacity, 250GB instead of 200GB):

------------------------------------------------------------------------
#fdisk -l /dev/sdb
Disk /dev/sdb: 250.0 GB, 250059350016 bytes
240 heads, 63 sectors/track, 32301 cylinders
Units = cylindry of 15120 * 512 = 7741440 bytes

 Device   Boot      Start         End      Blocks   Id  System
/dev/sdb1               1       32301   244195528+  83  Linux
------------------------------------------------------------------------

------------------------------------------------------------------------
#fsck /dev/sdb1
fsck 1.39 (29-May-2006)
e2fsck 1.39 (29-May-2006)
Couldn't find ext2 superblock, trying backup blocks...
fsck.ext3: Bad magic number in super-block while trying to
open /dev/sdb1

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>
------------------------------------------------------------------------

When I do "mount /dev/sdb1 /mnt/zaloha" at /mnt/zaloha I see that old
Windows NTFS partition that I already deleted (There are "Program
Files", "WINDOWS", ...). I don't understand why (somewhere I read that
ext3 start writing at the middle of the disk space to prevent
defragmentation).


-- 
gentoo-user@gentoo.org mailing list

Reply via email to