PDA

View Full Version : [wubi] Completing the Ubuntu installation fails Lenovo Y480



WatchMaker7
May 25th, 2012, 11:52 PM
Hello everyone,

I recently got a new Y480 from Lenovo with a small 32GB caching SSD for the primary 1TB HDD. I'm not sure if this is the source of the problem or not yet but I can't get wubi to install ubuntu inside windows.
When I run wubi I have two partitions that I can add ubuntu to: the primary C: partition and the backup D: partition. When I try the C: partition with a 30GB install everything seems to go well until I restart. Then I get a Mounting failed: failed to read last sector error. I've fiddled with install size some to see if that was the problem somehow and I get a more general error: couldn't read file message on restart if I select 18GB.
I've run the boot info script and here's the output from that:

Boot Info Script 0.61 [1 April 2012]


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

=> Windows is installed in the MBR of /dev/sda.
=> Windows is installed in the MBR of /dev/sdb.
=> Syslinux MBR (4.04 and higher) is installed in the MBR of /dev/sdc.
=> FreeDOS (eXtended FDisk) is installed in the MBR of /dev/sdd.

sda1: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /bootmgr /Boot/BCD

sda2: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Mounting failed: Failed to read last sector (1923478959): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/sda2': Invalid argument
The device '/dev/sda2' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Failed to read last sector (1923478959): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/sda2': Invalid argument
The device '/dev/sda2' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?

sdb1: __________________________________________________ ________________________

File system:
Boot sector type: -
Boot sector info:
Mounting failed: Failed to read last sector (1923478959): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/sda2': Invalid argument
The device '/dev/sda2' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
Failed to read last sector (1923478959): Invalid argument
HINTS: Either the volume is a RAID/LDM but it wasn't setup yet,
or it was not setup correctly (e.g. by not using mdadm --build ...),
or a wrong device is tried to be mounted,
or the partition table is corrupt (partition is smaller than NTFS),
or the NTFS boot sector is corrupt (NTFS size is not valid).
Failed to mount '/dev/sda2': Invalid argument
The device '/dev/sda2' doesn't seem to have a valid NTFS.
Maybe the wrong device is used? Or the whole disk instead of a
partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
mount: unknown filesystem type ''

sdb2: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files: /wubildr

sdb3: __________________________________________________ ________________________

File system: ntfs
Boot sector type: Windows Vista/7: NTFS
Boot sector info: According to the info in the boot sector, sdb3 has
40550399 sectors, but according to the info from
fdisk, it has 40963503 sectors.
Operating System:
Boot files: /bootmgr /boot/bcd

sdc1: __________________________________________________ ________________________

File system: vfat
Boot sector type: SYSLINUX 4.06 4.06-pre1
Boot sector info: Syslinux looks at sector 1452416 of /dev/sdc1 for its
second stage. SYSLINUX is installed in the directory.
The integrity check of the ADV area failed. No errors
found in the Boot Parameter Block.
Operating System:
Boot files: /syslinux/syslinux.cfg /ldlinux.sys

sdd1: __________________________________________________ ________________________

File system: vfat
Boot sector type: FAT16
Boot sector info: No errors found in the Boot Parameter Block.
Operating System:
Boot files:

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

Drive: sda __________________________________________________ ___________________

Disk /dev/sda: 32.0 GB, 32017047552 bytes
255 heads, 63 sectors/track, 3892 cylinders, total 62533296 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sda1 * 2,048 411,647 409,600 7 NTFS / exFAT / HPFS
/dev/sda2 411,648 1,923,890,607 1,923,478,960 7 NTFS / exFAT / HPFS

/dev/sda2 ends after the last sector of /dev/sda

Drive: sdb __________________________________________________ ___________________

Disk /dev/sdb: 1000.2 GB, 1000204886016 bytes
255 heads, 63 sectors/track, 121601 cylinders, total 1953525168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdb1 1,979 1,861,361,663 1,861,359,685 12 Compaq diagnostics
/dev/sdb2 1,861,361,664 1,912,561,663 51,200,000 7 NTFS / exFAT / HPFS
/dev/sdb3 1,912,561,664 1,953,525,167 40,963,504 12 Compaq diagnostics


Drive: sdc __________________________________________________ ___________________

Disk /dev/sdc: 2004 MB, 2004877312 bytes
64 heads, 42 sectors/track, 1456 cylinders, total 3915776 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdc1 * 32 3,915,775 3,915,744 6 FAT16


Drive: sdd __________________________________________________ ___________________

Disk /dev/sdd: 1051 MB, 1051721728 bytes
255 heads, 63 sectors/track, 127 cylinders, total 2054144 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes

Partition Boot Start Sector End Sector # of Sectors Id System

/dev/sdd1 63 2,008,124 2,008,062 6 FAT16


"blkid" output: __________________________________________________ ______________

Device UUID TYPE LABEL

/dev/loop0 squashfs
/dev/sda1 126CCA3C6CCA1A7D ntfs SYSTEM_DRV
/dev/sda2 90ECCB32ECCB1200 ntfs Windows7_OS
/dev/sdb2 FEFA75DFFA75951D ntfs LENOVO
/dev/sdb3 40AA7364AA7354FE ntfs LENOVO_PART
/dev/sdc1 D8C5-E127 vfat PENDRIVE
/dev/sdd1 0C41-6344 vfat

================================ Mount points: =================================

Device Mount_Point Type Options

/dev/loop0 /rofs squashfs (ro,noatime)
/dev/sdc1 /cdrom vfat (rw,relatime,fmask=0022,dmask=0022,codepage=cp437, iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
/dev/sdd1 /media/0C41-6344 vfat (rw,nosuid,nodev,uid=999,gid=999,shortname=mixed,d mask=0077,utf8=1,showexec,flush,uhelper=udisks)


========================= sdc1/syslinux/syslinux.cfg: ==========================

--------------------------------------------------------------------------------
# D-I config version 2.0
include menu.cfg
default vesamenu.c32
prompt 0
timeout 50

# If you would like to use the new menu and be presented with the option to install or run from USB at startup, remove # from the following line. This line was commented out (by request of many) to allow the old menu to be presented and to enable booting straight into the Live Environment!
# ui gfxboot bootlogo
--------------------------------------------------------------------------------

================= sdc1: Location of files loaded by Syslinux: ==================

GiB - GB File Fragment(s)

?? = ?? ldlinux.sys 1
?? = ?? syslinux/chain.c32 1
?? = ?? syslinux/gfxboot.c32 1
?? = ?? syslinux/syslinux.cfg 1
?? = ?? syslinux/vesamenu.c32 1

============== sdc1: Version of COM32(R) files used by Syslinux: ===============

syslinux/chain.c32 : COM32R module (v4.xx)
syslinux/gfxboot.c32 : COM32R module (v4.xx)
syslinux/vesamenu.c32 : COM32R module (v4.xx)

=============================== StdErr Messages: ===============================

./bootinfoscript: line 1646: [: 2.73495e+09: integer expression expected


As you can see, something screwy is going on but I'm not sure how to fix it.
At first I thought it was a windows dynamic disk issue but all of the disks are listed as basic in windows. So I don't think that's it.
Anyone have any ideas?
Thanks.

bcbc
May 26th, 2012, 12:52 AM
It's definitely choking on what looks like partition table errors. Can you edit your thread title to mention that - so it attracts the right people who might be able to help you?

Maybe you just have some fakeraid metadata that's confusing the linux utilities.