Date: Mon, 12 Dec 2005 13:50:09 +0100 From: Ferruccio Zamuner <nonsolosoft@diff.org> To: freebsd-geom@freebsd.org Cc: nonsolosoft@diff.org Subject: Re: from vinum on FreeBSD 4.x to gvinum on 5.4 and 6.0 Message-ID: <439D7201.8010301@diff.org> In-Reply-To: <439CB6C0.30109@diff.org> References: <439CB6C0.30109@diff.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Ferruccio Zamuner wrote: > Actually I was very interested to content of partition "/vinum/sicuro" > and it was simple: > # dd if=/dev/ad5s1e of=/usr/vinum_sicuro.bin skip=265 count=2097152 > # mdconfig -a -t vnode -f /usr/vinum_sicuro.bin -u 1 > # bsdlabel -w md1 auto > # mount /dev/md1c /mnt/ > > Then I recover first data contents easly. I thought to recover, ls shows me the root directory of my ex-sicuro partition, but I'm not able to access to contents. Then I thought about a consistent trouble to fix with fsck: root@k7# fsck -t ufs /dev/md1c ** /dev/md1c CANNOT READ BLK: 20779040 CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 20779040, 20779041, 20779042, 20779043, /dev/md1c: NOT LABELED AS A BSD FILE SYSTEM (unused) root@k7# fsck -t ufs /dev/md1 ** /dev/md1 CANNOT READ BLK: 20779040 CONTINUE? [yn] y THE FOLLOWING DISK SECTORS COULD NOT BE READ: 20779040, 20779041, 20779042, 20779043, ioctl (GCINFO): Inappropriate ioctl for device fsck_ufs: /dev/md1: can't read disk label But it doesn't fix anything. Any suggestion? Bye, \fer
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?439D7201.8010301>