10.04 upgrade will not boot "invalid argument" error

[olddave1]

Hi,

I did the online upgrade from 9.10 to 10.04, using 64 bit. I was forced to as the 2 solutions to my incedibly slow internet lookups both required new package installs, both of which failed, so hoped it was sorted out in 10.04 TLS.

It all went to plan until it tried to reboot. I get this:

mount: mounting /dev/disk/by-uuid/1e4e276c-8741-42e7-b52e-05c195790d28 on /root failed: invalid argument
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 filesystem doesn't have /sbin/init.
No init found. Try passing init= bootarg.

I don't have RAID at all a single Samsung 200GB SATA drive as the boot drive. Can someone tell me where to start looking? Also how can a TLS release screw up so badly on a common Gigabyte motherboard?

Thx.

David

[Tummycd28]

same problem, mine is fresh install

[olddave1]

Did some googling and after running e2fsck -p /dev/sda1 found it could not find the superblock. So tried this from 10.04 LiveCD
>sudo dumpe2fs /dev/sda1 |grep superblock

I got

dumpe2fs: No such file or directory while trying to open /dev/sda1
Couldn't find valid filesystem superblock.

Seems the 10.04 upgrade has trashed my boot stuff, way to go....

Any way out of this now?

Thx.

David

[olddave1]

Here is the output from sudo fdisk -l -u /dev/sda1

Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders, total 390721968 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x000c492c

Device Boot Start End Blocks Id System
/dev/sda1 * 63 374796449 187398193+ 83 Linux
/dev/sda2 374796450 390716864 7960207+ 5 Extended
/dev/sda5 374796513 390716864 7960176 82 Linux swap / Solaris

Is there a utility I can use that will show me the superblocks like dumpe2fs should be doing? Anything else I can do? Anyone?

[olddave1]

Might be getting somewhere. 10.04 upgrade is its wisdom seems to have thought that because I have 2 identical 200GB SATA drives they are in a RAID config, judging by the outcome of blkid

/dev/loop0: TYPE="squashfs"
/dev/sda: TYPE="isw_raid_member"
/dev/sdb: TYPE="isw_raid_member"
/dev/sdc1: LABEL="W2003Server" UUID="ae98cd9a-653d-4f42-8479-b78ea1ab6362" SEC_TYPE="ext2" TYPE="ext3"
/dev/sdc2: LABEL="TestSpace" UUID="126fdbbd-ba7a-4379-b0ec-4aa262c21d5e" TYPE="ext4"
/dev/mapper/isw_cgghdebhfi_Dev21: UUID="1e4e276c-8741-42e7-b52e-05c195790d28" TYPE="ext3"
/dev/mapper/isw_cgghdebhfi_Dev22: UUID="atNi17-RF09-GjJO-xKh1-tkIV-U746-9jzeGx" TYPE="LVM2_member"
/dev/sdd1: UUID="A663-94F1" TYPE="vfat"

/dev/sda1 is my boot drive and still shows as such in fdisk -l -u. So how do I get it from this false idea back to where it was before 10.04 upgrade worked it's magic.

Anyone at all?

[olddave1]

Bump.

As far as I can tell this must be a bug in the upgrade software. It has found something on the disk that is left over from when the disk was in a RAID 1 setup a couple of years ago. This ignores the fact it has been running from a single disk for over a year.