Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, 15 Sep 2010 17:11:30 -0400 (EDT), d...@safeport.com wrote: I have had two systems die with bad disks. Personally, I never had trouble with bad disks, but with defective file systems (origin unknown), and follow-up trouble caused by background fsck that prevented me many years from accessing my data. Going the old fashioned way brought everything back. Long story short: A present .snapshot from the 1st background fsck (which was introduced as default in 5.0, as far as I remember) caused fsck from working as expected; after removing this file, I got all the missing data back. Luckily, the problem didn't seem to be related to actual disk failure, as SMART data didn't give a hint about that. I did work with a 1:1 dd copy anyway. Modern disks die silently which I think is too bad. You usally see messages in dmesg / console that indicate disk trouble. In mos cases, those messages say that the disk is already dying - it's too late for repair. So time for backup and replacement. Seems that this is the result of continuing bigger and cheaper disks... If this is happening and you have data you want to recover you might try booting in single user move and using fsck manually on each slice. The fsck program operates on partitions, not on slices. Terminology, dear Watson. :-) -- 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-unsubscr...@freebsd.org
How to prevent system to launch interactive fsck after improper shutdown and reboot?
Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yuri I think this might do your trick: fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. fsck_y_flags= # Additional flags for fsck -y The reason for this to get interactively is because this might messup with your filesystem, and you are the one responsible for your filesystem, not us or the autmated system. So in case you want to play with that, that's entirely up to you. In addition, I can imagine that companies (been there done it) do not want to fsck -y by default, this because of the mentioned potential corruption and dataloss. Thanks remko p.s. This was found within 5 seconds in /etc/defaults/rc.conf. -- /\ Best regards, | re...@freebsd.org \ / Remko Lodder | re...@efnet Xhttp://www.evilcoder.org/ | / \ ASCII Ribbon Campaign | Against HTML Mail and News ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
El día Wednesday, September 15, 2010 a las 09:41:54AM +0300, Yuri escribió: Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yes, just do: $ echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc $ man rc.conf | col -b | fgrep fsck_ In general one should avoid unclean shutdowns. I even after such event go into single user mode and run fsck(8) by hand. HIH matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ Solidarity with the zionistic pirates of Israel? Not in my name! ¿Solidaridad con los piratas sionistas de Israel? ¡No en mi nombre! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On 15-9-2010 8:53, Matthias Apitz wrote: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc LOL, only worked with quotes, btw ;-) Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, Sep 15, 2010 at 1:59 AM, Peter Boosten pe...@boosten.org wrote: On 15-9-2010 8:53, Matthias Apitz wrote: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc LOL, only worked with quotes, btw ;-) Depends on the shell, I guess he's a bash user. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
El día Wednesday, September 15, 2010 a las 08:59:07AM +0200, Peter Boosten escribió: On 15-9-2010 8:53, Matthias Apitz wrote: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc LOL, only worked with quotes, btw ;-) no, $ sh $ echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM $ bash g...@current:/usr/home/guru echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM which shell you used? matthias -- Matthias Apitz t +49-89-61308 351 - f +49-89-61308 399 - m +49-170-4527211 e g...@unixarea.de - w http://www.unixarea.de/ Solidarity with the zionistic pirates of Israel? Not in my name! ¿Solidaridad con los piratas sionistas de Israel? ¡No en mi nombre! ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On 15-9-2010 9:07, Matthias Apitz wrote: $ sh $ echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM $ bash g...@current:/usr/home/guru echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM which shell you used? zsh. Peter -- http://www.boosten.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, Sep 15, 2010 at 2:07 AM, Matthias Apitz g...@unixarea.de wrote: El día Wednesday, September 15, 2010 a las 08:59:07AM +0200, Peter Boosten escribió: On 15-9-2010 8:53, Matthias Apitz wrote: echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc LOL, only worked with quotes, btw ;-) no, $ sh $ echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM $ bash g...@current:/usr/home/guru echo 16i[q]sa[ln0=aln100%Pln100/snlbx]sbA0D4D465452snlb xq | dc RTFM which shell you used? it doesn't work in zsh, csh, tcsh, I didn't try sh, it didn't even occur to me since I so rarely use it as an interactive shell. -- Adam Vande More ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, 15 Sep 2010 08:47:38 +0200, Remko Lodder re...@elvandar.org wrote: Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yuri I think this might do your trick: fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. fsck_y_flags= # Additional flags for fsck -y The reason for this to get interactively is because this might messup with your filesystem, and you are the one responsible for your filesystem, not us or the autmated system. So in case you want to play with that, that's entirely up to you. In addition, I can imagine that companies (been there done it) do not want to fsck -y by default, this because of the mentioned potential corruption and dataloss. Very important point. As an addition, allow me to mention background_fsck=YES as an entry in /etc/rc.conf. This will let the system boot up and perform fsck checks while the system is running - running on a maybe defective or inconsistent file system. This is dangerous, but possible. It utilizes a snapshot mechanism which can cause further trouble (lost / emptyinodes and disappearing subtrees of files). Personally, if fsck requires YOUR attention, there's usually a reason for this. The reason is possible data loss or file system corruption where YOU take the responsibility of decision, not fsck. By default, fsck does not do damaging, but under strange circumstances, it can happen. For example, if you want to do a special kind of data recovery or forensic analysis on a file system, you potentially DO NOT WANT fsck to assume y for all the questions because that can make your job harder. A common additional y flag is -f (means fsck -yf) to force all operations suggested by fsck and confirming them. -- 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-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On 09/15/10 09:47, Remko Lodder wrote: I think this might do your trick: fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. fsck_y_flags= # Additional flags for fsck -y The reason for this to get interactively is because this might messup with your filesystem, and you are the one responsible for your filesystem, not us or the autmated system. So in case you want to play with that, that's entirely up to you. In addition, I can imagine that companies (been there done it) do not want to fsck -y by default, this because of the mentioned potential corruption and dataloss. Thanks remko p.s. This was found within 5 seconds in /etc/defaults/rc.conf. Thanks Remko! I never had spare 5 secs for this :-), and now when I left my computer to friends (not computer savvy) they got into this trap. There is no database... I think installer better asks this question during installation since many users just run a desktop and -y is pretty much ok for them. Thank you again, Yuri ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, Sep 15, 2010 at 12:00 AM, Yuri y...@rawbw.com wrote: Thanks Remko! I never had spare 5 secs for this :-), and now when I left my computer to friends (not computer savvy) they got into this trap. There is no database... I think installer better asks this question during installation since many users just run a desktop and -y is pretty much ok for them. Train your friends to shut the machine down by pressing (not holding down!) the power button. On any modern machine ACPI should trigger a clean shutdown/poweroff. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: How to prevent system to launch interactive fsck after improper shutdown and reboot?
On Wed, 15 Sep 2010, Polytropon wrote: On Wed, 15 Sep 2010 08:47:38 +0200, Remko Lodder re...@elvandar.org wrote: Almost every time after improper shutdown (poweroff) and reboot I get into interactive fsck. I am being asked whole bunch of questions to which I just have to answer Y (what are my other options?) Why drop user into interactive fsck if there is not much choice anyways? Is there a way to set it up the way it doesn't drop into interactive mode? Like answer 'Y' to all questions? Yuri I think this might do your trick: fsck_y_enable=NO # Set to YES to do fsck -y if the initial preen fails. fsck_y_flags= # Additional flags for fsck -y The reason for this to get interactively is because this might messup with your filesystem, and you are the one responsible for your filesystem, not us or the autmated system. So in case you want to play with that, that's entirely up to you. In addition, I can imagine that companies (been there done it) do not want to fsck -y by default, this because of the mentioned potential corruption and dataloss. Very important point. As an addition, allow me to mention background_fsck=YES as an entry in /etc/rc.conf. This will let the system boot up and perform fsck checks while the system is running - running on a maybe defective or inconsistent file system. This is dangerous, but possible. It utilizes a snapshot mechanism which can cause further trouble (lost / emptyinodes and disappearing subtrees of files). Personally, if fsck requires YOUR attention, there's usually a reason for this. The reason is possible data loss or file system corruption where YOU take the responsibility of decision, not fsck. By default, fsck does not do damaging, but under strange circumstances, it can happen. For example, if you want to do a special kind of data recovery or forensic analysis on a file system, you potentially DO NOT WANT fsck to assume y for all the questions because that can make your job harder. A common additional y flag is -f (means fsck -yf) to force all operations suggested by fsck and confirming them. I have had two systems die with bad disks. This email contains great information and spot-on advice from my experience. When I was ready to give up on my last system I did a -yf in single user mode and was able to get most of my data because the bad sectors were in /usr/local which had many missing files and directories. Modern disks die silently which I think is too bad. If this is happening and you have data you want to recover you might try booting in single user move and using fsck manually on each slice. If you are lucky, your errors will be in /tmp or /var. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org