I installed opensuse milestone 7 and don’t starts beacause when initialize, the system not mount any patitions with returns read only.
My filesystem is ext4
My grub is correctly, and fstab too.
I’ve had the same thing happen on one of my systems too. Unfortunately I can’t get boot and when I do a recover there are no logs because… the FS is read only. I’ve installed 4 times now, the last one I switched from EXT4 to EXT3 and the exact same thing. Pretty sucky
Is this happening every time you start M7, or just occasionally? I have a similar problem, but it happens every other time I start M7. Fsck fails to fix errors and the file system is mounted read-only. Other times, the system fails to unmount when shutting down. I can’t trace the source of this. Are you by any chance running 11.2 on VirtualBox?
First thing is to boot into your BIOS and check the date/time is
correct, then if you boot the system and in the GRUB options add;
init=/bin/sh
This should automatically run fsck on the affected root drive and will
put you at a root prompt. If it doesn’t automatically run, then for
example (replace the example with your drive partition) run;
fsck /dev/sda2
Now reboot and should now boot without errors.
Once you system has booted, ensure the date/time is correct, you may
wish to setup ntp at this point and ensure the time is correct.
> Hi
> This is what worked for me to fix the issue on an ASUS netbook and a
> vmware machine;
> <http://forums.opensuse.org/pre-release-beta/421916-m7-asus-laptops-a7k-esp.html>
>
> First thing is to boot into your BIOS and check the date/time is
> correct, then if you boot the system and in the GRUB options add;
>
> init=/bin/sh
>
This should automatically run fsck on the affected root drive and will
put you at a root prompt. If it doesn’t automatically run, then for
example (replace the example with your drive partition) run;
> fsck /dev/sda2
>
Now reboot and should now boot without errors.
Once you system has booted, ensure the date/time is correct, you may
wish to setup ntp at this point and ensure the time is correct.
Now su to root user and;
> /sbin/mkinitrd
>
> Shutdown/reboot and all should be ok now
>
> Note, my systems are set to localtime.
I too have the problem - it is caused by the last write and/or the
last mount in the future. When it happens, I boot with “init=/bin/sh”
in the GRUB option line, do the ‘fsck /dev/sdaX’, and then reboot.
> Hi
> This is what worked for me to fix the issue on an ASUS netbook and a
> vmware machine;
> <http://forums.opensuse.org/pre-release-beta/421916-m7-asus-laptops-a7k-esp.html>
>
> First thing is to boot into your BIOS and check the date/time is
> correct, then if you boot the system and in the GRUB options add;
>
> init=/bin/sh
>
This should automatically run fsck on the affected root drive and will
put you at a root prompt. If it doesn’t automatically run, then for
example (replace the example with your drive partition) run;
> fsck /dev/sda2
>
Now reboot and should now boot without errors.
Once you system has booted, ensure the date/time is correct, you may
wish to setup ntp at this point and ensure the time is correct.
Now su to root user and;
> /sbin/mkinitrd
>
> Shutdown/reboot and all should be ok now
>
> Note, my systems are set to localtime.
I too have the problem - it is caused by the last write and/or the
last mount in the future. When it happens, I boot with “init=/bin/sh”
in the GRUB option line, do the ‘fsck /dev/sdaX’, and then reboot.
I too use localtime.
[/QUOTE]
Hi Larry
Can you try the mkinitrd command and see if it fixes it?
I’ve tried installing the 32-bit version on a Pentium 4 based machine, the 64-bit version on an AMD Phenom X4 based system, with similar results. Neither system appears to be having CMOS/battery/clock/etc., problems, and in fact the AMD based machine is quite new. I am using LVM on a SATA drive on both. I didn’t manually request install of anything, such as an NTP client or some such that would establish an external time reference, so there should be no reason the time would jump around. I had no such problem with M6 on the same machines.
When I try the repair mode, it claims it can’t find a valid swap partition. It also claims that the kernel is missing some modules for initrd. Even after that partial repair, it still fails to fully install on either machine. I can use rescue mode to fsck the root LV, but the problem happens again.
It’s as though a proper timestamp is not being committed to the volume before being shutdown, even though I follow the long-standing superstition of Unix-like systems and manually “sync” three times before shutdown. I’m tempted to try to find the right spot in the K* scripts and add an “hwclock” command and some “sync” commands.
It’s also as though the repair mode is inconsistent with the running system, although that’s not the first time I’ve seen that issue. That appears to be true even in the 11.1 GA.
I too am using localtime.
I note that there is a ticket on possible LVM problems in earlier Milestones and a more recent suspicion expressed in the ticket that there might remain some related problem.
http://bugzilla.novell.com/show_bug.cgi?id=505670
Don’t know it the current probs are related, but it caught my eye because I’m using LVM and I believe I’ve seen some of the dev mapper complaints during one of the stages of install of M7.
After much effort, haven’t gotten a smoothly functioning, fully installed M7 on either machine, 32 or 64 bit.
