Headless Ubuntu Natty Image Hangs at 100% Filesystem Resize and then Denies Write Permissions

[Milky]

Currently, I'm having trouble with a fresh copy of the Ubuntu Natty
headless image - http://cdimage.ubuntu.com/ubuntu-headless/daily-preinstalled/current/
(16th of April) - while booting up on the Pandaboard.

The kernel will uncompress, load and then continue to resize the root
partition. Eventually, the resize halts at [100/100] and continues no
further (I have waited 1 whole hour to see if it would complete, and
no luck).

***************************************************************************************************
reading boot.scr

350 bytes read
Running bootscript from mmc0 ...
## Executing script at 82000000
reading uImage

4116440 bytes read
reading uInitrd

3470029 bytes read
## Booting kernel from Legacy Image at 80000000 ...
Image Name: Ubuntu Kernel
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4116376 Bytes = 3.9 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 81600000 ...
Image Name: Ubuntu Initrd
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 3469965 Bytes = 3.3 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Caching vfat content in /dev/.initramfs/jasper-vfat ...
Resizing root partition ...
Re-writing vfat partition ...
Resizing root filesystem. Please wait, this will take a moment ...
Resizing root filesystem ...
Checking filesystem before resizing...
Resizing, please wait...
Resizing, pass: 1 [ 100/100]
***************************************************************************************************
|
|
So, I reboot the Pandaboard, interrupt the autoboot process and set
the root and rootdelay environment variables and then boot, via these
commands... (Idea from: http://www.omappedia.org/wiki/Get_started_with_ubuntu_on_omap4#Boot_the_board
)

Panda # setenv bootargs root=/dev/mmcblk0p2 rootdelay=1
Panda # boot

This is the output...
|
|
***************************************************************************************************
//etc... etc...

Resizing, pass: 1 [100/100]Enabling serial console login
Setting up fstab
Setting up swap
Enabling oem-config
Writing flash-kernel configuration
Creating bootloader configuration
[ 232.905609] journal commit I/O error
Rebooting into configuration session
[ 247.687744] Restarting system.
***************************************************************************************************
|
|
Reboot...
|
|
***************************************************************************************************
//etc... etc...

Creating bootloader configuration
[ 45.835388] journal commit I/O error
fsck from util-linux-ng 2.17.2
/dev/mmcblk0p2: recovering journal
[ 48.028289] mmcblk0: error -110 transferring data, sector 148529,
nr 16, card status 0xc00
[ 48.037231] end_request: I/O error, dev mmcblk0, sector 148529
[ 48.043365] Buffer I/O error on device mmcblk0p2, logical block 493
[ 48.049957] end_request: I/O error, dev mmcblk0, sector 148537
[ 48.056060] Buffer I/O error on device mmcblk0p2, logical block 494
/dev/mmcblk0p2 contains a file system with errors, check forced.
Your disk drives are being checked for errors. This may take some time
Press C to cancel all checks currently in progress
/dev/mmcblk0p2: ***** REBOOT LINUX *****
/dev/mmcblk0p2: 44943/1907808 files (0.1% non-contiguous),
388470/3875681 blocks
mountall: fsck / [352] terminated with status 3
mountall: System must be rebooted: /
init: mountall main process (314) terminated with status 4
[ 92.632568] omapdss DISPC error: timeout waiting for EVSYNC
[ 92.734069] omapdss DISPC error: timeout waiting for EVSYNC
[ 92.740234] Restarting system.
***************************************************************************************************
|
|
Reboot... again... sigh...
|
|
***************************************************************************************************
//etc... etc...

Uncompressing Linux... done, booting the kernel.
fsck from util-linux-ng 2.17.2
/dev/mmcblk0p2: clean, 44943/1907808 files, 388470/3875681 blocks
[ 21.216339] mmcblk0: error -110 transferring data, sector 2120937,
nr 96, card status 0xc00
[ 21.225463] end_request: I/O error, dev mmcblk0, sector 2120937
[ 21.231689] Buffer I/O error on device mmcblk0p2, logical block
247044
[ 21.238555] end_request: I/O error, dev mmcblk0, sector 2120945
[ 21.244781] end_request: I/O error, dev mmcblk0, sector 2120953
[ 21.250976] end_request: I/O error, dev mmcblk0, sector 2120961
[ 21.257202] end_request: I/O error, dev mmcblk0, sector 2120969
[ 21.263397] end_request: I/O error, dev mmcblk0, sector 2120977
[ 21.269622] end_request: I/O error, dev mmcblk0, sector 2120985
[ 21.275848] end_request: I/O error, dev mmcblk0, sector 2120993
[ 21.282043] end_request: I/O error, dev mmcblk0, sector 2121001
[ 21.288269] end_request: I/O error, dev mmcblk0, sector 2121009
[ 21.294494] end_request: I/O error, dev mmcblk0, sector 2121017
[ 21.300720] end_request: I/O error, dev mmcblk0, sector 2121025
[ 21.730865] mmcblk0: error -110 transferring data, sector 2121041,
nr 40, card status 0xc00
[ 21.739898] end_request: I/O error, dev mmcblk0, sector 2121041
[ 21.746124] end_request: I/O error, dev mmcblk0, sector 2121049
[ 21.752319] end_request: I/O error, dev mmcblk0, sector 2121057
[ 21.758544] end_request: I/O error, dev mmcblk0, sector 2121065
[ 21.764770] end_request: I/O error, dev mmcblk0, sector 2121073
[ 24.234527] mmcblk0: error -110 transferring data, sector 1725489,
nr 8, card status 0xc00
[ 24.243804] end_request: I/O error, dev mmcblk0, sector 1725489
[ 24.982604] mmcblk0: error -110 transferring data, sector 1725497,
nr 16, card status 0xc00
[ 24.991973] end_request: I/O error, dev mmcblk0, sector 1725497
[ 24.998199] end_request: I/O error, dev mmcblk0, sector 1725505
[ 26.366302] Aborting journal on device mmcblk0p2.
[ 26.371337] EXT3-fs (mmcblk0p2): error: ext3_journal_start_sb:
Detected aborted journal
[ 26.379791] EXT3-fs (mmcblk0p2): error: remounting filesystem read-
only
mkstemp: Read-only file system
* Starting AppArmor
profiles [fail]
touch: setting times of `/var/lib/sudo': Read-only file system
debconf: DbDriver "config": could not write /var/cache/debconf/
config.dat-new: Read-only file system
[ 68.233428] EXT3-fs error (device mmcblk0p2): ext3_lookup: deleted
inode referenced: 113035
***************************************************************************************************
|
|
At this point... it hangs, so I manually reboot... ending up with:
|
|
***************************************************************************************************
//etc... etc...

Uncompressing Linux... done, booting the kernel.
[ 17.022644] journal_bmap: journal block not found at offset 12 on
mmcblk0p2
[ 17.029968] journal_bmap: journal block not found at offset 24 on
mmcblk0p2
mount: mounting /dev/disk/by-uuid/e9cfe8ed-0ef8-48ff-a45f-fc110774dfe9
on /root failed: Invalid argument
mount: can't find /root in /proc/mounts
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 requested /sbin/init.
No init found. Try passing init= bootarg.


BusyBox v1.17.1 (Ubuntu 1:1.17.1-10ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)
***************************************************************************************************

It seems that the filesystem is corrupted in some way... as a quick
"fsck" ends up with warnings about the filesystem having more blocks
than the 16GB SD card itself.

I used the instructions issued here to copy the image to the SD
card... https://wiki.ubuntu.com/ARM/OMAPHeadlessInstall

So does anyone have any ideas to why this isn't even resizing in the
first place? Cheers

[michele]

I have reported the same issue here:
http://groups.google.com/group/pandaboard/browse_thread/thread/de07779a46ff6cc5
In my case headless works with 4 GB cards but not with 8 GB ones, it
resizes the partitions correctly.

On Apr 16, 10:54 am, Milky <akava...@gmail.com> wrote:
> Currently, I'm having trouble with a fresh copy of the Ubuntu Natty

> headless image -http://cdimage.ubuntu.com/ubuntu-headless/daily-preinstalled/current/

[Milky]

Yeah, I've bought a 4GB card and resorted to installing Linaro onto
it, which works.

When installing Natty Beta 2 Headless onto my 16GB card (http://
cdimage.ubuntu.com/ubuntu-headless/releases/natty/beta-2/), it
amazingly gets past the 100/100 resize... only to hang at the
"Creating bootloader configuration" prompt.

Even installing Linaro onto the 16GB card results in Read only
filesystems and hence not being able to mount /sys etc. Funnily enough
though, the first boot works, it's just that on reboot all hell breaks
loose...

Now I have no idea what to do... because jasper.log mentions nothing
about the bootloader config.

On Apr 18, 4:31 pm, michele <michele.zaffa...@gmail.com> wrote:
> I have reported the same issue here:http://groups.google.com/group/pandaboard/browse_thread/thread/de0777...

[Bryan Smith]

There seems to be issues with SD cards over 4GB. I've tried  an 8 and 16GB and both fail. Just switch up to a smaller SD card.

--
A healthy diet  includes Linux, Linux, and more Linux.

[Sriram Rangan]

A 16 gb sd card works fine for me

[Bryan Smith]

Might depend on the SD media but it's also reported here:

http://comments.gmane.org/gmane.comp.embedded.pandaboard/1486

[GrueMaster]

I have not experienced this problem with the released version of the
Headless image (http://cdimage.ubuntu.com/releases/11.04/release/
ubuntu-11.04-preinstalled-headless-armel+omap4.img.gz) using 4G, 8G,
or 16G flash drives (can't afford a 32G to test with - sorry). Please
try with the released image.

Tobin Davis
Ubuntu on Arm QA Tech.

On May 10, 8:24 pm, Bryan Smith <bryansmit...@gmail.com> wrote:
> Might depend on the SD media but it's also reported here:http://comments.gmane.org/gmane.comp.embedded.pandaboard/1486
>
> On Tue, May 10, 2011 at 11:11 PM, Sriram Rangan <sri...@sriramsr.info>wrote:
>
>
>
> > A 16 gb sd card works fine for me

> > On May 11, 2011 8:37 AM, "Bryan Smith" <bryansmit...@gmail.com> wrote:
> > > There seems to be issues with SD cards over 4GB. I've tried an 8 and 16GB
> > > and both fail. Just switch up to a smaller SD card.
>

> >http://www.omappedia.org/wiki/Get_started_with_ubuntu_on_omap4#Boot_t...

> > >> card...https://wiki.ubuntu.com/ARM/OMAPHeadlessInstall

[Milky]

Mmm, I gave in to writing the image to a 2GB MicroSD card (Image from
the 27th of April)... so far, 10 days straight of uptime and smooth
sailing ^^

Will try the new Natty Headless image now... and will post results.
Cheers for the replies.

> ...
>
> read more »

[Milky]

Oh and Bryan, that's a Gmane copy of this thread... lol, it got me too
there for a while...
That is... until I was baffled when I saw my own picture in the
posts...

[Milky]

Unfortunately... On the 16GB card, even the final release hangs at
100/100 while resizing.
Must be something to do with the card... or some SDHC problem...

On May 15, 1:30 pm, GrueMaster <gruemas...@gmail.com> wrote:

> ...
>
> read more »

[BrianC]

FWIW, I was running into the same problem: when booting Ubuntu 11.10 on a v3
Panda board from an 8GB SanDisk Extreme Class 10 SD Card, the boot hangs at
“Resizing, please wait…”

Resolved it by programming the SD card using Win32ImageWriter
(http://launchpad.net/win32-image-writer) instead of programming the card using
the "sudo sh -c 'zcat ./ubuntu-*-netbook-armel+omap4.img.gz |dd bs=4M
of=/dev/sde ; sync'" command from Ubunut 11.04.

So it doesn't look like a hardware problem...

Regards,
Brian

[ॐ M.Reddi Prasad Reddy ॐ]

Dear Brian,

I don't think so, thats not h/w problem.

$  sudo sh -c 'zcat ./ubuntu-*-netbook-armel+omap4.img.gz |dd bs=4M
of=/dev/sde'                                                 **** make sure you have set the correct drive name  and $ is prompt in terminal

$ sync

worked fine in my case.

Regards,

M.Reddi Prasad Reddy

[Brian C]

Hi Reddy,
   Yes, that command worked fine for me to, when I ran it from Ubuntu 10.04.  However, whenever I burned an SD Card using that command from Ubuntu 11.04, the Pandaboard would not boot properly.  See https://groups.google.com/d/topic/pandaboard/_17w0x8YTTw/discussion for details...

Regards,
  Brian

[ॐ M.Reddi Prasad Reddy ॐ]

Hai Brian,

Can you share the error which you are getting with the ubuntu 11.04 with headless.

Regards,

M.Reddi Prasad Reddy