Re: [arch-general] systemd fsck
On Sat, Aug 11, 2012 at 6:27 AM, David Benfell benf...@parts-unknown.org wrote: 2) But I did notice an error that worried me--just because it looks worrying--as it came up: Aug 09 13:34:36 graton systemd-fsck[270]: /dev/sda3 is mounted. Aug 09 13:34:36 graton systemd-fsck[270]: e2fsck: Cannot continue, aborting. Aug 09 13:34:36 graton systemd-fsck[270]: fsck failed with error code 8. Aug 09 13:34:36 graton systemd-fsck[270]: Ignoring error. Aug 09 13:34:36 graton systemd-fsck[289]: /dev/sdb1: clean, 398077/33554432 files, 27916145/134217728 blocks Aug 09 13:34:36 graton systemd-fsck[287]: /dev/sdb3: clean, 647214/21102592 files, 26531961/84405504 blocks Aug 09 13:34:36 graton systemd-fsck[348]: /dev/sda4: clean, 1650719/59490304 files, 57620902/237931957 blocks Aug 09 13:34:37 graton systemd-fsck[320]: /dev/sda1: clean, 33/10040 files, 22152/40160 blocks Aug 09 13:34:37 graton systemd-fsck[293]: /dev/sdb2: clean, 4926903/67125248 files, 195736925/268500992 blocks /dev/sda3 is the root partition. Does your kernel have the ro option specified? I know little about this, but I think ext34 partitions cannot be checked while mounted read-write and the usual way of doing this for the root partition has been to add ro to the kernel command line, and to remount the root partition read-write after checking it. (Though running the check from initramfs might be an even better method, Arch here has an option for that.) -- Mantas Mikulėnas
Re: [arch-general] systemd fsck
On Sat, Aug 11, 2012 at 8:57 AM, David Benfell benf...@parts-unknown.orgwrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I just moved my desktop to systemd, and saw a couple things as I booted it for the first time: 1) It is *fast*. Let me say that again. It is *fast*. I have never seen a system come up this fast. Critics of systemd might want to consider that. 2) But I did notice an error that worried me--just because it looks worrying--as it came up: Aug 09 13:34:36 graton systemd-fsck[270]: /dev/sda3 is mounted. Aug 09 13:34:36 graton systemd-fsck[270]: e2fsck: Cannot continue, aborting. Aug 09 13:34:36 graton systemd-fsck[270]: fsck failed with error code 8. Aug 09 13:34:36 graton systemd-fsck[270]: Ignoring error. Aug 09 13:34:36 graton systemd-fsck[289]: /dev/sdb1: clean, 398077/33554432 files, 27916145/134217728 blocks Aug 09 13:34:36 graton systemd-fsck[287]: /dev/sdb3: clean, 647214/21102592 files, 26531961/84405504 blocks Aug 09 13:34:36 graton systemd-fsck[348]: /dev/sda4: clean, 1650719/59490304 files, 57620902/237931957 blocks Aug 09 13:34:37 graton systemd-fsck[320]: /dev/sda1: clean, 33/10040 files, 22152/40160 blocks Aug 09 13:34:37 graton systemd-fsck[293]: /dev/sdb2: clean, 4926903/67125248 files, 195736925/268500992 blocks /dev/sda3 is the root partition. - -- David Benfell benf...@parts-unknown.org -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQJdEsAAoJELT202JKF+xpR8EP/RAqqrPz2pumaHET2XLI97UC zd52iPPuc8nh75Xh8Jd5x0dPkd4xuGtRCiu8pRSLgX63o3iAOQtMcwFsBaOk0mN6 gjwJLbi0DM2VIYrlGS9VpG86w30uVhQLuuFwT4WasLJ5pKLfbKSw5lEXp56WQ597 qZmZ+L04MzkKKLAk4UENywF0hWy4fsDGgOPVg1nfhHJyFAd6aRtqxNSE4waoWAdI HjdAx5SYIDnu69O/UhqJ1GJOEiJxZaQYslQjmGYhHFDJfE1NJuDcY6XM+LeDGeyc ibKaDD96hTpL5meJAV+ZtglMJH9cRtNX69jqT5wnX141lOSXf19ybD7TRfXyMilV rBZfxfu1crDp4osbBYrMeRxYoK/Wr0HBWoknS6+RhpOheLUCMvV+xwcb4HMvrnKk 7i+LVCdNgb2Ul/vsG/MDZURgfKAgaYLtGMca2k8Ms1Q1paIkieD9fJg6sC8cbPNo yO9KfXsq8K4DnPwEJu0pJoOFr0lxPDqk2FFgBJnEjcpHVJqV4aqSTwgDcA0EzKw0 7wgAmczBbgUKxCoQehavsRRTm8QqjbM6yjCrwp44Ek4auL5taog32LnEw/GVreTh vOHNtMyOC6GzZfOJixEc5QmZx2J6iI9L9/MX0oEJiZcDh3gGRgfYUwFEdF+R+CfC h1s40baqzeVk/l/INX+V =ijAC -END PGP SIGNATURE- An error code of 8 for fsck means an operational error/general failure. Do you get this error every time you boot or is it a one off thing? Have you tried running it manually? FWIW, I don't think mounting root without the ro option should be causing this problem, then again it is better to check and see if it works. -- Aurko Roy GPG key: 0x20C5BC31 Fingerprint:76B4 9677 15BE 731D 1949 85BA 2A31 B442 20C5 BC31
Re: [arch-general] systemd fsck
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 08/11/2012 04:09 AM, Mantas Mikulėnas wrote:
On Sat, Aug 11, 2012 at 6:27 AM, David Benfell
benf...@parts-unknown.org wrote:
2) But I did notice an error that worried me--just because it
looks worrying--as it came up:
Aug 09 13:34:36 graton systemd-fsck[270]: /dev/sda3 is mounted.
Aug 09 13:34:36 graton systemd-fsck[270]: e2fsck: Cannot
continue, aborting. Aug 09 13:34:36 graton systemd-fsck[270]:
fsck failed with error code 8. Aug 09 13:34:36 graton
systemd-fsck[270]: Ignoring error. Aug 09 13:34:36 graton
systemd-fsck[289]: /dev/sdb1: clean, 398077/33554432 files,
27916145/134217728 blocks Aug 09 13:34:36 graton
systemd-fsck[287]: /dev/sdb3: clean, 647214/21102592 files,
26531961/84405504 blocks Aug 09 13:34:36 graton
systemd-fsck[348]: /dev/sda4: clean, 1650719/59490304 files,
57620902/237931957 blocks Aug 09 13:34:37 graton
systemd-fsck[320]: /dev/sda1: clean, 33/10040 files, 22152/40160
blocks Aug 09 13:34:37 graton systemd-fsck[293]: /dev/sdb2:
clean, 4926903/67125248 files, 195736925/268500992 blocks
/dev/sda3 is the root partition.
Does your kernel have the ro option specified? I know little
about this, but I think ext34 partitions cannot be checked while
mounted read-write and the usual way of doing this for the root
partition has been to add ro to the kernel command line, and to
remount the root partition read-write after checking it. (Though
running the check from initramfs might be an even better method,
Arch here has an option for that.)
You're absolutely right that ext{2,3,4} partitions need to be
read-only for fsck. The latter throws up a very scary warning if you
try to run it on a partition mounted read-write. Here's the kernel
line from /boot/grub/menu.lst (haven't converted to grub2 yet):
kernel /vmlinuz-linux
root=/dev/disk/by-uuid/a7f84383-2cc2-4d70-adb5-3bf909a3f99b loglevel=3
ro quiet splash
resume=/dev/disk/by-uuid/2d185a12-115f-4f93-99a3-bfca4d0fc216
init=/bin/systemd
- --
David Benfell
benf...@parts-unknown.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQIcBAEBAgAGBQJQJu57AAoJELT202JKF+xp5BcP/RjXMcDSoCJBj2rDVGQdtu80
fbEnNDfvL8a5ucuBn4jPAIdad9/QKJ9UgsIfRo31HJXJU4hNfoxCRvEDTG1f4oCB
Y7bfqq89UyAtyLCOUBKGUbUGqzSyFrwuPa+ugTTKlIh58Gr1kfHaI1PMP4qoWr/z
iUq6YpsxPCV4K0BsK6aN5aG6+zis4sAw4NKW3X2DZyM0zMJcetiuKYEAANSVayGN
EA1HZz0JQwt21rpiSaWMmF46Q7IP/LqiJ7LPC2eO4wX72DZMvwowexFx1IsDpLfc
Yr/AZ8WcoA6Zpvc1Ze+epu1Pr/QdgdZgZ/1FvMEupNkHJ4Pxw4mAlU+qSWpLVFEz
QEgyIuVwxorTcmR6pzaimQNaZv80BTUXC6xQYAwmtlREPx7HTQxRMu5+q+4x8DIK
TxvSLkn3RrzIEpFo3h4+8eW07V2Nliqs+UUEWBr/s+LO2ue53YO7aGmIb0JR8ist
B4NlDiyKy6OT0QWI2nvpwLu+23HtwIfgn/r/ExcKE+oGxYTAjZwZyZV7Y6xYsT5v
nHh5/USE0qvyEXvPcDr7SOI62RAUzXqznYorcaMxovagtT1tcoxuPn6VdijUss02
siXHXNliA9kjIrrBv1WQnsacdF93Skoso6/6o5393tFXbHNzG85dxjPmS7PVWdMp
eXITfVi6qK0syYco8DxQ
=nv3C
-END PGP SIGNATURE-
Re: [arch-general] systemd fsck
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 08/11/2012 05:26 AM, Aurko Roy wrote: An error code of 8 for fsck means an operational error/general failure. Do you get this error every time you boot or is it a one off thing? Have you tried running it manually? To the first question, I don't know. I know I have occasionally--rarely enough that I forget--had trouble with large partitions (it didn't seem to appear before I had disks that had partitions larger than 500GB) where I needed to run e2fsck on them to clear a warning. This didn't even occur to me as something to check because I was focused on the system coming up for the first time under systemd. So I rebooted off a CD-ROM and ran e2fsck manually (with -fy), it ran cleanly, and when I rebooted off the hard drive, it came up cleanly. Thanks! - -- David Benfell benf...@parts-unknown.org -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQJvHwAAoJELT202JKF+xpz7AP/01maId1jpRXB8vd215/hqL/ ApsWMe432qPOFO89jcsi4OHUdqp6NRWDLMZlMwP4/pEvNubYZ5zOq32GHsAGc4JU 7L1gWMta8MfBWNM5h4iQfeI2qtpgnio9t9rUJvkljQs7vyxDOPHyRL6dvvK5Tkoy eEoSpszOiI5u5JSSkfANOCFPc2FGYUOlkQNAUTzx9DCR08rX47osYDBnf/Vyr3q2 IOKvnXVEl8sH+vRcUWTkowN9nnw0ForUTLj2xFKmksX73BCPugRsQbqwnJOwMQ+k PTL5ah7UY4Y0jzTXumu7fYKdQJUra8llPnGeLf6Lkb0ZAK04wel4hV7hAX5T7D63 pbcNRVcj+6gt91QPi5iMUmjQdEMz4NRfMWbrEzm0lmNZn+IoG9UFQ4JpZrCidI92 n4yGhwERIvnS2CBOWgIAcTWXHc8Ktfy0fRBFnU1HcB4/zhoOr6+43LeUvt4NsRdC 801gvf5rNCT8IB8K6zqGrYv48n5As1hsiIX+z66hgmc1FD7Rt7gvHCLAFSPFZ7s8 i8rmpesIeAKJxpXJblTPmOCw1QkzcOTKFKnsqBBTx/g9LTBy2ux1BaXnKHRINzBq dBLLi3Ev+idKxpXjpmuqlXzRKtis7n2BfPpOTO0qnJPK5pCfyn74lB1YHFEeYlXO 88O8g8G2O6JOkFpVX7vr =HOz6 -END PGP SIGNATURE-
[arch-general] systemd fsck
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, I just moved my desktop to systemd, and saw a couple things as I booted it for the first time: 1) It is *fast*. Let me say that again. It is *fast*. I have never seen a system come up this fast. Critics of systemd might want to consider that. 2) But I did notice an error that worried me--just because it looks worrying--as it came up: Aug 09 13:34:36 graton systemd-fsck[270]: /dev/sda3 is mounted. Aug 09 13:34:36 graton systemd-fsck[270]: e2fsck: Cannot continue, aborting. Aug 09 13:34:36 graton systemd-fsck[270]: fsck failed with error code 8. Aug 09 13:34:36 graton systemd-fsck[270]: Ignoring error. Aug 09 13:34:36 graton systemd-fsck[289]: /dev/sdb1: clean, 398077/33554432 files, 27916145/134217728 blocks Aug 09 13:34:36 graton systemd-fsck[287]: /dev/sdb3: clean, 647214/21102592 files, 26531961/84405504 blocks Aug 09 13:34:36 graton systemd-fsck[348]: /dev/sda4: clean, 1650719/59490304 files, 57620902/237931957 blocks Aug 09 13:34:37 graton systemd-fsck[320]: /dev/sda1: clean, 33/10040 files, 22152/40160 blocks Aug 09 13:34:37 graton systemd-fsck[293]: /dev/sdb2: clean, 4926903/67125248 files, 195736925/268500992 blocks /dev/sda3 is the root partition. - -- David Benfell benf...@parts-unknown.org -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.19 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBAgAGBQJQJdEsAAoJELT202JKF+xpR8EP/RAqqrPz2pumaHET2XLI97UC zd52iPPuc8nh75Xh8Jd5x0dPkd4xuGtRCiu8pRSLgX63o3iAOQtMcwFsBaOk0mN6 gjwJLbi0DM2VIYrlGS9VpG86w30uVhQLuuFwT4WasLJ5pKLfbKSw5lEXp56WQ597 qZmZ+L04MzkKKLAk4UENywF0hWy4fsDGgOPVg1nfhHJyFAd6aRtqxNSE4waoWAdI HjdAx5SYIDnu69O/UhqJ1GJOEiJxZaQYslQjmGYhHFDJfE1NJuDcY6XM+LeDGeyc ibKaDD96hTpL5meJAV+ZtglMJH9cRtNX69jqT5wnX141lOSXf19ybD7TRfXyMilV rBZfxfu1crDp4osbBYrMeRxYoK/Wr0HBWoknS6+RhpOheLUCMvV+xwcb4HMvrnKk 7i+LVCdNgb2Ul/vsG/MDZURgfKAgaYLtGMca2k8Ms1Q1paIkieD9fJg6sC8cbPNo yO9KfXsq8K4DnPwEJu0pJoOFr0lxPDqk2FFgBJnEjcpHVJqV4aqSTwgDcA0EzKw0 7wgAmczBbgUKxCoQehavsRRTm8QqjbM6yjCrwp44Ek4auL5taog32LnEw/GVreTh vOHNtMyOC6GzZfOJixEc5QmZx2J6iI9L9/MX0oEJiZcDh3gGRgfYUwFEdF+R+CfC h1s40baqzeVk/l/INX+V =ijAC -END PGP SIGNATURE-
