Mailinglist Archive: opensuse-bugs (19862 mails)
| < Previous | Next > |
[Bug 382070] error in service module - read-only file system
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Mon, 5 May 2008 11:18:32 -0600 (MDT)
- Message-id: <20080505171832.A455924538E@xxxxxxxxxxxxxxxxxxxxxx>
https://bugzilla.novell.com/show_bug.cgi?id=382070
User cerebus_8@xxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=382070#c13
Dan Gahlinger <cerebus_8@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|dgahling@xxxxxxxxx |
--- Comment #13 from Dan Gahlinger <cerebus_8@xxxxxxxxx> 2008-05-05 11:18:32
MST ---
Ok, this is bad. opensuse 11.0 beta 2 does EXACTLY the same thing!
This is a show stopper if I ever saw one.
I did the boot with init=/bin/sh
but nothing really out of the ordinary pops up on the file system.
It says fsck is clean, mounting read-only
The only thing that stands out is a statement about
invoking /dev/sda2 manually
and a user retry for the same statement.
I'll see if I can write it down and paste it in here later.
On the "up" side, I reinstalled using Grub/ext3 combo and that works perfectly.
So something about Lilo/reiser is really messing things up.
i'm going to write down those boot lines, then reinstall testing
grub/reiser and lilo/ext3 and see which (or both?) that causes the issue.
We need lilo (for some really weird reasons)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
User cerebus_8@xxxxxxxxx added comment
https://bugzilla.novell.com/show_bug.cgi?id=382070#c13
Dan Gahlinger <cerebus_8@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEEDINFO |NEW
Info Provider|dgahling@xxxxxxxxx |
--- Comment #13 from Dan Gahlinger <cerebus_8@xxxxxxxxx> 2008-05-05 11:18:32
MST ---
Ok, this is bad. opensuse 11.0 beta 2 does EXACTLY the same thing!
This is a show stopper if I ever saw one.
I did the boot with init=/bin/sh
but nothing really out of the ordinary pops up on the file system.
It says fsck is clean, mounting read-only
The only thing that stands out is a statement about
invoking /dev/sda2 manually
and a user retry for the same statement.
I'll see if I can write it down and paste it in here later.
On the "up" side, I reinstalled using Grub/ext3 combo and that works perfectly.
So something about Lilo/reiser is really messing things up.
i'm going to write down those boot lines, then reinstall testing
grub/reiser and lilo/ext3 and see which (or both?) that causes the issue.
We need lilo (for some really weird reasons)
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |