You are not logged in.
Pages: 1
Hey!
So I'm going to build my first system in a week or so, and I want #! on it
I was thinking, since Karmic was JUST released, it would be really convenient to just put Koala#! on it rather than eventually having to upgrade.
So is there going to be an "official" release of CB based off 9.10 anytime soon, or should I just be content with 9.04 for now?
Thanks for responding.
Unfortunately, the exact same thing happens when I try recovery mode.
I think the problem lies in those two lines about read only. I read somewhere (which I'm not sure if accurate) that ext3 switches to Read Only when there are a lot of write errors. Is this true?
Right now, I'm at the point where I just want it to work. What's the easiest way to backup a Linux partition and then restore it?
EDIT: After doing some work, I think I might have discovered that the card is toast. I tried to go in with a live of Crunchee, and it wouldn't mount. I tried to backup the ext3 with DiskImage, and it failed. I think it has a bad SuperBlock, whatever that is. 
So here's the dealeo. Last week, I installed Cruncheee on an SDHC card, and it worked fine. In the process of installing, I accidentally installed GRUB to my SSD instead of the card, which I preferred. Yesterday, I researched how to remove GRUB, since I kept getting various errors when attempting to boot into Windows straight from the BIOS. I found FIXMBR, removed my SDHC (just in case), and ran it. I rebooted, and Windows worked fine. Then I put the SDHC back in, attempted to boot into !#e (Cruncheee), and it worked. Other than a few problems here and there that I don't want to trouble you with, I had a wonderful dual-boot situation working.
Then today, I grabbed my 901 in a hurry and put my #!e SDHC in and headed off to class. Once there, I attempted to boot up, and got an error. I had accidentally left the card in read only (the little switch on the side), so I shut the computer down (hard reset....it had hung up....) and switched the read only off, put it in, and tried again. Now, every time I attempt to boot, I hang at a initramfs prompt. Here's the entire error:
Boot from (hd0,0) ext3 2f543642-fdc7-4785-88e8-7140e9c283f0
Starting up ...
Loading, please wait ...
19+0 records in
19+0 records out
kinit: name_to_dev_t(/dev/disk/by-uuid/5612049f-642b-4c48-bf9d-89c8d5abfe) = dev(8,37)
kinit: trying to resume from /dev/disk/by-uuid/5612049f-642b-4c48-bf9d-89c8d5abfe
kinit No resume image, doing normal boot...
[ 13.268294] EXT2-fs: INFO: recovery required on readonly filesystem.
[ 13.268373] EXT2-fs: write access unavailable, cannot proceed.
mount: mounting /dev/disk/by_uuid/2f543642-fdc7-4785-88e8-7140e9c283f0 on /root failed: invalid argument
mount: mounting /root/dev on /dev/.static/dev failed: No such file or directory
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /proc on /root/proc failed: No such file or directory
Target filesystem doesn't have /sbin/init.
No init found. Try passing init= bootarg.
(initramfs)_It makes it past the GRUB menu, past the #! loading screen, but then stops. It almost looks like the card is stuck in read only mode. Could it be that data on it got corrupted or something? My other comp's SD reader is sucking, so I'm having trouble seeing if it is toast or not.
Also, I did have to perform quite a few hard resets.....I am a beginner to Linux (hence the thread placement), and I couldn't get how to exit from the initramfs prompt. I tried 'exit', which just made it print back this error:
/init: line 231: cannot open /root/dev/console: no such file
[ 421.192684] Kernel panic - not syncing: Attempted to kill init!
_(Which just stays there indefinitely...)
I've read from one place that when Ubuntu hangs at the initramfs prompt on a dual boot, just boot into Windows, shut down, and try again and it should work. It didn't.
I've also read some things about editing GRUB, but I'm wondering, if it worked yesterday, why should I have to be editing GRUB now? Was it the read only issue that caused the problem? The hard resets? Is there any way to fix it without a fresh #!e installation?
Windows works fine, and up until today, so did #!e. Help! Thanks!
-Pie
Pages: 1
Copyright © 2012 CrunchBang Linux.
Proudly powered by Debian. Hosted by Linode.
Debian is a registered trademark of Software in the Public Interest, Inc.