Re: Forced to run fsck manually on unattended system

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]



I have found a way around my problem of freezing on startup.

The startup script is called from /etc/rc.d/functions

You simply find the section where the fsck command is called and edit the
flags to remove -a and add -y.

I understand that my data may end up getting a little frazzled, but
hopefully turning off disk caching with hdparm (this is a low performance
system anyway) should sort things out.

For what it's worth I'm using SSDs and I've found that a journalled file
system (ext3/4) struggled a bit more with sudden power outages, but this is
all emperical.

Many thanks for all your suggestions.



--
View this message in context: http://archlinux.2023198.n4.nabble.com/Forced-to-run-fsck-manually-on-unattended-system-tp4684861p4684978.html
Sent from the arch general mailing list archive at Nabble.com.


[Index of Archives]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [Share Photos]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]
  Powered by Linux