Hi
What's the difference between using the command "reboot" and let the keyboard trigger the "init 6" to reboot?
I notice I always get the "Filesystem not clean" message having switched over to grml when rebooting. I trigger the reboot via keyboard to issue init 6. Didn't notice so when using Debian Sarge though.
Can I rely on keyboard/HW triggers for reboot or poweroff, or I'd better type the command? Or, the Grml is more a live system which has skips some steps that normal non-live systems will do when shutdown?
I'm using the reiserfs systems.
thanks
* T mlist4suntong@yahoo.com [20060915 22:15]:
What's the difference between using the command "reboot" and let the keyboard trigger the "init 6" to reboot?
I notice I always get the "Filesystem not clean" message having switched over to grml when rebooting. I trigger the reboot via keyboard to issue init 6. Didn't notice so when using Debian Sarge though.
Hm strange. How do you trigger the reboot? Via /etc/inittab? How does your configuration look like?
Can I rely on keyboard/HW triggers for reboot or poweroff, or I'd better type the command? Or, the Grml is more a live system which has skips some steps that normal non-live systems will do when shutdown?
No, a harddisk installation of grml should work as any other harddisk system. If you notice any problems there it's a bug which has to be debugged.
I'm using the reiserfs systems.
Well, you know:
| <gorny> reiserfs, making files and wives dissapear in an instant
-- http://blogs.23.nu/ilja/stories/12795/
regards, -mi"it wasn't me, it was fortune!!!1! ;-)"ka-
On Fri, 15 Sep 2006 23:23:58 +0200, Michael Prokop wrote:
What's the difference between using the command "reboot" and let the keyboard trigger the "init 6" to reboot?
I notice I always get the "Filesystem not clean" message having switched over to grml when rebooting. I trigger the reboot via keyboard to issue init 6. Didn't notice so when using Debian Sarge though.
Hm strange. How do you trigger the reboot? Via /etc/inittab? How does your configuration look like?
$ grep -A1 CTRL-ALT-DEL /etc/inittab # What to do when CTRL-ALT-DEL is pressed. ca::ctrlaltdel:/etc/init 6
Can I rely on keyboard/HW triggers for reboot or poweroff, or I'd better type the command? Or, the Grml is more a live system which has skips some steps that normal non-live systems will do when shutdown?
No, a harddisk installation of grml should work as any other harddisk system. If you notice any problems there it's a bug which has to be debugged.
One thing is that recently I have to use bind mount for some testing, and for some weired reasons, I can't even unmount some of the bind mount points manually, especially when the /dev is bind mounted.
However, I've noticed that even I don't do anything, eg, power HD grml up, startx, quit X, reboot, I get "Filesystem not clean" as well. Just for such cases, there are far less inodes to repair.
I'm using the reiserfs systems.
Well, you know:
| <gorny> reiserfs, making files and wives dissapear in an instant
yeah, mika, I know your attitude towards reiserfs. That's why I stated it there. :-) but because of my own experience with ext3 and reiserfs, and my current environment, I have to stick to reiserfs for a while, until I can afford to buy a $20 UPS or something...
I have to say that my grml root fs, which is ext3, didn't seems to need repair. But I can't say it for sure because the repair message fill the screen so quickly even scroll up won't help. However, it shouldn't be necessary because it is more a read-only fs most of the time.
* T mlist4suntong@yahoo.com [20060916 18:15]:
On Fri, 15 Sep 2006 23:23:58 +0200, Michael Prokop wrote:
$ grep -A1 CTRL-ALT-DEL /etc/inittab # What to do when CTRL-ALT-DEL is pressed. ca::ctrlaltdel:/etc/init 6
Does changing the "/etc/init" to "/sbin/init" change anything? If *not* (I expect that), does something like:
ca::ctrlaltdel:/etc/init.d/grml-reboot
work for you and fixes the problem?
And please check that "grep umount /etc/runlevel.conf" looks like:
31 - 0,6 /etc/init.d/umountnfs.sh 40 - 0,6 /etc/init.d/umountfs 60 - 0,6 /etc/init.d/umountroot
regards, -mika-
On Sat, 16 Sep 2006 23:39:57 +0200, Michael Prokop wrote:
ca::ctrlaltdel:/etc/init.d/grml-reboot
work for you and fixes the problem?
I directly tried this. Unfortunately, problems not fixed. Still got "Filesystem is NOT clean".
And please check that "grep umount /etc/runlevel.conf" looks like:
yes, same as mine:
31 - 0,6 /etc/init.d/umountnfs.sh 40 - 0,6 /etc/init.d/umountfs 60 - 0,6 /etc/init.d/umountroot
Here is a typical error:
------------------------------- [/sbin/fsck.reiserfs (1) -- /export] fsck.reiserfs -a /dev/sda10 export: Reiserfs super block in block 16 on 0x80a of format 3.6 with standard jour nal Blocks (total/free): 1024128/11568 by 4096 bytes Filesystem is NOT clean Trans replayed: mountid 201, transid 10847, desc 4060, len 1, commit 4062, next tr ans offset 4045 Trans replayed: mountid 201, transid 10848, desc 4063, len 1, commit 4065, next tr ans offset 4048 Reiserfs journal '/dev/sda11' in blocks [18..8211]: 2 transactions replayed Checking internal tree..finished -------------------------------
This is strange, Filesystem is NOT clean, yet 0 transactions replayed:
------------------------------- % fsck -C -a -V /dev/sda6 fsck 1.39 (29-May-2006) [/sbin/fsck.reiserfs (1) -- /mnt/os12] fsck.reiserfs -a /dev/sda6 os12: Reiserfs super block in block 16 on 0x806 of format 3.6 with standard journal Blocks (total/free): 1024128/211099 by 4096 bytes Filesystem is NOT clean Replaying journal.. Reiserfs journal '/dev/sda6' in blocks [18..8211]: 0 transactions replayed Checking internal tree..finished -------------------------------
I'll exam further if it is a Reiserfs issue or grml issue...
thanks
On Sat, 16 Sep 2006 22:31:03 +0200, T wrote:
On Sat, 16 Sep 2006 23:39:57 +0200, Michael Prokop wrote:
ca::ctrlaltdel:/etc/init.d/grml-reboot
work for you and fixes the problem?
I directly tried this. Unfortunately, problems not fixed. Still got "Filesystem is NOT clean".
Hmm... the change take effect right away, right? Ie, right after I've made the change, the keyboard would then trigger grml-reboot instead of init 6, correct?
The reason that I'm asking is that, right after I tried reboot (after modifying /etc/inittab), I get the "Filesystem is NOT clean" for all my volumes. But when I reboot the 2nd time, all of them are clean now. I think at least things are improved a bit, since it was not ok for this simple case previously.
If the change to /etc/inittab take effect right away, then the only difference between the observed 2 boots is how long the volumes has been mounted, ie, how chaotic are they... one being used for about 2 weeks, one is just several minutes.
* T mlist4suntong@yahoo.com [20060917 05:15]:
On Sat, 16 Sep 2006 22:31:03 +0200, T wrote:
On Sat, 16 Sep 2006 23:39:57 +0200, Michael Prokop wrote:
ca::ctrlaltdel:/etc/init.d/grml-reboot
work for you and fixes the problem?
I directly tried this. Unfortunately, problems not fixed. Still got "Filesystem is NOT clean".
Hmm... the change take effect right away, right? Ie, right after I've made the change, the keyboard would then trigger grml-reboot instead of init 6, correct?
No. You have to either run 'telinit q' or reboot at all so init rereads the files /etc/inittab.
The reason that I'm asking is that, right after I tried reboot (after modifying /etc/inittab), I get the "Filesystem is NOT clean" for all my volumes. But when I reboot the 2nd time, all of them are clean now. I think at least things are improved a bit, since it was not ok for this simple case previously.
Oh! Can you please try to reboot some more times and check whether you get "Filesystem is NOT clean" once more? If not then I would change the ctrlaltdel-line in grml itself, seems like my grml-reboot script is more reiserfs friendly than Debian. ;-))
regards, -mika-
On Sun, 17 Sep 2006 10:38:05 +0200, Michael Prokop wrote:
Hmm... the change take effect right away, right? Ie, right after I've made the change, the keyboard would then trigger grml-reboot instead of init 6, correct?
No. You have to either run 'telinit q' or reboot at all so init rereads the files /etc/inittab.
thanks, that explains it.
think at least things are improved a bit, since it was not ok for this simple case previously.
Oh! Can you please try to reboot some more times and check whether you get "Filesystem is NOT clean" once more? If not then I would change the ctrlaltdel-line in grml itself, seems like my grml-reboot script is more reiserfs friendly than Debian. ;-))
I feel more confident that it will do. Ok, we've got one clean boot already, let's wait several days to simulate my previous "chaotic" status before I reboot. I'll report afterward.
cheers
On Sun, 17 Sep 2006 10:46:19 +0200, T wrote:
... at least things are improved a bit, since it was not ok for this simple case previously.
Oh! Can you please try to reboot some more times and check whether you get "Filesystem is NOT clean" once more? If not then I would change the ctrlaltdel-line in grml itself, seems like my grml-reboot script is more reiserfs friendly than Debian. ;-))
I feel more confident that it will do. Ok, we've got one clean boot already, let's wait several days to simulate my previous "chaotic" status before I reboot. I'll report afterward.
YES! Filesystem is clean!!!
... after so many days, I reboot again, and yes, Filesystem is clean!
Problem solved, thanks mika
participants (2)
-
Michael Prokop -
T