Just achieve this by add on the /etc/fstab exactly below :
## Backup disk on usbdrive TOSHIBA
/dev/sdc1 /media/crashplanext4defaults,auto,_netdev00
Of course the ## means what is next is a comment.
default,aotu,_netdevhelp me to get my usb drive mounted durin
This was fixed in 9.10 when we switched to upstart instead of util-
linux's mountall.
** Changed in: util-linux (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Instead of hacking /usr/share/initramfs-tools/init, it's more elegant
and robust to add the delay as a rootdelay boot parameter. E.g. edit
/etc/default/grub as follows:
GRUB_CMDLINE_LINUX_DEFAULT="quiet rootdelay=10"
and run 'sudo update-grub'.
--
You received this bug notification because you
If I understand Scott's reply, the problem is that we all expect a
synchronous response from an asynchronous device. What about writing a
small daemon that is automatically activated at boot (init.d), and waits
until the device is available in order to mount it? Feeding the daemon
with the mount pa
I'm seeing this bug on 3 totally different machines, all booting off usb
drives, all without CD drives.
luckily, all the usb drives are just /boot, and i can bring them up
manually with "mount -a" when i need to do /boot update/upgrades
i'm with Marcelo, it would be nice to have an options file
Hi, is there any way to get rid of this problem easier?
Maybe allowing some "init_delay=10" parameter in the options field,
inside /etc/fstab for that usb device entry, and make update-initramfs
to search for it when updating... (it's not a beautiful idea, right, but
maybe it's cleaner than the cu
I use an external USB drive as /home and it seems to have worked great
until about when this bug was originally reported. Something
changed/regressed that caused some USB devices to be enumerated after
the partitions in /etc/fstab are mounted. I can completely corroborate
the experience mikeabout d
This is a fundamental issue with our boot sequence, and has always been.
The problem is that the USB bus is inherently asynchronous. After we
load the USB host driver, devices will begin appearing throughout the
rest of the boot sequence. I guess your device is taking longer to
appear than norma
This was plaguing me too until I found the above post. For me, the steps to
reproduce are:
1) Enter the drive to be mounted in /etc/fstab -- something like:
UUID=XXX /mnt/backup ext3 defaults,relatime 0 0
2) sudo mount -a -- which would succeed
3) sudo reboot
4) L
I have been searching Ubuntu Forums and found
http://ubuntuforums.org/archive/index.php/t-1021719.html
It is the same issue. It is interesting that the problem only manifests
itself if there is no CD-ROM drive installed. This is the case with the
server machine I am using.
The last post in thi
10 matches
Mail list logo
