From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1H9mdQ-0000VZ-EK for garchives@archives.gentoo.org; Wed, 24 Jan 2007 18:14:12 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id l0OID6eV011086; Wed, 24 Jan 2007 18:13:06 GMT Received: from smtp.seznam.cz (smtp.seznam.cz [194.228.32.43]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id l0OI9Dmn006777 for ; Wed, 24 Jan 2007 18:09:13 GMT Received: (qmail 3241 invoked from network); 24 Jan 2007 18:09:09 -0000 Received: from unknown (HELO ?89.103.43.214?) (jcd@seznam.cz@89.103.43.214) by cetus.go.seznam.cz with ESMTPA; 24 Jan 2007 18:09:09 -0000 X-Seznam-User: jcd@seznam.cz Subject: Re: [gentoo-user] ext3 partition dissapeared :( From: jcd To: gentoo-user@lists.gentoo.org In-Reply-To: <200701232255.15179.alan@linuxholdings.co.za> References: <1169550701.11188.27.camel@paulie.kitchen> <1169569078.10964.10.camel@paulie.kitchen> <20070123184701.f2d0761d.hilse@web.de> <200701232255.15179.alan@linuxholdings.co.za> Content-Type: text/plain; charset=UTF-8 Date: Wed, 24 Jan 2007 19:09:09 +0100 Message-Id: <1169662149.11076.11.camel@paulie.kitchen> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 X-Mailer: Evolution 2.8.2.1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by robin.gentoo.org id l0OID6ei011086 X-Archives-Salt: 9ee644cd-c09e-49a0-9880-a4da1093c8ed X-Archives-Hash: 7e0d3ba556f14146673529eb180f8cfc Alan McKinnon p=C3=AD=C5=A1e v =C3=9At 23. 01. 2007 v 21:55 +0100: > On Tuesday 23 January 2007 19:47, Hans-Werner Hilse wrote: >=20 > > Did you reboot between changing the partition layout and creating > > that new partition (and moving data)? Otherwise the kernel wouldn't > > be aware of the new partition layout. Well, if everything you wrote > > is correct, that data should have ended up on that former Windows > > partition and that partition should now be an ext3 one. But if you > > just didn't care and mounted the old linux partition (sdb2 at that > > point in time before the new partition layout), copied data and you > > _then_ rebooted -- then you would have written your data to a > > partition that was only a reminiscence in the kernel's structures and > > not > > corresponding to what cfdisk wrote to the HD. That would be an > > explanation why the next boot failed. > > > > > 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). > > > > Deleting the partition is something that only affects the boot > > sector. Ext3 should in fact have overwritten this with it's first > > superblock. So the mkext2fs you issued did definitively hit the wrong > > partition. > > > > So my suggestion is: try "gpart -w ext2,1.5 /dev/sdb" to find your > > partition (even better: write back the backup you've made from the > > old partition table. Errrm...) >=20 > Some background here to elaborate on what Hans has said: >=20 > It looks like when you moved the data onto the new partition, it got=20 > written somewhere on the disk. However, the kernel's idea of how the=20 > partitions are laid out at that time and what fdisk just wrote to the=20 > disk probably don't agree and the kernel had got it wrong.... This does= =20 > happen when you delete two or more partitions and create one large one. >=20 > That's the bad news. The good news is that unless you did something to=20 > wipe the disk clean, the data is there somewhere and you need to find=20 > it. Hans' gpart command will search the disk looking for the sequence=20 > of data that is found at the start of a filesystem, and will then make=20 > a smart estimate as to what the partition ought to look like. >=20 > The next good news is that you can create and delete partitions many=20 > times and still get the data back intact as long as you don't overwrite= =20 > it. fdisk updates the partition table right at the start of the disk=20 > and does nothing else so you can always undo these changes. Until you=20 > are happy that everything is back it will be smart to mount this=20 > partition read-only so it can't be changed: >=20 > mount -o rw /dev/sdb1 /path/to/mount/point >=20 > You say in your original mail that after moving the data "everything wa= s=20 > fine". What exactly do you mean by that: >=20 > 1. The command ended without failure so you assume it moved stuff=20 > correctly, or > 2. You proved the move was done by mounting the partition and all your=20 > files were there, or > 3. Some other reason? >=20 > alan >=20 --=20 gentoo-user@gentoo.org mailing list