PDA

View Full Version : [SOLVED] 10.04 upgrade probem, won't boot correctly



julz7
May 1st, 2010, 10:56 PM
Hello,
I recently upgraded from Karmic to Lucid using 'cdromupgrade' from the alternate ISO. After upgrading, when I attempted to boot into the system, it output the following:

screen init failed
mount: mounting /dev/disk/by-uuid/aaba7eea-cd6c-44c4-a676-04f1c7fb88ed on /root
failed: Invalid argument
mount: mounting /sys on /root/sys failed: No such file or directory
mount: mounting /dev on /root/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 file system doesn't have /sbin/init
No init found. Try passing init= bootarg


Busybox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built-in shell (ash)
Enter 'help' for a list of built-in commands
(initramfs) _
I tried booting into recovery mode via grub, but it didn't help.
I tried using the other kernels listed in grub, but they gave the same output.

oldfred
May 2nd, 2010, 12:21 AM
Lets see if this tells us what's wrong:

Boot Info Script courtesy of forum member meierfra
Page with instructions and download:
http://bootinfoscript.sourceforge.net/
Be sure to highlight and use code tags (# in edit panel) to make it easier to read when you post the results.txt.

smash4uf
May 2nd, 2010, 06:55 PM
I get the same exact output after trying to boot 10.04, I upgraded from 9.10 via the software update, now forced to use my Vista install for the first time in like a year. Any ideas on whats goin on / how to fix?

JohnDewey
May 2nd, 2010, 07:15 PM
I have exactly the same problem as the original poster. (In my case, I was suspecting it was due to having installed into a RAID1 in the alternate installer.)

AdamGott
May 2nd, 2010, 08:11 PM
Put this one down as a 'me too' issue. I can't boot Ubuntu now and it finishes with an error:

mountall: filesystem could not be mounted

oldfred
May 2nd, 2010, 08:32 PM
I am not sure if new version changed message slightly but this looks somewhat like this errror with possible solutions:
http://sourceforge.net/apps/mediawiki/bootinfoscript/index.php?title=Boot_Problems:search

ahalin
May 3rd, 2010, 05:25 AM
Me too, although I was running 9.04 and just did a normal update through update manager. I did NOT press the "10.04 upgrade is available" button. I thought it was a big update at 280Mb.

Anyway, I come back, rebooted to the grub menu ok, but got fsck errors (exit status 8 ). I ran "e2fsck -y -f -v on my Home and Ubuntu partitions from a Parted Magic live cd. Still no good. My Windows and Home partitions are fine, thankfully.

Then I reinstalled grub and was back to nothing but Windows, no grub menu or anything.

Finally I installed 9.10 on another partition, which is where I picked up that my Ubuntu 9.04 sda5 partition is now called Ubuntu 10.04 LTS. Hmmmmm. I wanted 10.04, but was waiting until it came on a Linux Format disk!

Anyway, I finished the install without formatting Home or touching sda5, rebooted and chose Ubuntu, linux 2.6.28-11-generic (on /dev/sda5 ) from the grub2 menu options. It started with the Ubuntu splash screen and progress bar but then got the flashing "_" and nothing else. The 9.10 install works fine except naturally enough it's missing my personal modifications (OOo3.2 is back to 3.1, no Digikam, no Skype, no Gnome-do, etc).

Checked the UUIDs, they are fine. Updated grub 2 and it "Found Ubuntu 10.04 LTS (10.04) on /dev/sda5"

So I would really like to get back sda 5 and Ubuntu 9.04 or Ubuntu 10.04 LTS or whatever it has become.....

julz7
May 3rd, 2010, 09:34 PM
Lets see if this tells us what's wrong:

Boot Info Script courtesy of forum member meierfra
Page with instructions and download:
http://bootinfoscript.sourceforge.net/
Be sure to highlight and use code tags (# in edit panel) to make it easier to read when you post the results.txt.

Ok. (It took a while to get into a livecd and run it for probably unrelated reasons.)

Boot Info Script 0.55 dated February 15th, 2010

============================= Boot Info Summary: ==============================

=> Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
in partition #1 for /boot/grub/stage2 and /boot/grub/menu.lst.

sda1: __________________________________________________ _______________________

File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


sda2: __________________________________________________ _______________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sda5: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0xcab10bee

Partition Boot Start End Size Id System

/dev/sda1 * 63 485,773,469 485,773,407 83 Linux
/dev/sda2 485,773,470 488,392,064 2,618,595 5 Extended
/dev/sda5 485,773,533 488,392,064 2,618,532 82 Linux swap / Solaris


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 aaba7eea-cd6c-44c4-a676-04f1c7fb88ed ext3 julzhd
/dev/sda5 d890c210-9e94-4ba3-9c18-54d37f20fc6a swap

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

aufs / aufs (rw)
/dev/sr0 /cdrom iso9660 (rw)
/dev/loop0 /rofs squashfs (rw)

=======Devices which don't seem to have a corresponding hard drive==============

sdb sdc sdd sde

oldfred
May 3rd, 2010, 11:30 PM
There is something wrong with sda1 as it show the bad superblock.

I would try this:

From liveCD so everything is unmounted
sudo e2fsck -C0 -p -f -v /dev/sda1
if errors:
sudo e2fsck -f -y -v /dev/sda1

julz7
May 4th, 2010, 03:41 AM
There is something wrong with sda1 as it show the bad superblock.

I would try this:

From liveCD so everything is unmounted
sudo e2fsck -C0 -p -f -v /dev/sda1
if errors:
sudo e2fsck -f -y -v /dev/sda1

Ok. I ran both commands, but there was so much output from the second one that I couldn't copy it all. I ran the commands again (this time putting the output to a text file) and got the following results, respectively:

625882 inodes used (4.12%)
9270 non-contiguous files (1.5%)
698 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 30191/835/0
9067002 blocks used (14.93%)
0 bad blocks
1 large file

492166 regular files
74576 directories
182 character device files
77 block device files
6 fifos
1320 links
58829 symbolic links (46620 fast symbolic links)
37 sockets
--------
627193 files

Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

625882 inodes used (4.12%)
9270 non-contiguous files (1.5%)
698 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 30191/835/0
9067002 blocks used (14.93%)
0 bad blocks
1 large file

492166 regular files
74576 directories
182 character device files
77 block device files
6 fifos
1320 links
58829 symbolic links (46620 fast symbolic links)
37 sockets
--------
627193 files
I tried starting the computer again, but after showing "Starting up...", my monitor says "Input signal out of range". A similar thing happened when I tried to use a 10.04 LiveCD (I had to use a 9.10 one to run the script), except then it showed a purple screen before showing "out of range".

oldfred
May 4th, 2010, 04:31 AM
First try recovery mode. and all its alternatives to update

If not
When the menu comes up press e to edit the menu lines on your boot.

Go the kernel line delete quiet splash and add this:
nomodeset

Control x to boot.

ahalin
May 4th, 2010, 12:49 PM
Thanks for that.

No recovery modes listed for the 10.04, sda5 partition in grub2, but single user mode, memtest and previous kernel are there. They and the "nomodeset" solution suggested above ended with the same problem: Lots of text flashing past then:

init: plymouth main process (754) killed by SEGV signal

a few more lines then

[ 14.443916]EXT3-fs: mounted file system with ordered data mode

and the flashing cursor. I waited a few minutes but nothing happened so ctrl-alt-del to reboot.

tsaowang
May 4th, 2010, 12:52 PM
Hello,

I have had the exact same problem from the day when Lucid Lynx was released.
I have been looking everywhere on the net to find a solution and found this :

http://www.dedoimedo.com/computers/u...nitrd-bug.html (http://www.dedoimedo.com/computers/ubuntu-initrd-bug.html)

I haven't tested yet (at least today), after several installations of Karmic<->Lucid, the only OS that is working for me is Xubuntu 10.04 (don't ask me why, because I should encounter the same issue)

Hope this can help

julz7
May 4th, 2010, 11:08 PM
First try recovery mode. and all its alternatives to update

If not
When the menu comes up press e to edit the menu lines on your boot.

Go the kernel line delete quiet splash and add this:
nomodeset

Control x to boot.

It seems that no matter what I do, including changing the menu lines, it just goes to the initramfs prompt. Once, I was able to get to a command line login screen, but I can't seem to reproduce whatever I did.

tngcritters
May 4th, 2010, 11:26 PM
I too am having boot up problems.

going from hardy to lucid...went smoothly till the "re-boot system"...Nothing. Black screen tnen the message on the screen "no signal". When I installed I removed the old partitions to make it just one boot-up. When the 10.04 didn't work I tried the Studio Ubuntu 10.04 alternate for 64 install. Again worked great, smoothly but took forever like before. And again no booting up. Help!!!

I am using an HP Slimline s7600n AMD 64, that was dual booting windows xp and Ubuntu Hardy. Then later I replaced the xp with Studio (Hardy version). Now I just want one boot up (for now). I have 200 gb hard drive.
Interrogated graphics card, (Nvidia). If it's a no go with my old pc then I will see about getting a new one (later).

Thanks for any help!
Sheila

oldfred
May 5th, 2010, 12:03 AM
On my nvidia it went to sleep (no signal) but by adding nomodeset both on the install and the first boot by manually editing the kernel line it worked in low res mode. I then installed nvidia driver and it worked just fine. the nomodeset also applies to other video cards with issues as a first try at solving issues.

tngcritters
May 5th, 2010, 01:54 AM
On my nvidia it went to sleep (no signal) but by adding nomodeset both on the install and the first boot by manually editing the kernel line it worked in low res mode. I then installed nvidia driver and it worked just fine. the nomodeset also applies to other video cards with issues as a first try at solving issues.


Okay..sounds good, what steps do I take to get to where I can add the nomodeset? I get the first start up screen that has the EnergyStarz logo...then sleepy time!

oldfred
May 5th, 2010, 05:28 AM
tngcritters, I think you are highjacking julz7 thread on booting issues which are totally different than yours. Please start a new thread with your video problem in the title. You will also get more/better help on that issue based on a correct title.

We need to work on julz7 issue although I am running out of suggestions.

If you rerun the boot info script does it show your sda1 partition ok?

julz7
May 7th, 2010, 01:05 AM
tngcritters, I think you are highjacking julz7 thread on booting issues which are totally different than yours. Please start a new thread with your video problem in the title. You will also get more/better help on that issue based on a correct title.

We need to work on julz7 issue although I am running out of suggestions.

If you rerun the boot info script does it show your sda1 partition ok?

Firstly, I noticed when I tried to back up my home directory (which i feel really stupid for not having done in the first place) that if i try to go to my hard drive it gives the following error:

Unable to mount julzhd
Error mounting: mount exited with exit code 32:
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so
when running the command given:

ubuntu@ubuntu:~$ dmesg | tail
[ 133.454776] sd 7:0:0:0: [sdf] 488397168 512-byte logical blocks: (250 GB/232 GiB)
[ 133.456486] sd 7:0:0:0: [sdf] Write Protect is off
[ 133.456493] sd 7:0:0:0: [sdf] Mode Sense: 00 00 00 00
[ 133.456498] sd 7:0:0:0: [sdf] Assuming drive cache: write through
[ 133.458387] sd 7:0:0:0: [sdf] Assuming drive cache: write through
[ 133.458394] sdf: sdf1 < sdf5 >
[ 133.482398] sd 7:0:0:0: [sdf] Assuming drive cache: write through
[ 133.482409] sd 7:0:0:0: [sdf] Attached SCSI disk
[ 161.990062] EXT3-fs error (device sda1): ext3_check_descriptors: Block bitmap for group 11 not in group (block 294912)!
[ 161.990479] EXT3-fs: group descriptors corrupted!

Now, running the script:


Boot Info Script 0.55 dated February 15th, 2010

============================= Boot Info Summary: ==============================

=> Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
in partition #1 for /boot/grub/stage2 and /boot/grub/menu.lst.
=> Windows is installed in the MBR of /dev/sdf

sda1: __________________________________________________ _______________________

File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


sda2: __________________________________________________ _______________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sda5: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

sdf1: __________________________________________________ _______________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sdf5: __________________________________________________ _______________________

File system: ntfs
Boot sector type: Windows XP
Boot sector info: According to the info in the boot sector, sdf5 starts
at sector 63.
Operating System:
Boot files/dirs:

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0xcab10bee

Partition Boot Start End Size Id System

/dev/sda1 * 63 485,773,469 485,773,407 83 Linux
/dev/sda2 485,773,470 488,392,064 2,618,595 5 Extended
/dev/sda5 485,773,533 488,392,064 2,618,532 82 Linux swap / Solaris


Drive: sdf ___________________ __________________________________________________ ___

Disk /dev/sdf: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0x549581cc

Partition Boot Start End Size Id System

/dev/sdf1 16,065 488,392,064 488,376,000 f W95 Ext d (LBA)
/dev/sdf5 16,128 488,392,064 488,375,937 7 HPFS/NTFS


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 aaba7eea-cd6c-44c4-a676-04f1c7fb88ed ext3 julzhd
/dev/sda5 d890c210-9e94-4ba3-9c18-54d37f20fc6a swap
/dev/sdf5 78908F0F908ED354 ntfs New Volume

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

aufs / aufs (rw)
/dev/sr0 /cdrom iso9660 (rw)
/dev/loop0 /rofs squashfs (rw)
/dev/sdf5 /media/New Volume fuseblk (rw,nosuid,nodev,allow_other,default_permissions,b lksize=4096)

=======Devices which don't seem to have a corresponding hard drive==============

sdb sdc sdd sde


Also, if it matters, I tried upgrading soon after the upgrade was first available, but it took too long to download and I cancelled it. I'm not sure if that would impact anything, though.

julz7
May 12th, 2010, 11:07 PM
Anyone?
Also, I noticed that I had an external hard drive connected when I ran the boot info script last time; here it is without the other drive connected:

Boot Info Script 0.55 dated February 15th, 2010

============================= Boot Info Summary: ==============================

=> Grub 0.97 is installed in the MBR of /dev/sda and looks on the same drive
in partition #1 for /boot/grub/stage2 and /boot/grub/menu.lst.

sda1: __________________________________________________ _______________________

File system: ext3
Boot sector type: -
Boot sector info:
Mounting failed:
mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so


sda2: __________________________________________________ _______________________

File system: Extended Partition
Boot sector type: -
Boot sector info:

sda5: __________________________________________________ _______________________

File system: swap
Boot sector type: -
Boot sector info:

=========================== Drive/Partition Info: =============================

Drive: sda ___________________ __________________________________________________ ___

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Disk identifier: 0xcab10bee

Partition Boot Start End Size Id System

/dev/sda1 * 63 485,773,469 485,773,407 83 Linux
/dev/sda2 485,773,470 488,392,064 2,618,595 5 Extended
/dev/sda5 485,773,533 488,392,064 2,618,532 82 Linux swap / Solaris


blkid -c /dev/null: __________________________________________________ __________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 aaba7eea-cd6c-44c4-a676-04f1c7fb88ed ext3 julzhd
/dev/sda5 d890c210-9e94-4ba3-9c18-54d37f20fc6a swap

============================ "mount | grep ^/dev output: ===========================

Device Mount_Point Type Options

aufs / aufs (rw)
/dev/sr0 /cdrom iso9660 (rw)
/dev/loop0 /rofs squashfs (rw)

=======Devices which don't seem to have a corresponding hard drive==============

sdb sdc sdd sde

oldfred
May 12th, 2010, 11:39 PM
Testdisk can supposedly do a lot of things, I would try it next. It is in the repositories you can just download it from synaptic.

repairs including testdisk info & link to testdisk
http://members.iinet.net.au/~herman546/p21.html
download TestDisk http://www.cgsecurity.org/wiki/TestDisk

Instructions
http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step

julz7
May 13th, 2010, 12:28 AM
Testdisk can supposedly do a lot of things, I would try it next. It is in the repositories you can just download it from synaptic.

repairs including testdisk info & link to testdisk
http://members.iinet.net.au/~herman546/p21.html
download TestDisk http://www.cgsecurity.org/wiki/TestDisk

Instructions
http://www.cgsecurity.org/wiki/TestDisk_Step_By_Step

One problem with using this, however, is that I don't know what exactly the problem I'm trying to fix *is*, and so I don't know what to do.

oldfred
May 13th, 2010, 09:28 PM
this is the problem and testdisk I think will also see it:

mount: wrong fs type, bad option, bad superblock on /dev/sda1,
missing codepage or helper program, or other error
In some cases useful info is found in syslog - try
dmesg | tail or so

julz7
May 16th, 2010, 05:14 PM
I ran testdisk, but I still don't know what exactly to do.
You say it's supposed to 'see [the problem]'. It doesn't really seem to be doing anything, probably because I myself don't know what exactly to do with it.
I went through the first few steps as shown in the how to; created a log, selected my hard drive, selected the auto-detected "Intel" option, and used "Analyse", then used "Quick Search". Here's what was in the log:



Sun May 16 15:59:51 2010
Command line: TestDisk

TestDisk 6.11.3, Data Recovery Utility, May 2009
Christophe GRENIER <grenier@cgsecurity.org>
http://www.cgsecurity.org
OS: Linux, kernel 2.6.31-14-generic (#48-Ubuntu SMP Fri Oct 16 14:04:26 UTC 2009)
Compiler: GCC 4.3 - May 6 2009 14:40:08
ext2fs lib: 1.41.4, ntfs lib: 10:0:0, reiserfs lib: 0.3.1-rc8, ewf lib: 20080501
/dev/sda: LBA, LBA48, DCO support
/dev/sda: size 488397168 sectors
/dev/sda: user_max 488397168 sectors
/dev/sda: dco 488397168 sectors
Warning: can't get size for Disk /dev/mapper/control - 0 B - CHS 1 1 1, sector size=512
/dev/sr0 is not an ATA disk
Hard disk list
Disk /dev/sda - 250 GB / 232 GiB - CHS 30401 255 63, sector size=512 - ATA ST3250824AS
Disk /dev/sr0 - 723 MB / 690 MiB - CHS 353280 1 1 (RO), sector size=2048 - TSSTcorp CD/DVDW TS-H652L

Partition table type (auto): Intel
/dev/sda: Device Configuration Overlay (DCO) present.
Disk /dev/sda - 250 GB / 232 GiB - ATA ST3250824AS
Partition table type: Intel

Analyse Disk /dev/sda - 250 GB / 232 GiB - CHS 30401 255 63
Geometry from i386 MBR: head=255 sector=63
get_geometry_from_list_part_aux head=255 nbr=6
get_geometry_from_list_part_aux head=8 nbr=1
get_geometry_from_list_part_aux head=16 nbr=1
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=6
Current partition structure:
1 * Linux 0 1 1 30237 254 63 485773407 [julzhd]
2 E extended 30238 0 1 30400 254 63 2618595
5 L Linux Swap 30238 1 1 30400 254 63 2618532
Ask the user for vista mode
Computes LBA from CHS for Disk /dev/sda - 250 GB / 232 GiB - CHS 30402 255 63
Allow partial last cylinder : Yes
search_vista_part: 1

search_part()
Disk /dev/sda - 250 GB / 232 GiB - CHS 30402 255 63

recover_EXT2: s_block_group_nr=0/1853, s_mnt_count=7/25, s_blocks_per_group=32768, s_inodes_per_group=8192
recover_EXT2: s_blocksize=4096
recover_EXT2: s_blocks_count 60721675
recover_EXT2: part_size 485773400
Linux 0 1 1 30237 254 56 485773400 [julzhd]
EXT3 Large file Sparse superblock Recover, 248 GB / 231 GiB
Linux Swap 30238 1 1 30400 254 43 2618512
SWAP2 version 1, 1340 MB / 1278 MiB
get_geometry_from_list_part_aux head=255 nbr=4
get_geometry_from_list_part_aux head=8 nbr=1
get_geometry_from_list_part_aux head=16 nbr=1
get_geometry_from_list_part_aux head=32 nbr=1
get_geometry_from_list_part_aux head=64 nbr=1
get_geometry_from_list_part_aux head=128 nbr=1
get_geometry_from_list_part_aux head=240 nbr=1
get_geometry_from_list_part_aux head=255 nbr=4

Results
* Linux 0 1 1 30237 254 63 485773407 [julzhd]
EXT3 Large file Sparse superblock Recover, 248 GB / 231 GiB
L Linux Swap 30238 1 1 30400 254 63 2618532
SWAP2 version 1, 1340 MB / 1278 MiB

interface_write()
1 * Linux 0 1 1 30237 254 63 485773407 [julzhd]
2 E extended LBA 30238 0 1 30400 254 63 2618595
5 L Linux Swap 30238 1 1 30400 254 63 2618532
simulate write!

write_mbr_i386: starting...
write_all_log_i386: starting...
write_all_log_i386: CHS: 30238/0/1,lba=485773470

TestDisk exited normally.
It also has other options on the menu, namely [Advanced], [Geometry], [Options], [MBR Code], and [Delete]. Should I try going through one of those, and if so which one if any would help?

oldfred
May 16th, 2010, 06:30 PM
These links have further info. They seem to be two ways to solve the problem.

http://linuxexpresso.wordpress.com/2010/03/31/repair-a-broken-ext4-superblock-in-ubuntu/
http://www.cgsecurity.org/wiki/Advanced_NTFS_Boot_and_MFT_Repair

julz7
May 16th, 2010, 09:34 PM
Tried the first one.

ubuntu@ubuntu:~$ sudo fdisk -l

Disk /dev/sda: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xcab10bee

Device Boot Start End Blocks Id System
/dev/sda1 * 1 30238 242886703+ 83 Linux
/dev/sda2 30239 30401 1309297+ 5 Extended
/dev/sda5 30239 30401 1309266 82 Linux swap / Solaris
ubuntu@ubuntu:~$ sudo fsck.ext3 -v /dev/sda
e2fsck 1.41.9 (22-Aug-2009)
fsck.ext3: Device or resource busy while trying to open /dev/sda
Filesystem mounted or opened exclusively by another program?
ubuntu@ubuntu:~$ sudo fsck.ext3 -v /dev/sda1
e2fsck 1.41.9 (22-Aug-2009)
fsck.ext3: Group descriptors look bad... trying backup blocks...
Superblock needs_recovery flag is clear, but journal has data.
Recovery flag not set in backup superblock, so running journal anyway.
julzhd: recovering journal
Truncating orphaned inode 8856009 (uid=0, gid=0, mode=0100644, size=36)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Free blocks count wrong for group #0 (31223, counted=7168).
Fix<y>?


(I realize that I might not have wanted to stray from the guide and change '/dev/sda' to '/dev/sda1', but it ended up working.)
At that point I canceled it and was able to mount my hard drive with no errors. I copied my home directory to an external drive. I then rebooted and got an "Input signal out of range" error on my monitor, same as when I try using a 10.04 LiveCD.
Booting into the 2.6.31-21 kernel gets

chroot: cannot execute /etc/apparmor/initramfs: No such file or directory
I then went back to the LiveCD and unmounted the hard drive before running the second command, but nothing changed.
Editing the boot options (removing "splash quiet" and adding "nomodeset") gives a command line with a bunch of quickly-scrolling output and:

julzhd contains a file system with errors, check forced.
Going back and running "sudo fsck.ext3 -v /dev/sda1", I keep getting the following output, then pressing y, then getting the same output again with different numbers:

Free blocks count wrong for group #X (32254, counted=Y).
Fix<y>?
where X and Y keep changing each time. Should I keep going through with this thirty thousand times or try something else?
EDIT: After holding down the Y key, I get:

Free blocks count wrong (58459862, counted = 52043382).
then:

Directories count wrong for group #X (Y, counted=Z).
Fix<y>? yes
Free inodes count wrong for group #X (Y, counted=Z).
Fix<y>?
EDIT2: Now I get to this:

Free inodes count wrong (15187957, counted=14562097).
Fix<y>? yes


julzhd: ***** FILE SYSTEM WAS MODIFIED *****

625871 inodes used (4.12%)
9269 non-contiguous files (1.5%)
698 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 30182/829/0
8678293 blocks used (14.29%)
0 bad blocks
1 large file

492161 regular files
74578 directories
182 character device files
77 block device files
6 fifos
1320 links
58829 symbolic links (46620 fast symbolic links)
29 sockets
--------
627182 files
ubuntu@ubuntu:~$
EDIT4: My computer now boots normally after using the nomodeset option.
EDIT5: Still have some problems. The graphics card driver apparently isn't working (wrong resolution, Compiz isn't working, nVidia settings says "You do not appear to be using the NVIDIA X driver. Please edit your X configuration file (just run `nvidia-xconfig` as root), and restart the X server." (which gives a "command not found" error, by the way).) Also, there isn't any sound.
EDIT6: Trying to install the nVidia driver under "Hardware Drivers" gives the following error:

SystemError: Failed to lock /var/cache/apt/archives/lock

oldfred
May 17th, 2010, 12:57 AM
I was just able to install the nvidia driver without issue and then everything just worked. So you are now beyond what I have seen. Someone else may have better answers.

You may want to start a new thread on the video issue as those who have seen something may then look at that thread. Good titles are important to get someone with knowledge to look.

julz7
May 21st, 2010, 09:37 PM
I was able to fix all three of the problems (the respective solutions were: apparently aptitude was already running; just needed to install the graphics driver; the "mute" option was checked under sound settings for some reason). Then, though, the Update Manager gives the following message:

Not all updates can be installed
Run a partial upgrade, to install as many updates as possible.
This can be caused by:
* A previous upgrade which didn't complete
* Problems with some of the installed software
* Unofficial software packages not provided by Ubuntu
* Normal changes of a pre-release version of Ubuntu
with options "Partial Upgrade" and "Close". There are also quite a few updates listed that are unchecked and greyed out.
I ran a partial upgrade. Everything seems fine now except for the tiny little problem that I can't connect to the Internet. It recognizes my wifi network and is connected to it, but I can't actually access anything; everything I try gives a "Server not found" or "Bad hostname" or "Unable to resolve address" error. I also tried FTP and SSH; they don't work. I can't access 192.168.1.1, though 127.0.0.1 works.
(Also if it matters I left Pidgin and Skype open during the partial upgrade.)
I think I'll go ahead and start a new thread for this problem, then.

yielder
November 12th, 2011, 03:46 PM
There is something wrong with sda1 as it show the bad superblock.

I would try this:

From liveCD so everything is unmounted
sudo e2fsck -C0 -p -f -v /dev/sda1
if errors:
sudo e2fsck -f -y -v /dev/sda1

Mine wasn't an upgrade problem but the problem was the same.

My first cut at solving the problem was to download the version of Ubuntu that I'm running. I'm running Windows7 in a partition so that wasn't a problem. I then burned the download to a DVD and rebooted so that the DVD drive loaded first. That got me to a trial version of Ubuntu. I could see my Ubuntu partition but could get it to mount. I grabbed the screen and saved it by emailing it to myself.

Then lots more googling led me to this thread and your suggestion. It didn't work initially. Then I looked at my screengrab again and saw that it said that the problem was in sda6. I changed sda1 in your suggestion to sda6 and that did it. Everything is as it was before. I thought I'd share this with folks just in case it helps another poor soul like me.

Thanks for your sharing.

Regards,
Mike