[karmic] various pre-mount errors

[arky]

Binary package hint: casper

Begin: Running /scripts/casper-premount ...
Done.
Done.
/init: line 1: can't open /dev/sda: no such file
unable to open '/dev/sda'
/init: line 1: can't open /dev/sda: no such file
/init: line 1: can't open /dev/sda1: no such file
/init: line 1: can't open /dev/sda2: no such file
/init: line 1: can't open /dev/sda5: no such file
/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
/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
/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
/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
/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
stdin: error 0
stdin: error 0
/init: line 1: can't open /dev/sr0: No medium found
Warning: Unable to find the persistent home medium
stdin: error 0
/init: line 1: can't open /dev/sr0: No medium found
stdin: error 0
/init: line 1: can't open /dev/sr0: No medium found
/init: line 1: can't open : no such file
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu4) 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

/init: line 1: du: not found
expr: non-numeric argument
umount: can't umount /mnt/tmp_fs_size: Invalid argument
Warning: Impossible to include the casper-sn Snapshot
stdin: error 0
/init: line 1: can't open /dev/sr0: No medium found
stdin: error 0
/init: line 1: can't open /dev/sr0: No medium found
/init: line 1: can't open : no such file
BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu4) 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

/init: line 1: du: not found
expr: non-numeric argument
umount: can't umount /mnt/tmp_fs_size: Invalid argument
Warning: Impossible to include the home-sn Snapshot
Done.

ProblemType: Bug
Architecture: i386
Date: Wed Jul 29 06:24:21 2009
DistroRelease: Ubuntu 9.10
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Alpha i386 (20090727)
Package: casper 1.183
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-3.19-generic
SourcePackage: casper
Uname: Linux 2.6.31-3-generic i686

[Tormod Volden (tormodvolden)]

Thanks for your report. This was fixed here:

casper (1.190) karmic; urgency=low

  [ Colin Watson ]
  * Don't produce an invalid sed program when trying to remove an applet
    which isn't in the panel (LP: #406188).

  [ Tormod Volden ]
  * do not remount filesystems that already have been probed when
    searching for the livefs (LP: #424464)
  * Fix quoting in try_snap (LP: #424742).
  * Silence error messages for non-existent device nodes (LP: #425159).

 -- Colin Watson < <email address hidden>> Mon, 07 Sep 2009 13:10:53 +0100

[Caysho (caysho)]

Getting this error when booting the mythbuntu 9.10 Alpha 6 Live CD.

[Caysho (caysho)]

Found bug 432176 which is open and covers the problem.

[Luca Livraghi (luca91)]

I still have this bug with the ubuntu 9.10 final version. Nothing seems to be fixed

[Ion (ionlng)]

I get the same error as well during boot. Probably the fixes haven't been applied to the final release of 9.10.

[Mikko Kortelainen (kortsi)]

I am suffering from this same problem on an HP Compaq nc8439. Booting from USB key with Karmic Desktop 32-bit image.

/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
mount: mounting /dev/sdb on /cdrom failed: Invalid argument

BusyBox v1.13.3 (Ubuntu 1:1.13.3-1ubuntu7) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs) /init: line 1: can't open /dev/sr0: No medium found
mount: mounting /dev/sdb on /snap-backing failed: Device or resource busy

[beratchu (beratchu)]

Still remaining.
Ubuntu Desktop CD amd64 final release

[wyginwys (wyginwys-hotmail)]

I confirm the same bug for Karmic Final Release Amd64 for a computer Amd Phenom II x4 965, Gigabyte 790fxta-ud5 board etc.

[SDonatas (sdonatas)]

I have the same problem on my HP DV6529em laptop. I have a fear that this might be motherboard failure, because I have long delay before ubuntu starts to read files from HDD on boot, also live CD which previously worked fine now says stdin error 0. Also I tried launching vista recovery cd and it crashes during boot. In some cases laptop for no reason stops on bios screen. And one more thing my DVD drive has disappeared from Ubuntu and when I turn on my touchpad, keyboard stops working and touchpad doesn't work either. Anyone, similar symptoms?

[Maximo Arratia (megasis)]

Same problem here, I'm using an USB with Ubuntu 10.04 2GB Persistent (casper), but the PC I'm using has no Hard Drives at all ( I disconnected them for a test). If I put the Hard Drive that boots Windows XP then Ubuntu starts without any issue.
If I put the other drive that has multimedia (videos and Music) without the boot drive it doesn't work.

This doesn't make any sense, I want to use Linux but apparently it requires to have a bootable partition on the file system.

Once again, this is because my XP bootable drive is not working properly, so I want to access the other dirve using linux from USB, to see my movies, music, etc.

It's a requirement that the PC has an active partition with a working boot record or MBR to let Ubuntu work?

[Fernando J. Cordeiro (perfectron)]

Same problem with Ubuntu 11.04 on a HP G42-240 Notebook (Core i3)