>
> From: Usama Akkad <email address hidden>
> Subject: [Bug 492301] Re: Can not mount /dev/loop1 on /cow
> To: <email address hidden>
> Date: Tuesday, 12 January, 2010, 1:54 PM
> I've the same problem with Asus Eee
> 1005HA and the workaround works for
> me
>
Hi,
The workaround asks you to disable persistence completely right?
I wanted persistence and found a solution to the problem. To use a later version of 'usb-creator' v0.2.12 which has no problems with persistence.
If you want persistence, try using that version of 'usb-creator'.
Thanks,
Praveen
> ** Changed in: usb-creator (Ubuntu)
> Status: New =>
> Confirmed
>
> --
> Can not mount /dev/loop1 on /cow
> https://bugs.launchpad.net/bugs/492301
> You received this bug notification because you are a direct
> subscriber
> of the bug.
>
> Status in “usb-creator” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: usb-creator
>
> LiveUSB stick created using this program failed to boot.
> The size of my usb stick is 2GB.
>
> The version of usb-creator I have is 0.1.16 (according to
> synaptic)
>
> 1. I created a persistence-enabled 128MB (default value)
> drive with xubuntu 9.10 desktop i386 iso image.
> The stick booted fine and the OS was running ok.
>
> 2. I created a persistence-enabled 1.2GB (max value by
> pulling the slider all the way up). The stick fails to boot
> by giving the message: 'Can not mount /dev/loop1 on /cow'
>
> I have re-verified the checksums of the iso that I was
> trying to use and they are fine. I re-tried this particular
> step thrice and I got the logs during that third attempt.
>
> Using the instructions at: https://wiki.ubuntu.com/DebuggingCasper , I got the
> following in casper.log:
>
> --
> Begin: Running /scripts/casper-premount ...
> Done.
> Done.
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> stdin: error 0
> BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) multi-call
> binary
>
> Usage: mount [flags] DEVICE NODE [-o options,more-options]
>
> Mount a filesystem. Filesystem autodetection requires /proc
> be mounted.
>
> Options:
> -a
> Mount all filesystems in fstab
> -f
> don't mount
> -i
> Don't call /sbin/mount.<filesystem> helper
> -r
> Read-only mount
> -t fs-type Filesystem
> type
> -w
> Read-write mount (default)
> -o option:
> loop
> Ignored (loop devices are autodetected)
> [a]sync
> Writes are asynchronous / synchronous
> [no]atime Disable /
> enable updates to inode access times
> [no]diratime Disable /
> enable atime updates to directories
> [no]relatime Disable /
> enable atime updates relative to modification time
> [no]dev
> Allow use of special device files /
> disallow them
> [no]exec Allow use of
> executable files / disallow them
> [no]suid Allow
> set-user-id-root programs / disallow them
> [r]shared Convert
> [recursively] to a shared subtree
> [r]slave Convert
> [recursively] to a slave subtree
> [r]private Convert
> [recursively] to a private subtree
> [un]bindable Make
> mount point [un]able to be bind mounted
> bind
> Bind a directory to an additional
> location
> move
> Relocate an existing mount point
> remount
> Remount a mounted filesystem, changing
> its flags
> ro/rw
> Mount for read-only / read-write
>
> There are EVEN MORE flags that are specific to each
> filesystem
> You'll have to see the written documentation for those
> filesystems
>
> Can not mount /dev/loop1 on /cow
> --
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/usb-creator/+bug/492301/+subscribe
>
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http://in.yahoo.com/
>
> From: Usama Akkad <email address hidden>
> Subject: [Bug 492301] Re: Can not mount /dev/loop1 on /cow
> To: <email address hidden>
> Date: Tuesday, 12 January, 2010, 1:54 PM
> I've the same problem with Asus Eee
> 1005HA and the workaround works for
> me
>
Hi,
The workaround asks you to disable persistence completely right?
I wanted persistence and found a solution to the problem. To use a later version of 'usb-creator' v0.2.12 which has no problems with persistence.
If you want persistence, try using that version of 'usb-creator'.
Thanks,
Praveen
> ** Changed in: usb-creator (Ubuntu) /bugs.launchpad .net/bugs/ 492301 /wiki.ubuntu. com/DebuggingCa sper , I got the casper- premount ... more-options] <filesystem> helper /bugs.launchpad .net/ubuntu/ +source/ usb-creator/ +bug/492301/ +subscribe
> Status: New =>
> Confirmed
>
> --
> Can not mount /dev/loop1 on /cow
> https:/
> You received this bug notification because you are a direct
> subscriber
> of the bug.
>
> Status in “usb-creator” package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: usb-creator
>
> LiveUSB stick created using this program failed to boot.
> The size of my usb stick is 2GB.
>
> The version of usb-creator I have is 0.1.16 (according to
> synaptic)
>
> 1. I created a persistence-enabled 128MB (default value)
> drive with xubuntu 9.10 desktop i386 iso image.
> The stick booted fine and the OS was running ok.
>
> 2. I created a persistence-enabled 1.2GB (max value by
> pulling the slider all the way up). The stick fails to boot
> by giving the message: 'Can not mount /dev/loop1 on /cow'
>
> I have re-verified the checksums of the iso that I was
> trying to use and they are fine. I re-tried this particular
> step thrice and I got the logs during that third attempt.
>
> Using the instructions at: https:/
> following in casper.log:
>
> --
> Begin: Running /scripts/
> Done.
> Done.
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> /init: line 1: can't open /dev/sr0: No medium found
> stdin: error 0
> BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) multi-call
> binary
>
> Usage: mount [flags] DEVICE NODE [-o options,
>
> Mount a filesystem. Filesystem autodetection requires /proc
> be mounted.
>
> Options:
> -a
> Mount all filesystems in fstab
> -f
> don't mount
> -i
> Don't call /sbin/mount.
> -r
> Read-only mount
> -t fs-type Filesystem
> type
> -w
> Read-write mount (default)
> -o option:
> loop
> Ignored (loop devices are autodetected)
> [a]sync
> Writes are asynchronous / synchronous
> [no]atime Disable /
> enable updates to inode access times
> [no]diratime Disable /
> enable atime updates to directories
> [no]relatime Disable /
> enable atime updates relative to modification time
> [no]dev
> Allow use of special device files /
> disallow them
> [no]exec Allow use of
> executable files / disallow them
> [no]suid Allow
> set-user-id-root programs / disallow them
> [r]shared Convert
> [recursively] to a shared subtree
> [r]slave Convert
> [recursively] to a slave subtree
> [r]private Convert
> [recursively] to a private subtree
> [un]bindable Make
> mount point [un]able to be bind mounted
> bind
> Bind a directory to an additional
> location
> move
> Relocate an existing mount point
> remount
> Remount a mounted filesystem, changing
> its flags
> ro/rw
> Mount for read-only / read-write
>
> There are EVEN MORE flags that are specific to each
> filesystem
> You'll have to see the written documentation for those
> filesystems
>
> Can not mount /dev/loop1 on /cow
> --
>
> To unsubscribe from this bug, go to:
> https:/
>
The INTERNET now has a personality. YOURS! See your Yahoo! Homepage. http:// in.yahoo. com/