dear all,
a while back I posted to this list because my file systems on LVM over
RAID1 would not mount cleanly anymore after upgrade from sarge to
etch. this weekend I had time to poke around in the data on both the
disks, and found out what was wrong.
as it turns out, since almost a year, *no*
> yes, / on md0 does get fsck'd cleanly, whether in single boot or
> 'normal' boot. I can get into a root shell w/o any filesystem related
> errors.
Good. Now if only debian's single-user mode didn't start all kinds of
extras that need /usr and /var
> the problem are all other mounts, which
On Mon, May 07, 2007 at 10:38:30AM +0200, David Fuchs wrote:
> On 5/6/07, Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
> >On Sun, May 06, 2007 at 07:27:26PM +0200, David Fuchs wrote:
> yes, / on md0 does get fsck'd cleanly, whether in single boot or
> 'normal' boot. I can get into a root shell w
On 5/6/07, Douglas Allan Tutty <[EMAIL PROTECTED]> wrote:
On Sun, May 06, 2007 at 07:27:26PM +0200, David Fuchs wrote:
> I mounted (read-only) some of the virtual volumes, to see if the data is
> still there... it seems as if there is some 'offset' on the file system,
> i.e.
> when looking at som
On Sun, May 06, 2007 at 07:27:26PM +0200, David Fuchs wrote:
> I mounted (read-only) some of the virtual volumes, to see if the data is
> still there... it seems as if there is some 'offset' on the file system,
> i.e.
> when looking at some file it contains stuff that should be in a completely
> d
I mounted (read-only) some of the virtual volumes, to see if the data is
still there... it seems as if there is some 'offset' on the file system, i.e.
when looking at some file it contains stuff that should be in a completely
different file... or it tells me attempt to access beyond end of device.
thanks for the help.
here's what I did: I booted single-user with init=/bin/sh, and md0 mounted
read-only. everything works so far, I get to the shell w/o any errors.
at this point, md1 is not started but I can start it with mdadm -A
--auto=yes /dev/md1. mdadm -D /dev/md{0,1} shows state: clean
On Sun, May 06, 2007 at 03:25:02PM +0200, David Fuchs wrote:
> I have just upgraded my sarge system to etch, following exactly the upgrade
> instructions at http://www.us.debian.org/releases/etch/i386/release-notes/.
>
> now my system does not boot correctly anymore... I'm using RAID1 with two
> d
hi all,
I have just upgraded my sarge system to etch, following exactly the upgrade
instructions at http://www.us.debian.org/releases/etch/i386/release-notes/.
now my system does not boot correctly anymore... I'm using RAID1 with two
disks, / is on md0 and all other mounts (/home/, /var, /usr et
9 matches
Mail list logo
