[opensuse] Can't boot 10.3 after 11.0 install
Hello SuSE people, During the boot up process it fails and dumps me into maintenance mode. It says "FSCK failed for at least one filesystem. (not /)Then to do it manually and reboot. I shutdown and then did an fsck on the entire filesystem. (All three drives) Didn't help. Now the funny thing is that 10.2 and the new 11.0 boot OK and every fstab is exactly the same. They all mount the exact same partitions, yet 10.3 fails where the other two do not. Here are two other strange messages which might help in analyzing this problem. "Superblock last write time is in the future. FIXED" What causes that? "BLOGD: no message logging because /var file system is not accessible" Don't know if that could be the problem. Help please! I've spent the last three days trying to fix this. 10.3 is my "work" system. I need it back. The install of 11.0 should have been easy. It wasn't. Can't imagine what could have happened. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 02 September 2008 01:22:50 Bob S wrote:
Hello SuSE people,
Hate to beg, Hate even more to reply to my own messages.Someone must have some thoughts on this.
During the boot up process it fails and dumps me into maintenance mode. It says "FSCK failed for at least one filesystem. (not /)Then to do it manually and reboot.
I shutdown and then did an fsck on the entire filesystem. (All three drives) Didn't help. Now the funny thing is that 10.2 and the new 11.0 boot OK and every fstab is exactly the same. They all mount the exact same partitions, yet 10.3 fails where the other two do not.
Here are two other strange messages which might help in analyzing this problem.
"Superblock last write time is in the future. FIXED" What causes that?
"BLOGD: no message logging because /var file system is not accessible" Don't know if that could be the problem.
Help please! I've spent the last three days trying to fix this. 10.3 is my "work" system. I need it back. The install of 11.0 should have been easy. It wasn't. Can't imagine what could have happened.
Bob S
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Bob S <911@sanctum.com> [09-02-08 17:46]:
During the boot up process it fails and dumps me into maintenance mode. It says "FSCK failed for at least one filesystem. (not /)Then to do it manually and reboot.
I shutdown and then did an fsck on the entire filesystem. (All three drives) Didn't help. Now the funny thing is that 10.2 and the new 11.0 boot OK and every fstab is exactly the same.
you don't reall mean this? all three fstabs are the same? They cannot be, addressing three different systems!
They all mount the exact same partitions, yet 10.3 fails where the other two do not.
Here are two other strange messages which might help in analyzing this problem.
"Superblock last write time is in the future. FIXED" What causes that?
probably the last system that wrote to the disk has a different clock time than the system causing the error message
"BLOGD: no message logging because /var file system is not accessible" Don't know if that could be the problem.
/var is out of space or otherwise fsck'ed
Help please! I've spent the last three days trying to fix this. 10.3 is my "work" system. I need it back. The install of 11.0 should have been easy. It wasn't. Can't imagine what could have happened.
I would boot from a live disk and fsck the drive partition that contains 10.3's /var THEN remove some of the older log files and clean /var/tmp if you have one. -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 3 Sep 2008 07:55:36 Patrick Shanahan wrote:
* Bob S <911@sanctum.com> [09-02-08 17:46]:
[...]
"BLOGD: no message logging because /var file system is not accessible" Don't know if that could be the problem.
/var is out of space or otherwise fsck'ed
Help please! I've spent the last three days trying to fix this. 10.3 is my "work" system. I need it back. The install of 11.0 should have been easy. It wasn't. Can't imagine what could have happened.
I would boot from a live disk and fsck the drive partition that contains 10.3's /var
THEN remove some of the older log files and clean /var/tmp if you have one.
Another possibility is that if you are trying to share /var between 11.1 and 10.3 that the owner and group id's don't match across the 2 systems. You need to check /etc/passwd and /etc/group on each system to find out. A better idea would be not to share any partitions other than (perhaps) /home; even if you do share /home. make sure that you have separate user accounts between 10.3 and 11 to avoid problems with config files. -- =================================================== Rodney Baker VK5ZTV rodney.baker@iinet.net.au =================================================== The trouble with a kitten is that When it grows up, it's always a cat -- Ogden Nash.
On Tuesday 02 September 2008 18:55:21 Rodney Baker wrote:
On Wed, 3 Sep 2008 07:55:36 Patrick Shanahan wrote:
* Bob S <911@sanctum.com> [09-02-08 17:46]:
[...]
"BLOGD: no message logging because /var file system is not accessible" Don't know if that could be the problem.
/var is out of space or otherwise fsck'ed
Help please! I've spent the last three days trying to fix this. 10.3 is my "work" system. I need it back. The install of 11.0 should have been easy. It wasn't. Can't imagine what could have happened.
I would boot from a live disk and fsck the drive partition that contains 10.3's /var
THEN remove some of the older log files and clean /var/tmp if you have one.
Another possibility is that if you are trying to share /var between 11.1 and 10.3 that the owner and group id's don't match across the 2 systems. You need to check /etc/passwd and /etc/group on each system to find out. A better idea would be not to share any partitions other than (perhaps) /home; even if you do share /home. make sure that you have separate user accounts between 10.3 and 11 to avoid problems with config files.
Hi Rodney, No, I'm not trying to share it. Each system has it's own separate /var partition. Will check /etc/passwd and /etc/group though. Thanks again.Will report back. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 02 September 2008 18:25:36 Patrick Shanahan wrote:
* Bob S <911@sanctum.com> [09-02-08 17:46]:
During the boot up process it fails and dumps me into maintenance mode. It says "FSCK failed for at least one filesystem. (not /)Then to do it manually and reboot.
I shutdown and then did an fsck on the entire filesystem. (All three drives) Didn't help. Now the funny thing is that 10.2 and the new 11.0 boot OK and every fstab is exactly the same.
you don't reall mean this? all three fstabs are the same? They cannot be, addressing three different systems!
Hi Patrick, Thanks for replying. Yes, I do. That way I could access any file on any system. Worked just fine on 10.2 and 10.3. If I can't cure it I will try modifying the fstab files.
They all mount the exact same partitions, yet 10.3 fails where the other two do not.
Here are two other strange messages which might help in analyzing this problem.
"Superblock last write time is in the future. FIXED" What causes that?
probably the last system that wrote to the disk has a different clock time than the system causing the error message
"BLOGD: no message logging because /var file system is not accessible" Don't know if that could be the problem.
/var is out of space or otherwise fsck'ed
Help please! I've spent the last three days trying to fix this. 10.3 is my "work" system. I need it back. The install of 11.0 should have been easy. It wasn't. Can't imagine what could have happened.
I would boot from a live disk and fsck the drive partition that contains 10.3's /var
Already fsck'd it about 100 times :-) I'll see what is in it.
THEN remove some of the older log files and clean /var/tmp if you have one.
Will try it. Thanks Patrick Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Bob S <911@sanctum.com> [01-01-70 11:34]:
On Tuesday 02 September 2008 18:25:36 Patrick Shanahan wrote:
* Bob S <911@sanctum.com> [09-02-08 17:46]:
During the boot up process it fails and dumps me into maintenance mode. It says "FSCK failed for at least one filesystem. (not /)Then to do it manually and reboot.
I shutdown and then did an fsck on the entire filesystem. (All three drives) Didn't help. Now the funny thing is that 10.2 and the new 11.0 boot OK and every fstab is exactly the same.
you don't reall mean this? all three fstabs are the same? They cannot be, addressing three different systems!
Hi Patrick, Thanks for replying.
Yes, I do. That way I could access any file on any system. Worked just fine on 10.2 and 10.3. If I can't cure it I will try modifying the fstab files.
More explanation is necessary. You cannot have all three systems using the same root and the same /var, and .... And you said that you did not share /var.... Thus the three fstabs *must* be different. Please explain -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 02 September 2008 21:56:34 Patrick Shanahan wrote:
* Bob S <911@sanctum.com> [01-01-70 11:34]:
On Tuesday 02 September 2008 18:25:36 Patrick Shanahan wrote:
* Bob S <911@sanctum.com> [09-02-08 17:46]:
During the boot up process it fails and dumps me into maintenance mode. It says "FSCK failed for at least one filesystem. (not /)Then to do it manually and reboot.
I shutdown and then did an fsck on the entire filesystem. (All three drives) Didn't help. Now the funny thing is that 10.2 and the new 11.0 boot OK and every fstab is exactly the same.
you don't reall mean this? all three fstabs are the same? They cannot be, addressing three different systems!
Hi Patrick, Thanks for replying.
Yes, I do. That way I could access any file on any system. Worked just fine on 10.2 and 10.3. If I can't cure it I will try modifying the fstab files.
More explanation is necessary. You cannot have all three systems using the same root and the same /var, and .... And you said that you did not share /var....
Thus the three fstabs *must* be different. Please explain
Hi Patrick, No, they are all the same. Every mountable partition is mounted in each OS. Of course they are named differently. e.g. I always make separate partitions for /home /var and /tmp. When the partitioner asks for a mount point you cannot use the same one as another existing one. So instead of / I call it /11.0 and instead of /var I call it /var11.0 etc. etc. So, when I boot 10.2 (or 11.0) all of the mounted partitions, including the other os's will show up in the file tree, including /11.0, /10.2 /10.3 /home11.0, /home10.2 /home 10.3 /var11.0, /var10.2 /var10.3 etc etc. Thusly, all the fstab's will be the same. This worked fine for 10.2 and 10.3 installed side by side. Whatever os was booted seemed to find it's own partitions to work with and ignored the others.Same as /workspace, /datastorage, and /backup which are on the first disk and can be accessed from the other two os's and disks.Can't tell you why or how this works. But it did with 10.2 and 10.3, and now it works with 10.2 and 11.0. Am I violating some rule here? If I am and this is not supposed to work please let me know. Do you run more than one version of openSUSE? If so, how do you handle duplicate file names within the different versions that the installer allows. Another thing, is it possible to paginate the boot screen? I seem to remember way back in the Win3.11 days you could add a -p or something like that to get a screenfulj at a time.If I could do that I might be able to see where the trouble is. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* Bob S <911@sanctum.com> [09-03-08 21:16]:
Am I violating some rule here? If I am and this is not supposed to work please let me know.
??
Do you run more than one version of openSUSE?
no, no need that I can see. But I run several servers and seldom reboot.
If so, how do you handle duplicate file names within the different versions that the installer allows.
Another thing, is it possible to paginate the boot screen?
look at /var/log/boot.*
I seem to remember way back in the Win3.11 days you could add a -p or something like that to get a screenfulj at a time.If I could do that I might be able to see where the trouble is.
gud luk, -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 03 September 2008 22:02:32 Patrick Shanahan wrote:
* Bob S <911@sanctum.com> [09-03-08 21:16]:
Am I violating some rule here? If I am and this is not supposed to work please let me know.
??
Do you run more than one version of openSUSE?
no, no need that I can see. But I run several servers and seldom reboot.
If so, how do you handle duplicate file names within the different versions that the installer allows.
Another thing, is it possible to paginate the boot screen?
look at /var/log/boot.*
Problem is, if you remember in my first post. when the boot process errored out it said it couldn't log to /var
I seem to remember way back in the Win3.11 days you could add a -p or something like that to get a screenfulj at a time.If I could do that I might be able to see where the trouble is.
gud luk, --
Yeah, well, thanks for trying. Still have no idea. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Tuesday 02 September 2008 18:25:36 Patrick Shanahan wrote: ................<snipped a whole bunch>..............
I would boot from a live disk and fsck the drive partition that contains 10.3's /var
THEN remove some of the older log files and clean /var/tmp if you have one.
OK Patrick. Here is what I did. Dropped down and booted from the disk to the rescue system. I (again) fsck'd every partition on every disk. All clean. Then I went to the 10.3 fstab and commented out everything except the four partitions for 10.3. That would leave only /10.3, 10.3home. 10.3var, and 10.3tmp. Then I went to 10.3tmp, and 10.3var and cleaned out everything that I thought would help in /10.3var,10.3/var/tmp, and /10.3tmp. Now! these are 10GB dedicated partitions, mind you. They couldn't possibly be full, and, it worked beautifully before I installed 11.0, and 11.0 was installed on a different hard drive. This is crazy! Still getting the LOGD message that it can't log to /var because it is inaccessible. There is one other failure message that I didn't mention before. It is"Failed /10.3/etc/kbd (line 42 locale) So I went there and it says "LOCALE_CHARMAP=lcale charmap". I don't think that has anything to do with this. I also checked out the /etc/group and /etc/passwd for all of the three systems as suggested by Rodney Baker. Didn't see anything remiss there either. I am not sharing the /var partitions.All separate. Soooo...Now what? Any other ideas? That's all I want.ideas and clues. Bob S -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (3)
-
Bob S -
Patrick Shanahan -
Rodney Baker