Insert usb storage for mounting что это
В этом руководстве мы покажем вам шаги по исправлению невозможности смонтировать хранилище в TWRP Recovery. Экосистема Android, благодаря своей природе с открытым исходным кодом, допускает множество настроек.
Единственное требование — разблокировать загрузчик устройства. Как только вы этого добьетесь, вы сможете запустить множество пользовательских двоичных файлов, модов, пользовательских ПЗУ и даже Magisk для рутирования вашего устройства. Однако стандартное восстановление не может установить эти файлы. Вам нужно будет установить кастомное рекавери, например TWRP.
После того, как ваше устройство загрузится в это восстановление, вы можете стереть различные разделы устройства, выполнить резервное копирование Nandroid и, конечно, прошить вышеупомянутые файлы. Однако несколько раз вы можете столкнуться с ошибкой или двумя.
Среди них самые распространенные и пугающие, похоже, не могут смонтировать ошибку хранилища при отображении TWRP. В этом руководстве мы рассмотрим различные причины этой ошибки, а затем перечислим возможные исправления для исправления этой ошибки. Следуйте.
Requirements
Privileged access to your Kali Linux system will be required.
Unmounting the Drive
When you are finished with the device, don't forget to unmount the drive before disconnecting it. Assuming /dev/sdb1 is mounted at /media/external, you can either unmount using the device or the mount point:
You cannot unmount from the desktop by right-clicking the icon if the drive was manually mounted.
User Privileges
If your usb device doesn't appear on your desktop, you should check that your user has the correct privileges. Go to System->Administration->User and Groups, choose the user, click on "Properties", then go to the "User Privileges" tab. You should have the "Access external storage devices automatically" option checked.
USB 2 Issues
Access Your USB drive
Optionally check to see whether your USB drive has been mounted correctly using the following linux command:
Access your files on your USB drive by navigating to the previously created mount point directory /media/usb-drive :
Check your USB drive
Booting from USB storage can be very handy, but there is no guarantee that it will work with your particular combination of computer and USB drive. Even if you are able to boot from your USB drive on one computer, this does not mean that it is going to work with the next one. You can try experimenting with different settings in your PC's BIOS to make it work.
In order to boot from a USB drive, there are a few requirements to meet. The drive must contain at least one partition with a Master Boot Record (MBR) sector. (Some BIOSs do not require this, but many, especially older ones, do.) Formatting using the built-in windows tools will not create an MBR, so you will need to use another tool to do so. For more information, see USB boot without bios support or google "boot from usb" and read a lot. For more technical details, check out Prepping a USB flash device for boot. For a tool from HP which will format a USB stick with an MBR, download the HP USB Disk Storage Format Tool v2.1.8. Make sure you do any partitioning/formatting before you proceed with the following methods.
Make sure to pick a drive that is large enough to hold the contents of the installation CD (about 700MB), 1GB is recommended. Versions of SYSLINUX 3.53 and before require the use of a FAT16 file system, which most 2GB or smaller USB drive come formatted with anyway. This is the most compatible file system, and is recommended. As of version 3.00, SYSLINUX works with FAT32 as well.
Insert the USB drive you want to use for the installer. A few seconds after plugging in the USB drive run the dmesg command or sudo fdisk -l to find the device name it was assigned. The rest of the instructions refer to /dev/sdX1, remember to replace X with your device location.
Using pmount
There is a program called pmount available in the repositories which allows unprivileged users to mount drives as if they were using sudo, even without an entry in /etc/fstab. This is perfect for computers that have users without RootSudo access, like public terminals or thin clients.
pmount can be used with the same syntax as mount (but without sudo), or quite simply as follows:
- This will mount the device /dev/sdb1 at /media/flash_drive.
If you leave off the label option, it will mount by default at /media/device.
To unmount the device, use pumount, like so:
For more help, see the man pages for pmount and pumount.
Before disconnecting devices, you must unmount them first. This is similar to "Safely Remove" in Windows in that the device won't unmount until data is finished being written to the device, or until other programs are finished using it. This applies to all types of storage devices, including flash drives, flash cards, external hard drives, ipods and other media players, and even remote storage like Samba or NFS shares.
Failure to unmount before disconnecting the device can result in loss of data and/or a corrupted file system. There are no exceptions to this rule. Be safe - unmount your drives before disconnecting them!
To see a list of your USB devices (the vendor and device ID's), run:
To see all attached storage devices and their partitions, run:
To see information about currently mounted systems, simply run:
Presented here are some common problems users encounter.
Download harddisk kernel to replace CD-ROM kernel
Set a shell variable to the files' directory, e.g.: HD_MEDIA=your-browser-download-directory
Move files to the root directory
- isolinux (all files)
- casper (vmlinuz and initrd.gz)
- install (all files)
Using mount
Alternate Install (Ubuntu 9.10)
The procedure above causes problems for people when using the Alternate Install CD-ROM. This variant works for me:
Make your USB stick bootable with SYSLINUX
Same as above. Set a shell variable to your USB disk mount point, e.g.: USB_MNT=/media/disk
Configuring Program Autostart
To control which programs automatically start when you plug in a device, go to System-Settings - Details - Removable Media.
For more complex scenarios, see UsbDriveDoSomethingHowto.
UNetbootin (Windows or Linux)
UNetbootin automates this task by providing a GUI to create a bootable Ubuntu Live USB drive from an ISO file, and can be run from both an installed Windows or Linux system, or from a liveCD.
Optional: If you need to activate the original Ubuntu livecd boot menu, for example if you want to disable the framebuffer or read the Ubuntu livecd HELP screens and cheatcodes, please make these changes to your USB drive after your UNetbootin installation is completed:
1) Delete the SYSLINUX.CFG file or rename it to be SYSLINUX.OLD
2) Enter the ISOLINUX folder and rename the ISOLINUX.CFG file to be SYSLINUX.CFG. You may or may not need to rename ISOLINUX.BIN to SYSLINUX.BIN, but it won't hurt.
3) Move up to the top level and rename the ISOLINUX folder to be SYSLINUX
Other notes
- The instructions there work great with gutsy as well, but on my machine i needed to add "vesa vga=771" to the "append anchor" >
- I also succeeded in installing on a Libretto 100CT by using a 2.5" IDE disk in one of those cheap USB cradles. This machine has no CD-ROM, no floppy (on my unit), no USB. I've taken the liberty to annotate my experiences in an indented style, like this. -- Era
- I installed on an IBM X40 using the contents of the mini.iso for edgy on a USB stick instead of using the iso for the bulkier alternate CD. I only had to install syslinux and rename isolinux.cfg to syslinux.cfg (I didn't have to change the contents of the file). It was very easy. I didn't have to try fooling the installer into thinking the stick was the CD and mess with symlinks etc. -- MikkelErup
- I succeeded installing Ubuntu 7.04 (Feisty) with this guide and just a few changes I added. Ubuntu is running stable and without any problems -- Boo
- Short guide (to get the idea): mkfs.vfat /dev/; fdisk /dev/ (make bootable); ./isotostick.sh ubuntu-7.10-desktop-i386.iso /dev/; -- Syke
- Thanks for the advice guys, it also worked on my laptop: got it installed with 7.10 (and the encrypted LVM partitions I needed). I needed
- syslinux -s /dev/sdb1
- mount -o loop /home/stilus/Desktop/mini.iso /media/cdrom0/
- cp -r /media/cdrom0/* /media/Flashdisk
- cd /media/Flashdisk
- mv isolinux.cfg syslinux.cfg
- cd /
- umount /media/Flashdisk
Plugged this Flashdisk in my to-be-installed system, and that was that: let the netinstall begin!! -- stilus
- This does not work, at least for me. Boot fails in syslinux already: selecting "install" boot menu option shows a dialog "install./vm" with button "Start", which does nothing. It seems it somehow tries to interpret the path "install/vmlinuz" as a single 8.3 filename, resulting in the nonsense "install./vm". Same happens for all other boot options. After booting manually, I got further errors later on when trying to find the packages to install.
- What about a howto or tutorial about use Grub instead of syslinux ?
- Jaunty Install from the alternate CD failed for me after following these instructions with "failed to determine the codename for the release". I could go no further. -- naught101
- I had to manually set the partition as bootable after following the instructions for syslinux above to install from my external harddrive. That is, I used gparted to set the "boot" flag to on. There should be some program to do this under Windows as well
USB-Device is or becomes read-only without errors
If you see "Write Protect is off" and no errors in your logfiles, than you should set filesystem type specific mount options (FS_MOUNTOPTIONS) in /etc/usbmount/usbmount.conf. Wrong gid causes mounting read only.
Исправление 3: форматирование внутренней памяти
Если ни один из вышеперечисленных методов не помог устранить проблему с монтированием, возможно, вам придется выбрать ядерный вариант. Форматирование внутреннего хранилища кажется единственным выходом. Это, в свою очередь, сотрет все данные, имеющиеся на вашем устройстве.
Убедитесь, что вы создали эту резервную копию на SD-карте или USB OTG, а не в памяти телефона, так как мы собираемся полностью стереть этот раздел. Когда вы закончите резервное копирование, выполните следующие действия.
- Загрузите устройство в TWRP Recovery.
- Перейдите в Wipe > Advanced Wipe и выберите Internal Storage.
- Наконец, проведите пальцем вправо, чтобы отформатировать этот раздел (все данные будут стерты).
- Как только это будет сделано, ошибка монтирования будет исправлена. Имейте в виду, что внутреннее хранилище может по-прежнему отображаться как 0 МБ. Но на этот раз это данные в реальном времени (ваше внутреннее хранилище очищается, следовательно, используется 0 МБ пространства).
Мы поделились тремя разными методами для одного и того же, дайте нам знать, какой из них сработал за вас.
This page explains how to use USB drives, like external hard disks and USB flash drives (aka USB sticks, thumb drives, pen drives, etc). The material here also applies to flash cards (like in your digital camera).
USB storage devices have the enormous advantage that for the most part they use a standard set of protocols. Thus, instead of needing individual drivers, as does much computer hardware, a standard driver permits access to the devices, making them very portable and able to easily work on many platforms.
For help with internal hard drives, see Fstab and MountingWindowsPartitions.
Preferences
NOTE: This does not seem to apply to Hardy Heron.
Seeking Further Help
The best place to get help with almost any Ubuntu problem is on the Ubuntu Forums. The Absolute Beginner Talk section is best for beginners.
Ubuntu distributions from 8.04 'Hardy' onwards have 'Startup Disk Creator' a usb-creator tool that creates a bootable USB flash drive from a Ubuntu CD or iso image. Most users should use Startup Disk Creator or Unetbootin instead of many alternatives described here that perform similar steps. Current Ubuntu versions can also be cloned directly from the iso file to a USB drive. See Installation/FromUSBStick.
Mount USB drive
At this stage, we are ready to mount our USB drive partition. Execute, the below mount command while replacing the block device path ( /dev/sdc1 ) with the one you took a note about previously.
Create the Mount Point
Now we need to create a mount point for the device. Let's say we want to call it "external". You can call it whatever you want, but if you use spaces in the name it gets a little more complicated. Instead, use an underscore to separate words (like "my_external"). Create the mount point:
Device suddenly becomes read-only
If your device changes suddenly to read-only mode, and you see this kind of error:
This might be the sign of an unclean device. You should check your device. Try TestingStorageMedia to do so. Or use "Disk Utility" (under System, Administration), find your device, unmount it, check the file system, then mount it again.
liveusb-creator (from Fedora)
If you are currently running Fedora you can use the liveusb-creator to create a live Ubuntu USB drive. Use the Use existing live CD option to select an Ubuntu Live CD that you have downloaded.
- Make the USB flash drive bootable using SYSLINUX.
- Copy the contents of the Ubuntu CD to your flash drive (make sure you include hidden files/directories).
Auto-mounting (Ubuntu Server)
By default, disk drives do not auto-mount in Ubuntu Server Edition. If you are looking for a lightweight solution that does not depend on HAL/DBUS, you can install "usbmount".
Unmount USB
Do not remove your USB drive before you do not perform a proper umount otherwise your risk losing your data:
See also
USB Block Device Name
Given you have already inserted your USB drive into your computer, we first need to determine a block device name of your USB partitions. The easiest way to approach this is by executing fdisk -l command to list all drives and their associated partitions.
Scan through the output of the above fdisk -l command and find partition block name. In the example above it is /dev/sdc1 .
Permanent Mount
In case you need to mount your USB drive permanently after reboot first you need to determine the UUID belonging to USB partition you wish to mount:
Create a new /etc/fstab entry:
Your USB drive will now mount automatically after reboot. Please, note that the UUID uniqueness is not guaranteed. It is recommended to use partition tags instead, but that is a tale for another time.
Operating System and Software Versions
Unmounting/Ejecting
- Right-click the desktop icon and select "Unmount" (or in some cases, "Eject").
- In the file manager window, click on the "eject" button next to the name of the mounted volume.
- Right-click the icon in the launcher and select "Unmount".
Difficulty
Mounting
By default, storage devices that are plugged into the system mount automatically in the /media/ directory, open a file browser window for each volume and place an icon on your desktop. The rationale for this slight change of behavior can be found here. If you plug in a usb hard disk with many partitions, all of the partitions will automatically mount. This behaviour may not be what you want; you can configure it as shown below.
If the volumes have labels the icons will be named accordingly. Otherwise, they will be named "disk", "disk-1" and so on.
To change the volume label see RenameUSBDrive.
Confusion
Is this page about installing Ubuntu from a USB stick, or installing it to a USB stick? Those are completely different things, you know.
Ubuntu distributions from 8.04 'Hardy' onwards have 'Startup Disk Creator' a usb-creator tool that creates a bootable USB flash drive from a Ubuntu CD or iso image. Most users should use Startup Disk Creator or Unetbootin instead of many alternatives described here that perform similar steps. Current Ubuntu versions can also be cloned directly from the iso file to a USB drive. See Installation/FromUSBStick.
USB Installation Media (последним исправлял пользователь ckimes 2017-09-22 19:01:48)
The material on this wiki is available under a free license, see Copyright / License for details
You can contribute to this wiki, see Wiki Guide for details
Additional info: I'm working on an up-to-date console-only Debian wheezy linux.
By How do I achieve automatic mounting when this USB device with known UUID is plugged in do you mean you only want to automount this specific USB drive? Or does it matter? I've gone ahead an posted a more generic answer that will automatically mount most USB storage devices, but I am not entirely sure this is what you want.
@Seth I have a specific USB stick which I use for quickly transferring files between the Debian device and other devices (sometimes granting network access for these devices is to much work if you only want to transfer a tiny file quickly).
Mount the Drive
We can now mount the drive. Let's say the device is /dev/sdb1, the filesystem is FAT16 or FAT32 (like it is for most USB flash drives), and we want to mount it at /media/external (having already created the mount point):
The options following the "-o" give you ownership of the drive, and the masks allow for extra security for file system permissions. If you don't use those extra options you may not be able to read and write the drive with your regular username.
Otherwise, if the device is formatted with NTFS, run:
Note: You must have the ntfs-3g driver installed. See MountingWindowsPartitions for more information.
Using Disks
Disks (the GNOME disk utility) is an application for visually managing disk drives and media. When you run it, you will see a list of your drives, including USB drives. If you click a drive on the list, you can view its details, and you can click the triangle-shaped button (Play button) to mount the drive. (This method works even when the drive does not auto-mount.)
Исправление 1: удалить экран блокировки
Если вы используете графический ключ на своем устройстве, TWRP не сможет его расшифровать. Рекомендуется переключиться на пин-код или пароль.
- Для этого, если вы загружены в TWRP, перезагрузите устройство в Системе.
- После загрузки перейдите в Настройки > Безопасность и экран блокировки > Блокировка экрана.
- Выберите из списка PIN-код или пароль. Теперь перезагрузите устройство обратно в TWRP.
- Теперь программа восстановления попросит вас ввести PIN-код / пароль. Введите его, и ваше хранилище будет зашифровано.
Теперь попробуйте прошить нужные файлы и посмотрите, исправлена ли проблема с невозможностью монтировать хранилище в TWRP Recovery.
Причина невозможности смонтировать хранилище в TWRP
Первая причина, по-видимому, связана с тем, что внутреннее хранилище вашего устройства зашифровано. В результате TWRP не может расшифровать его на ходу и, следовательно, не может получить доступ к файлам, хранящимся на вашем устройстве.
Это причина, по которой эта ошибка чаще всего возникает, когда вы собираетесь прошить файл с помощью этого восстановления.
В других случаях ваш раздел данных может быть поврежден из-за того, что мигает неправильный файл или файл в неправильном разделе. Во всех этих сценариях ваш TWRP может отображать внутреннее хранилище как имеющее 0 МБ занятого места.
Но не волнуйтесь, это не так, и ваши данные на данный момент могут быть все еще нетронутыми. Итак, с учетом сказанного, вот различные методы исправления невозможности монтировать хранилище в TWRP Recovery.
Мы поделимся тремя разными способами решения этой проблемы. Следуйте инструкциям в том же порядке, как указано. Просто убедитесь, что ваше устройство уже загружено в TWRP. Е
3 Answers 3
I use the usbmount package to automount USB drives on my Ubuntu server install. I have confirmed that the package exists for Wheezy too. Recently also added for Jessie.
usbmount will automount hfsplus, vfat, and ext (2, 3, and 4) file systems. You can configure it to mount more/different file systems in /etc/usbmount/usbmount.conf . By default it mounts these file systems with the sync,noexec,nodev,noatime,nodiratime options, however this can also be changed in the aforementioned configuration file.
usbmount also supports custom mount options for different file system types and custom mountpoints.
after installing this it did start auto-mounting drives again but I don't seem to have access rights as my user, making it needlessly painful to copy files. Would you expect I'd have to edit the config mentioned to achieve this or is it likely to be something else? My machine has just been crippled by some updates - i had to shutdown on the command line previously but now it wont work with my usb. also just lost my graphics drivers so my desktop looks like windows 3.1 or something! :( not been a good week for my computer
@Jonny You didn't mention what distribution you were running but if it has a GUI it should auto-mount drives by default. It sounds like what you are experiencing is part of a bigger, different problem; especially if other things started behaving oddly too.
The procedure on how to mount USB drive on Kali Linux is no different from any other Linux distribution. Kali Linux was used by this guide to provide you with simple to follow steps on how to mount USB drive on Linux.
Instructions
Boot from the USB stick
Boot the computer from the USB drive. The installation can now be done as if you would be booting from the installation CD.
Conventions
Copy the Ubuntu CD to your USB stick, Adjust SYSLINUX
Note: in this variant, the USB stick only contains a few boot-supporting files and the raw .iso image.
Исправление 2: восстановить или изменить файловую систему
Вы также можете попробовать восстановить или изменить файловую систему вашего устройства. Все это можно было сделать прямо из самого TWRP.
Live USB creator (GUI-based, runs from Live CD)
Live USB creator automates the process of creating a bootable Live USB system from a running Ubuntu Live CD. Simply run the Live CD, install the tool and start the Live USB installation from the System administration menu.
You can run the tool from your normal desktop, just insert the Ubuntu Live CD and run it.
You may encounter an error when trying to boot from the USB drive, something like "Missing operating system". Make sure that you can mount the USB drive on a normal Ubuntu install, and that you can browse it in the file browser. If you can't, it hasn't been created properly. I found that using fdisk to delete the partition on the drive first, then running liveusb, worked nicely.
ubuntu-server-flashdrive-installer.sh (Command-line shell script, runs from Linux)
Comment: Does not work with ubuntu-8.10-server-amd64.iso - says no usable ISO found - any ideas?
Get the Information
Sometimes, devices don't automount, in which case you should try to manually mount them. First, you must know what device you are dealing with and what filesystem it is formatted with. Most flash drives are FAT16 or FAT32 and most external hard disks are NTFS. Type the following:
Find your device in the list. It is probably something like /dev/sdb1. For more information about filesystems, see LinuxFilesystemsExplained.
After Installing
After finishing the installation, edit /etc/fstab and make sure that /media/cdrom0 points to the CD drive and not to the USB drive. If you don't, you might get this error when trying to mount a USB drive: "Cannot mount volume. Invalid mount option when attempting to mount the volume." This is because the installer believes it is installing from a CD drive (bug 150872).
You can also rename the real cdrom mount point to /media/cdrom0 if you like.
Save the file, and you're done.
recent kernels workaround, from Karmic
- Determine your device id using
- Find which bus it is connected to. The bus id can be found as a folder in /sys/bus/pci/drivers/ehci_hcd. The following script explores buses and connected devices: The information is also usually available in /var/log/kern.log
- Unbind the bus (and all devices) from the ehci_hcd driver. Insert the bus id in the following command, using the format 0000:00:xx.x
Video
Copy the Ubuntu CD to your USB stick
Copy the contents of the Ubuntu installation CD to your USB drive (i.e. all files and directories that are on the installation CD). Please do not copy an ISO image of the installation CD. Note that you don't have to burn the iso to copy it's contents, from linux it can be mounted like so:
Make sure you also copy hidden files and directories (eg. ones with names beginning with a "."). In Gnome, press ctrl-H to see hidden files. In MS Windows you can use the following command, assuming that D: is your CD-ROM drive and F: is the USB drive:
'cp' doesn't copy hidden files, by default, but the following command line works:
Note the /. after the source, and the lack of / after the destination.
Configuring Automounting
To enable or disable automount open a terminal and type:
Browse to org.gnome.desktop.media-handling.
The automount key controls whether to automatically mount media. If set to true, Nautilus will automatically mount media such as user-visible hard disks and removable media on start-up and media insertion.
Another key, org.gnome.desktop.media-handling.automount-open, controls whether to automatically open a folder for automounted media.
If set to true, Nautilus will automatically open a folder when media is automounted. This only applies to media where no known x-content type was detected; for media where a known x-content type is detected, the user configurable action will be taken instead. This can be configured as shown below.
Adjust SYSLINUX.CFG
For recent versions of syslinux, you just need to rename the isolinux directory to syslinux and rename the file isolinux.cfg inside this directory to syslinux.cfg .
Again, for anyone installing Ubuntu 7.04 (Feisty): Just remove the /install/ reference. The only line it is found is kernel /install/mt86plus, which must be changed to kernel mt86plus. -- Boo
no, it is not. there were 23 entries on isolinux.cfg -- capi
I found twenty one, with Feisty, and syslinux 3.51 -- Gedanken
Portable Linux
This will install the LiveCD environment from your install CD onto the USB drive. When you boot from USB, it will show you a GRUB menu with one option in it, which will then take you directly into the LiveCD environment.
You can use this to install Ubuntu onto the computer's hard drive by using the Install icon on the desktop.
Persistence is setup automatically, so it will remember any changes you make between reboots. You can also use the built-in GRUB to launch other disk images, like MS-DOS or memory test. The USB drive has a single normal partition on it, with a casper-rw image and a boot directory for GRUB. You can use the drive normally when not in the Live environment, and access it from the Live environment through a loopback.
Create Mount Point
Next, create a mount point to serve as a destination target directory for USB partition mount. This directory will after we mount the above USB partition contain all files stored your USB drive. Choose any name for your USB mount point directory, e.g., usb-drive .
old kernels workaround
If you encounter problems using your USB device with USB 2 (i.e. 'high speed' mode), you can revert to the 'full speed' mode (slower) by unloading ehci_hcd. To do that, type in a terminal:
before plugging in your device.
General tip
When you encounter problems with USB devices, the first thing to do is to check the latest debug information generated from the kernel just after you plug in your device and/or just after you encounter the problem.
To do that, open a terminal and type :
Check the latest messages; they should be related to your problem.
Mounting the USB stick as /cdrom
This was a bit tricky until I got the hang of it. You need to have the hardware detection detect your hda before you can mount it! But just wait until it complains about a missing CD-ROM, then don't try to helpfully tell it where to look. Just accept the dialog where it says that this stage failed, then switch over to the virtual console and mount -t vfat /dev/hda3 /cdrom. (I skipped the gyrations with /dev/cdroms, they don't seem to be necessary.) Back in the installer, you should now be able to proceed from the next point in the dialog. (Remember, I'm talking about the text-only installer. It might be different in the GTK install.) -- Era
When installing Ubuntu 7.04 (Feisty), there was no need for me to mount the flash. -- Boo
On Partitioning the Flash drive
- I partitioned the disk for installation with room for several boot images. I created hda1 for /boot (in retrospect, maybe not necessary), hda2 for swap (again in retrospect, could go in an extended partition; if I do it again I'll add the good old Woody installer rescue288 disk image -- still viable and valuable as a rescue disk!), hda3 for the Dapper 6.06 server install CD filesystem (this is a low-memory system which can't boot the regular live CD, I have been told), and hda4 as an extended partition for the remaining BIOS hibernation and actual root filesystem partitions.
At this stage, I only marked the installer partition as bootable. It's a FAT16 partition (partition type 06).
Since there is no filesystem yet, the newly created partition needs to be formatted. mkfs -t vfat /dev/sdXY . and be real careful to not format the wrong disk by mistake. (So in my case, this would be sda3 here.)
.. mount with no arguments will tell you what's where, if you're unsure).
Make your USB stick bootable with SYSLINUX
Regarding the IDE disk: When in the USB cradle, the disk is sda, whereas when I mount it in the Libretto as the primary IDE disk, it is of course hda. (I shot myself in the foot a couple of times because of this . )
The automatic mounting is a bit distracting at times. My recommendation would be to pumount any device you intend to do any low-level operations on, and then mount and unmount as root as necessary. -- Era
Make sure to include the -m option with the Windows version of syslinux, to ensure that it copies a fresh ISOLINUX master boot record (MBR.) Otherwise the preexisting MBR may be used, which therefore may not point to your syslinux.cfg file.
Unclean LogFile
If you are mounting drives formatted with NTFS (like most external USB hard disks are), you must first have the ntfs-3g driver installed. This is done automatically in newer versions of Ubuntu. You should also install ntfs-config and enable mounting, which is not done automatically. For ntfs-3g and ntfs-config, see MountingWindowsPartitions.
When a drive is not Safely Removed from a Windows machine (or a forced shutdown occurs from Windows), you may get an error like this when you plug in your drive:
The best option is Choice 1, but you can force the mount by running Choice 2 with sudo. You must then manually unmount it from the terminal (you can't right click the desktop icon):
After that the drive should automount normally again.
Interfering services
Two services/programs responsible for automounting might interfere and thereby prevent a successful automount and permission setting.
Example: Activating the Automount function of Nautilus while using pmount will result in read-only permissions for normal users. Either disable Nautilus' Automount function or deinstall pmount.
Buffer I/O Errors
If you see errors related to Buffer I/O when attaching a USB storage device, there are two ways to work around it. First, try using varying max_sectors settings, as such:
Try values of 120, 64 and 32.
If this does not resolve the issue, then you may need an unusual_dev entry for your device. It would look something like this:
The vendor and device IDs can be obtained from the output of "lsusb". The entry would be placed in drivers/usb/storage/unusual_devs.h. If you cannot compile your own kernel, please file a bug report, and we'll attempt to compile a test module for you.
Comments and Troubleshooting
isotostick.sh (Command-line shell script, runs from Linux)
Warning: Running scripts from untrusted websites is potentially dangerous! Warning: Something's wrong with the script as it wants to use vol_id which was removed in newer versions of Ubuntu. Simply replacing the path by the blkid one won't solve this isse.
Don't forget to replace /dev/sdX1 with the partition name of your USB drive found in the previous section! You will see some "operation not permitted" errors when the script tries to copy the symlinks for /dists/stable and /dists/unstable. This is because fat16 file systems do not handle symlinks, but it will not cause any problems.
Now you can boot from the USB drive and install Ubuntu like as if you had booted from the Desktop CD.
Читайте также: