You are not logged in.
Pages: 1
Hi.. i've just rebooted my arch after 4days.. and it doesn't boot up. I just updated the kernel.. the last one.
At start, it stop at "Checking Filesystem".. [FAIL]
Then he told me that i have to insert the root password and repair manually the filesystem, after remount the root partition as rw. I use xfs filesystem.
There is a command to check the filesystem? I don't know why he doesn't do it automatically..
Please, help me because i had to start win for the first time after 6 month to write this post..
Offline
Sounds like there is a problem with one of the filesystems on your computer. You have to boot with some kind of live/rescue cd and perform a fsck.xfc (for xfs filesystems) procedure on the partition that's causing trouble.
Last edited by fwojciec (2008-02-21 22:38:25)
Offline
Sounds like there is a problem with one of the filesystems on your computer. You have to boot with some kind of live/rescue cd and perform a mkfs.xfs (for xfs filesystems) procedure on the partition that's causing trouble.
won't this delete like all your data?
i guess if you typed in your root password, a simple
fsck.xfs -y
should be enough
if not, see the man page of fsck.xfs for further details
man fsck.xfs
Offline
Thanks for pointing that out -- you are obviously right -- what was I thinking... I edited my previous post.
Offline
I have got the same error, fsck.xfs does not help. I am on testing repository and have update yesterday filesystem to v. 2008.02-2.
Could it be reason that Arch doesn't boot anymore?
edit
I have find this bug
http://bugs.archlinux.org/task/9640
Last edited by mini (2008-02-22 06:38:25)
Offline
I have the same problem and found an solution, when I try to fsck my disk I experience that /dev is nerly empty.
So I check what's going wrong, and in my case it seems that someone has forgotten the /etc/start_udev file so
/dev gets static.
So I set up my network and do a
pacman -S core/udev
and downgrade to 116-3 ... rebooting and tada, boots like there was never any problem
edit: hm should have read the bug report first
Last edited by sargon (2008-02-22 11:13:44)
Offline
Could somebody please post instructions on how to fix this issue for those not familiar with LiveCDs / rescue disks?
Offline
http://wiki.archlinux.org/index.php/Kernel_Panics in the wiki more specific for kernel, hopefully you know how to bring the network up if you don't have a locally stored file.
Not sure enabling testing is correct if unsure how to fix though.
Last edited by FeatherMonkey (2008-02-22 14:05:13)
Offline
So I set up my network and do a
pacman -S core/udevand downgrade to 116-3 ... rebooting and tada, boots like there was never any problem
OK.. now i try to get the core/udev packet..
Offline
sargon wrote:So I set up my network and do a
pacman -S core/udevand downgrade to 116-3 ... rebooting and tada, boots like there was never any problem
OK.. now i try to get the core/udev packet..
after downgrading
if u are still looking for a fix, u need to
pacman -Syy initscripts udev
both packages are in testing. So you will need to enable the testing repository
Last edited by jacko (2008-02-22 17:44:22)
Offline
sargon wrote:So I set up my network and do a
pacman -S core/udevand downgrade to 116-3 ... rebooting and tada, boots like there was never any problem
OK.. now i try to get the core/udev packet..
Way 2 go.. It works
Offline
I have updated my initscripts and udev from testing but this hasn't fixed my problem.
When I boot now, during the process of loading modules and starting services, my screen resolution changes (which I guess is part of the new initscript), and is helpful beacuse it allows me to see more of the problem I'm having...
Anyway, after "Loading udev uevents", I get a message printed saying something about "Bad superblock on /dev/sda3, last edit time in the future. FIXED.", but immediately thereafter, none of my filesystems are mounted properly, and the system hangs on "Starting Hardware Abstraction Layer"
Any ideas?
I have already booted into the Arch installation environment and run an fsck on all my filesystems, they checkout OK.
Edit: False alarm, this has nothing to do with the aforementioned bug. It's because I was playing around in my fstab last night and forgot I had made changes this morning when I turned my PC on. Silly me.
Last edited by Oblong_Cheese (2008-02-23 02:11:25)
Offline
Check the bios setting for time and year.....
Prediction...This year will be a very odd year!
Hard work does not kill people but why risk it: Charlie Mccarthy
A man is not complete until he is married..then..he is finished.
When ALL is lost, what can be found? Even bytes get lonely for a little bit! X-ray confirms Iam spineless!
Offline
Pages: 1