From owner-freebsd-questions@FreeBSD.ORG Fri Jan 10 07:07:52 2014 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 18589971 for ; Fri, 10 Jan 2014 07:07:52 +0000 (UTC) Received: from mail-wg0-x236.google.com (mail-wg0-x236.google.com [IPv6:2a00:1450:400c:c00::236]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 990D41DEB for ; Fri, 10 Jan 2014 07:07:51 +0000 (UTC) Received: by mail-wg0-f54.google.com with SMTP id x13so757214wgg.21 for ; Thu, 09 Jan 2014 23:07:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=PIZ6Kth5A+8lXIq4UGqqR6HBSLtUWKXjDf+lz9+M2jk=; b=d/IpSbCf4diCufhP/oa3Fz6A3bRtTtSn3uifUO4dyAkrpTfEAMXqJep5BW/y+8ZkF4 /2cpODLAPWNGr2tIPfQDB0DLCo8CDMovlLuOoUBjn0lSxb4D6S/Av5m7zSK5Nkp1AIi/ ogoYfUEiEvYYcFH10sT2BXv52aTQ1yVdrG0yTeFOFd9SQGTPnNyUUQgHBklfPEioNXrV xxnC0HA+OE7Dth6mBmVs/wd6pZfHimz3yiBDqwoZcyUmDXAAvlCeTmmZ3XWXBQ+HKDwr fr4/tIKadRaPjbfY3vLCC9dcI+Pep8hA6lK+U8u44CXezH9zhVjIoSwLDq+82udstHJM u/tw== MIME-Version: 1.0 X-Received: by 10.180.149.175 with SMTP id ub15mr1094207wib.44.1389337670083; Thu, 09 Jan 2014 23:07:50 -0800 (PST) Received: by 10.216.108.195 with HTTP; Thu, 9 Jan 2014 23:07:50 -0800 (PST) Received: by 10.216.108.195 with HTTP; Thu, 9 Jan 2014 23:07:50 -0800 (PST) In-Reply-To: References: <20140109131515.fdf53ef6.freebsd@edvax.de> Date: Fri, 10 Jan 2014 01:07:50 -0600 Message-ID: Subject: Re: Server hang : fsck From: iamatt To: eras mus Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.17 Cc: Polytropon , FreeBSD Mailing List X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 10 Jan 2014 07:07:52 -0000 Seem like a lot of wasted time trying to revive broken hardware. We all know where this is headed. Why not line up your replacement hw or VM and just restore from backups. On Jan 10, 2014 1:04 AM, "eras mus" wrote: > Dear List, > > I tried > > fsck -yf /usr yesterday evening at 6 pm. > Images are here > http://picpaste.com/img1-4zq2ytTk.jpg > http://picpaste.com/img2-uXfJ8REF.jpg > > Left it running and morning 10 a.m today found the message > > FILE SYSTEM DIRTY > FILE SYSTEM MODIFIED > rerun fsck > > Then went in setup and changed boot made APIC disabed. > and went into boot option 2 boot ACPI disabled. > > > It gave the following message: > > The following filesystem HAD AN UNEXPECTED INCONSISTENCY > ufs: /dev/ad4s1e(/usr) > Automatic file system check failed: help! > Jan 10 16:16:59 init:/bin/sh on etc/rc terminated abnormally, going to > single user mode > > > As advice by Polytropon burnt alive CD And ran fsck manually. > # fsck -yfv /dev/ad4s1a > # fsck -yfv /dev/ad4s1d > > are successful. > But when ran > # fsck -yfv /dev/ad4s1e > > It was messages as in > > http://picpaste.com/img3-It4JOaph.jpg > > > > > > > > > On 1/9/14, Polytropon wrote: > > On Thu, 9 Jan 2014 17:03:51 +0530, eras mus wrote: > >> dear List > >> > >> I have attached the snapshots of fsck. > > > > This list does not allow attachments. You should either copy > > the printed text into the message or upload images somewhere > > and provide an URL. > > > > > > > >> Whether fsck is fixing the errors of /usr. Or just sitting in > infinite > >> loop? > > > > Transfering your system to a new disk aside - THAT is the REALLY > > STRANGE question here! The fsck program does not simply hang in > > infinite loops. This indicates a severe problem probably with > > your hardware, and that has not neccessarily to be the disk. > > > > You should really try step by step, in _small_ steps. Can you > > boot the system from a live CD? If yes, do that. Then check > > each file system separately: > > > > # fsck -yfv /dev/ad4s1a > > # fsck -yfv /dev/ad4s1d > > # fsck -yfv /dev/ad4s1e > > # fsck -yfv /dev/ad4s1f > > # fsck -yfv /dev/ad4s1g > > > > and so on. If it helps, try that with ACPI disabled again. There > > is no real use in trying to copy a possibly damaged file system > > to a new disk. Before you copy, make sure they're all consistent. > > > > > > > > By the way, in addition to the mentioned ways to copy an OS and > > and data, there's still the "old school" toolset that can be used: > > First initialize the disks (for example with gpart, use MBR only > > if you need to, otherwise go with GPT). Then format the new > > partitions (newfs) and install the boot blocks (or boot partition > > for GPT). Additionally make sure to apply labels to the file > > systems (so you don't have to mess with device names in the > > future). Finally, use ye olden dump and restore. > > > > Here's an example. Let's assume /dev/ad4 is your designated new > > disk, /dev/ad6 your current disk (failing, will be abandoned). > > The target disk has been partitioned with GPT, the file systems > > have been initialized already. The source disk is _not_ mounted. > > > > # mount /dev/ad4p2 /mnt > > # cd /mnt > > # dump -0 -L -a -u -f - /dev/ad6s1a | restore -r -f - > > > > # mount /dev/ad4p3 /mnt/tmp > > # cd /mnt/tmp > > # dump -0 -L -a -u -f - /dev/ad6s1d | restore -r -f - > > > > # mount /dev/ad4p4 /mnt/var > > # cd /mnt/var > > # dump -0 -L -a -u -f - /dev/ad6s1e | restore -r -f - > > > > # mount /dev/ad4p5 /mnt/usr > > # cd /mnt/usr > > # dump -0 -L -a -u -f - /dev/ad6s1f | restore -r -f - > > > > # mount /dev/ad4p6 /mnt/home > > # cd /mnt/home > > # dump -0 -L -a -u -f - /dev/ad6s1g | restore -r -f - > > > > # cd / > > # umount /mnt > > > > In this example, /mnt will be the subtree that later on becomes /. > > Of course you have to check which things apply to _your_ setup! > > > > Note that you can also do that easily from a live CD. Note that > > for this task, only the destination media has to be mounted, the > > source media usually not. By using this approach, you can make > > sure that all file attributes get transferred correctly. > > > > You can find further inspiration around here: > > > > http://www.wonkity.com/~wblock/docs/html/disksetup.html > > > > > > > > -- > > Polytropon > > Magdeburg, Germany > > Happy FreeBSD user since 4.0 > > Andra moi ennepe, Mousa, ... > > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to " > freebsd-questions-unsubscribe@freebsd.org" >