Update after fresh install

Nibodhika · 2012-07-09 22:37:12

So, my funtoo system broke, and I realized I've had it for quite long and so I decided to reformat my / and start from scratch. I installed the current stage3 and everything went perfectly, until I rebooted my system after the first upgrade. Then I got :

(none) login:

And it didn't accepted root as a valid login (I don't know which log is adequate for this). So I went back to my LiveCD and tried to do a depclean, which resulted in nothing. Then I decided to try with a freshly installed funtoo, and was able to boot, I performed a emerge -uND world and after the reboot same thing.
Then I decided to try a emerge -e world in a fresh installation to avoid incompatibility problems, but just this was enought to give me the same error.
A friend sugested that the first boot could be corrupting some file, so I tried to boot and reboot into the fresh system, but it booted just fine, until the emerge -uND world.

Last time I tried (and current state of the machine) was a fresh install, and a emerge -uND world, when rebooted the / was mounted read-only, so even though the login screen was the same this time I managed to login. I'm now in a liveCD on this machine.

The strangest thing is that I'm not even trying to install something new that could be breaking the system, I'm performing an upgrade on the stage3.

My guess is that this has something to do with the system mounting the root as read-only, However I don't understand why the root is not being mounted as read-write.

Some info:
I tryed this with the stage3-current and stage3-stable for the intel i7 family (mine is a intel i5). In my make.conf I'm using ~amd64 keyword as default

rh1 · 2012-07-10 00:00:16

Going to need a little more info such as where exactly it's failing during boot, as in what services start and what fails before you get the login prompt. Error messages, ect.. would also be a help. Take a picture if you have to.

Nibodhika · 2012-07-10 15:41:57

I'm not shure of which log post here, but here's /var/log/dmesg
http://pastebin.com/tkBRyhrz

(my filesystem is /dev/sda1 ext2 for /boot /dev/sda2 ext4 for / and /dev/sda4 ext4 for /home)

There is no other log because the root is mounted read-only, and that prevents the generation of startup logs... but most of the other errors seem related to the fact that the root was mounted read-only, things like could not create this or that file.

PS: I've managed to log into a usable system by loging and then remounting the root with rw option, also tried to force that option in /etc/fstab, but was not sucessful...
The strangest thing is that in dmesg appears this:

[    5.361944] EXT4-fs (sda2): mounted filesystem with ordered data mode. Opts: (null)
[    5.493007] EXT4-fs (sda3): mounted filesystem with ordered data mode. Opts: (null)
[    5.617194] EXT4-fs (sda4): mounted filesystem with ordered data mode. Opts: (null)

and my fstab is

/dev/sda1               /boot           ext2            noauto,noatime  1 2
/dev/sda2               /               ext4            noatime         0 1
/dev/sda4               /home           ext4            noatime         1 3
/dev/cdrom              /mnt/cdrom      auto            noauto,ro       0 0

Last edited by Nibodhika (2012-07-10 15:42:36)

rh1 · 2012-07-10 21:09:55

Whats the first thing that fails? Thats most likely where the problem is. If needed, You can edit /etc/rc.conf and set interactive to yes. This will allow you to hit 'I' during boot to pause rc and allow you to start services one at a time. Root should be mounted read only untill fsck and then remounted rw. Also newest open rc requires /run dir which should have been created by new baselayout but You should verify it exists.

Nibodhika · 2012-07-11 18:03:18

A friend of mine managed to solve this, altough we are not shure why. Things that were made different this time:
- Support to extended and debugging options in the kernel for ext4 filesystem were disabled (this could be the cause, since after updating the system the files were changed and then the system stopped recognized them)
- Support to ext2 was enabled as default instead of using the ext2/ext3 support for the ext4 driver (This could have lead to the /boot not being read correctly and failing to load something)
- Partition table was deleted, remade and reformated (A problem with the filesystem not detected by badblocks or fsck could have been the cause)

So this is solved, even if I have no idea of which of this things solved the problem

Thanks

#1 2012-07-09 22:37:12

Update after fresh install

#2 2012-07-10 00:00:16

Re: Update after fresh install

#3 2012-07-10 15:41:57

Re: Update after fresh install

#4 2012-07-10 21:09:55

Re: Update after fresh install

#5 2012-07-11 18:03:18

Re: Update after fresh install

Board footer