Date: Fri, 10 Jan 2014 14:10:17 +0700 From: Olivier Nicole <olivier.nicole@cs.ait.ac.th> To: iamatt <iamatt@gmail.com> Cc: eras mus <erasmu@gmail.com>, Polytropon <freebsd@edvax.de>, FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Server hang : fsck Message-ID: <CA%2Bg%2BBvg1-ikvKFS0ABiQhmb0akG2cQCLT16zS2aB62kL9gymgw@mail.gmail.com> In-Reply-To: <CAEeRwNVVstau-cn0GAKXvS=0FT0kmbkm-5whgAJ9OdhYacn1Mg@mail.gmail.com> References: <CALeO_hPB=2H9cF0LJDof1Wdqq3JGa7LiinQtOrGGVL8FwGnxPw@mail.gmail.com> <20140109131515.fdf53ef6.freebsd@edvax.de> <CALeO_hPnSDHwBCQGhcwpOZeLpp71zp5epNR8cnMA9CeLWePkcA@mail.gmail.com> <CAEeRwNVVstau-cn0GAKXvS=0FT0kmbkm-5whgAJ9OdhYacn1Mg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
> 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. At same time, it is a good exercise to learn some new commands, how to copy file systems... Olivier > On Jan 10, 2014 1:04 AM, "eras mus" <erasmu@gmail.com> 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 <freebsd@edvax.de> 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" >> > _______________________________________________ > 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"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2Bg%2BBvg1-ikvKFS0ABiQhmb0akG2cQCLT16zS2aB62kL9gymgw>