I have had similar experiences, though with no fatal results.
Sometimes I see the error message, it claims to have fixed the problem, yet
sometimes after another reboot done properly the same error.
I no longer use CF cards, but either the flash memory supplied with the HP thin
clients, or Transcend replacements. Not sure that really makes any difference.
So far, knock on wood, I have yet to have a total failure.
Looking forward to the 1.1.5 release.
John Novack
Lonnie Abelbeck wrote:
AstLinux users,
As Martin demonstrated the consistent perfect storm of media and hardware where
pulling-the-plug is causing corruption "e2fsck -p" can't fix without human
interaction.
After much googling and research it seems "e2fsck -p" will not automatically fix common disk corruption while
"e2fsck -y" does. "e2fsck -y" is commonly used in these situations, for example
"FSCKFIX=yes" in Ubuntu.
Martin has demonstrated that using "e2fsck -y" solves his startup e2fsck
failures.
This change has been added to AstLinux and will be a part of AstLinux 1.1.5 to
be released in the not too distant future.
Thanks to Martin for the hours of testing and detailed results.
Lonnie
On Apr 1, 2014, at 6:05 PM, Martin Sunstrum wrote:
Hello,
I have an Astlinux installation using the latest 1.1.4-Asterisk-11.7.0 for our Soekris net5501 hardware.
Astlinux is installed on Sandisk compact flash card.
In our situation, I cannot guarantee our users will not do a hard power-down by unplugging the power cord.
Also, usage of a UPS is not an option for these installations.
But I wasn’t too concerned, because I would expect there would be very few configuration changes / writes to flash occurring in this system.
Once the system is setup, it might be year(s) before the configuration will
ever be changed.
But what I have noticed is that if I perform power cord unplug tests, I see that in about 30% of the tests, fsck will fail, requiring manual intervention to run a fsck fixup. In the other 70% of cases, fsck will detect errors, but will be able to fix them up, and bootup occurs properly.
For the 30% fsck failure rate, the console message is as follows:
Configuring for unionfs...
Checking asturw filesystem
ASTURW: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
Fsck detected errors on /dev/sda2 (4)
execute fsck -t ext2 /dev/sda2 to attempt to repair errors manually.
Few questions / notes
- I am using high quality Sandisk Ultra / Ultra II compact flash disks
- During these powerdown tests, Asterisk is quite idle. Only one
device is registered, no active calls on the go.
- Is this the expected hard fsck failure rate for ext2 filesystem ?
- Is there an option to run Astlinux with a ext3 filesystem for
/dev/sda2 ?
Thanks, Martin
------------------------------------------------------------------------------
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
[email protected].
------------------------------------------------------------------------------
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
[email protected].
--
Dog is my Co-pilot
------------------------------------------------------------------------------
_______________________________________________
Astlinux-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/astlinux-users
Donations to support AstLinux are graciously accepted via PayPal to
[email protected].
