I fired up my old Ubuntu system and it asked if I wanted to update. I did. When booting up it gave me the red screen and then just the below screen. The computer is a Dell Inspiron 530 that also has Windows Vista as an alternative boot.  mount: mounting /dev/loop0 on /root failed: Invalid argument 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.21.1 (Ubuntu 1:1.21.0-1ubuntu1) built-in shell(ash)   Enter 'help' for a list of built-in commands.     (initramfs) _
7767
I installed 10.10 a few days ago. The only changes to the default install are the addition of Chrome and Pinta.  It was fine for a few days, then today login etc seemed slow. Likewise it couldn't even render the restart/shutdown menus.  Hoping it was some botched update, I ran the update manager; it tried to install but failed (the UI didn't make it obvious what had failed).  Fine, ok. Shut it down (press enter on the blank shut-down dialog).  Fire it up hoping... And... #fail.  Target filesystem doesn't have requested /sbin/init. No init found. Try passing init= bootarg.   Is it now a brick?     More details:  GRUB 1.98+20100804-5ubuntu3   With  Ubuntu, with Linux 2.6.35-22-generic   Causes  udevadm trigger is not permitted while udev is unxonfigured Giving up waiting for root device.   Or  Ubuntu, with Linux 2.6.35-23-generic   Causes  mount: mounting /dev on /root/dev failed: No such file or directory   Then the same for /sys and /process
72146
After update my system to 15.04, I have an error message at the boot: 'starting build 219'.  The bug is known, its recommend to go to console mode and enter this command:  sudo systemctl enable sddm.service -f   But when I enter this command I get an error message:  Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)
99987
I have been trying to install a fresh copy of Ubuntu 14.04 (64 bit version) on my desktop PC from a USB memory stick, but I'm experiencing a problem.  Each time I attempt an install I received an  "[Errno 5] Input/output error", followed by the following message before the installer exits:  "The installer encountered an error copying files to the hard disk: [Errno 5] Input/output error This is often due to a faulty CD/DVD disk or drive, or a faulty hard disk. It may help to clean the CD/DVD, to burn the CD/DVD at a lower speed, to clean the CD/DVD drive lens (cleaning kits are often available from electronics suppliers), to check whether the hard disk is old and in need of replacement, or to move the system to a cooler environment."  In order to attempt to remedy this I have so far tried installing Ubuntu to two different hard disks, one of which is brand new, and each time I have received the same error "Errno 5" message. I have also tried installing from 3 different USB sticks using torrent and Ubuntu site iso images burned using both Unetbootin and Startup Disk Creator.  Again, these measures have proved fruitless.  The installation process varies depending of the iso I use, with the Ubuntu download page iso exiting at an earlier stage compared to the torrented iso.  The later torrent iso returns an error and exits when I am prompted for my name, computer's ID and password.  I've never experienced anything like this when installing previous versions of Ubuntu.  I'm absolutely stumped!  Does anyone have any more ideas?
73421
These instructions () doesn't work for Ubuntu Server iso. Doing dd if=ubuntuserver.iso of=/dev/sdb doesn't work either. In both situations, after the Ubuntu Server installer boots correctly, it says it hasn't found any CD drive and stops.  I've a USB stick where I've put the content of Ubuntu Server iso on it. I've configured Syslinux (with no APPEND parameter) pointing to vmlinuz+initrd present in "install" folder. The installer boots correctly but it hangs with an error saying it doesn't find the CD-ROM.  If I replace the vmlinuz+initrd with the "hd-media" ones (available ) I get another error: installer can't find any iso file anywhere (which is logical because I don't have any iso, I have the expanded tree on sdb1).  So I can't boot Ubuntu Server 16.04 from a USB stick.
88459
When booting to the graphical desktop fails we sometimes are recommended to boot into a "root shell" or to boot in "recovery mode".  How do I do that?
77616
I try to run Android from SD-card. This card is prepared. There are partitions: boot(FAT32), rootfs(ext4), system(ext4), cache(ext4) and usedata(ext4). Boot partitions has files to run u-boot: MLO, u-boot.bin and uImage. To run it I use commands  mmcinit 0 fatload mmc 0 0x80000000 uImage setenv bootargs 'console=ttyO2,115200n8 mem=456M@0x80000000 mem=512M@0xA0000000 init=/init vram=10M omapfb.vram=0:4M androidboot.console=ttyO2 root=/dev/mmcblk1p2 rw rootwait rootfstype=ext4' bootm 0x80000000   Than I see how Linux starts. But after few seconds on step of loading rootfs I see an error message  [    4.015655] EXT4-fs (mmcblk1p2): couldn't mount RDWR because of unsupported optional features (400) [    4.036499] sd 0:0:0:0: [sda] Attached SCSI removable disk [    4.079986] List of all partitions: [    4.083801] b300        31162368 mmcblk0  driver: mmcblk [    4.089660]   b301             128 mmcblk0p1 f9f21f00-a8d4-5f0e-9746-594869aec34e [    4.097839]   b302             256 mmcblk0p2 f9f21f01-a8d4-5f0e-9746-594869aec34e [    4.106018]   b303             128 mmcblk0p3 f9f21f02-a8d4-5f0e-9746-594869aec34e [    4.114288]   b304           16384 mmcblk0p4 f9f21f03-a8d4-5f0e-9746-594869aec34e [    4.122436]   b305              16 mmcblk0p5 f9f21f04-a8d4-5f0e-9746-594869aec34e [    4.130676]   b306            8192 mmcblk0p6 f9f21f05-a8d4-5f0e-9746-594869aec34e [    4.138916]   b307            8192 mmcblk0p7 f9f21f06-a8d4-5f0e-9746-594869aec34e [    4.147094]   103:00000     524288 mmcblk0p8 f9f21f07-a8d4-5f0e-9746-594869aec34e [    4.155334]   103:00001     262144 mmcblk0p9 f9f21f08-a8d4-5f0e-9746-594869aec34e [    4.163574]   103:00002   30342128 mmcblk0p10 f9f21f09-a8d4-5f0e-9746-594869aec34e [    4.171874] b310            2048 mmcblk0boot1  (driver?) [    4.177734] b308            2048 mmcblk0boot0  (driver?) [    4.183593] b318        15179776 mmcblk1  driver: mmcblk [    4.189453]   b319          102400 mmcblk1p1 00000000-0000-0000-0000-000000000000 [    4.197692]   b31a           10240 mmcblk1p2 00000000-0000-0000-0000-000000000000 [    4.205932]   b31b               1 mmcblk1p3 00000000-0000-0000-0000-000000000000 [    4.214141]   b31d          262144 mmcblk1p5 00000000-0000-0000-0000-000000000000 [    4.222351]   b31e        13228032 mmcblk1p6 00000000-0000-0000-0000-000000000000 [    4.230682]   b31f         1572864 mmcblk1p7 00000000-0000-0000-0000-000000000000 [    4.238891] No filesystem could mount root, tried:  ext4 [    4.244812] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(179,26) [    4.254089] CPU1: stopping   I don't know why it happens.  How can I solve this problem?
87467
A few days ago, I accidentally replaced my desktop in Mint 18 with a virtual console with an errant keystroke. Not having an obvious way to reverse the changes, I logged in and typed exit to exit the console and go back to the desktop. Instead, the computer rebooted, and I lost God-only-knows-how-much unsaved work.  After showing the Mint logo and flashing a message underneath it far too quickly to read, the computer now boots only to a black screen. By pressing esc during reboot, I can get to a Startup Menu. I ran disk checks and memory checks using it, and they all came up clean. None of the other options in this menu help. I have no idea what to do.  The screen is clearly receiving power, and the black screen that it boots to shows a dash or underscore in the top right corner.  How do I get my computer back? It's an HP Pavilion laptop.
9112
I have just set up my new system by creating three partitions on a whole hard disk (/boot, /home, swap and /). I saw  article and now I am getting those errors and the system provide me with some options: (I to ignore, S to skip mounting or M for manual recovery).   I am forced to choose skip mounting because I don't know what manual recovery is. Despite the error I get I think that the system boots okay because I can use the system but this error is very annoying.
49694
I had Ubuntu 14.04 LTS installed on my Laptop. After a while I had some troubles starting it up. I decided to reinstall Ubuntu.  I had 3 ntfs partitions, 2 ext3 partitions the mount point for the first was / and for the second was ./local and a swap partition. During the reinstallation I chose the option: "erase Ubuntu 14.04 and reinstall".  During the reinstallation the power cut off. After it worked again I turned my laptop on to try to restart the installation process. I couldn't find any options other than:   Erase disk and install Ubuntu Something else   When I chose Something else I couldn't see my partitions. Instead I found this:  Device                         Type     Mount point     Format?     Size      Used     System     /dev/mapper/ubuntu--vg-root  /dev/mapper/ubuntu--vg-root   ext4                                 631381 MB unknown  Linux device-mapper (linear)(631.4 GB) /dev/mapper/ubuntu-vg-swap_1  /dev/mapper/ubuntu-vg-swap_1  swap                                 8493 MB   unknown /dev/sda  /dev/sda1                     ext2                                 254 MB    27 MB  /dev/sda5                                                          639877 MB unknown   At the Testdisk phase I have this:
21132
I could use a pointer on fixing the fstab problem to restore earlier working order. I dont have owner in mnt directory and its all snafu. Thank you very much. I tried changing the mount point of a external HDD. Failed. This is the end. mount /dev/sdc  mount: /dev/sdc: can't find in /etc/fstab.  When mounting it with Disks this appears: Error mounting filesystem Error mounting system-managed device /dev/sdc1: unknown filesystem type 'nosuid,nodev,nofail,noauto,x-gvfs-show' (udisks-error-quark, 0) Editing mount options in Disks this appears: Error removing old /etc/fstab entry Didn't find entry to remove (udisks-error-quark, 0) Thank you again.
107472
I had windows &amp; Kali linux (dual boot) then I took off Kali linux Parition so I delete it but I Made a mistake ... and PC won't boot "Rescue grub error" or something ...   but I installed Ubuntu &amp; removed Windows and all .  All is running fine but I just can't open one of my disks , this is the error :   Error mounting /dev/sdb5 at /media/imad/Disque local: Command-line `mount -t "ntfs" -o "uhelper=udisks2,nodev,nosuid,uid=1000,gid=1000,dmask=0077,fmask=0177" "/dev/sdb5" "/media/imad/Disque local"' exited with non-zero exit status 14: The disk contains an unclean file system (0, 0). Metadata kept in Windows cache, refused to mount. Failed to mount '/dev/sdb5': Operation not permitted The NTFS partition is in an unsafe state. Please resume and shutdown Windows fully (no hibernation or fast restarting), or mount the volume read-only with the 'ro' mount option.   I asked this question before but no one had an idea , help please .
108811
This happened when I attempted to upgrade from 17.10 to 18.04.  I receive this error during boot, and my Ubuntu that I've had a few months running without issue twice (not counting during the upgrade) randomly reset to select user and login screen but let me back into my desktop no problem.   During the unpacking part of the update it did this and hung in a select user, type password loop not letting me into the desktop. I turned my computer off twice and on the third try I get a consistent error 256 after selecting Ubuntu from the GRUB menu. My system was at full battery during all these random resets.   How do I fix my system without losing my files? It was only 1/10 or 1/20th unpacked on the update bar. I'm on an Asus with Intel processor/graphics card.
2326
Long story short, I installed ubuntu while I was watching netflix and feeling very lazy, and may have lost all my windows 7 files.  Quick summary:    -Windows 7 was installed on Legacy bios and I installed ubuntu on UEFI bios -ubuntu installer didn't detect any other OS on my computer and wanted to write over the disk, so I had to manually edit the partition    -Despite repeated warnings about partitioning windows in the ubuntu installer, I did this anyway, assigning 140 gigs to ubuntu and 500 to windows Now, my computer won't boot into anything but Ubuntu  -in Gparted, it still shows that I have two partitions, and windows 7 boot loader -However, I can't boot into the non-linux partition, and boot loader says I need a recovery disk.  My question is does anyone know if what I've done is fixable? I'm hoping that I can fix it using the way outlined in this thread:   Thanks for the help everyone!  Note: gparted shows:    Foudn linux image: /boot/vmlinuz - 3.13.0.30 - generic   Found linitrd image: /boot/initrd.img - 3.13.0 - 30 - generic   Found linux image: /boot/vmlinuz - 3.13.0 - 24 generic   Found  initrd image: /boot/initrd.img - 3.13.0 - 24- generic   memtest   memtest   Found windows 7 (loader) on /dev/sda1
52890
When I'm trying to boot my PC from the Xubuntu minimal CD, it fails. It just goes straight to the other operating system, windows vista.  I don't have admin access is that occurring the problem? My computer is really old. It is the 32 bit.  How to solve this problem?
89737
I'm stuck on this screen. I've edited the Ubuntu boot partition while running Windows now Ubuntu does not boot anymore. In depth I have seen a lot of question like this one on here, but what I have not gotten is the replies from the people who have asked about whether the answer has worked or not. Basically tried to boot Ubuntu and it went well. It worked and I installed it something somewhere went wrong and now when I try to boot it. I looked at the other answers that said troubleshoot. So I did it ctrl-alt-1-7 but 1-6 just tells me to log in and runs a whole script than stops unexpectedly and 7 is where it says /dev/mmcblk0p2: clean Booting Ubuntu worked earlier (yesterday) but I trashed a file and then  renamed the file trash 1000 but kept the files so I renamed it ubuntu. Then I tried to restart it up on my Chromebook. It still has old entries from it but I don't know how to delete those to start ALL over. This on Ubuntu 20.04.
5451
I am running an HP pavilion dv6000 dual boot win7 and Ubuntu 12.04. (well, up until today).  After a reboot, the boot process drops to the BusyBox shell and I end up at the prompt:  BusyBox v1.18.5 (Ubuntu 1:1.18.5-1ubuntu4) built-in shell (ash) Enter 'help' for a list of built-in commands.  (initramfs)   I've been researching others who have had this same problem, but haven't been able to find any of those solutions to work for me.  I tried the method described , and after the final command   mount -t ntfs-3g /dev/sda1 /root -o force   it does nothing and gives me another (initramfs) prompt.  I can boot to a live CD (USB) and get to a terminal, but it doesn't seem to do much good, as I can see the /dev/sda1 in the ls command, but it doesn't recognize it when I try to cd to it.  One more question: using the command fdisk -l how can I tell which mount point (sda1/sda2) is my windows partition and which one is Ubuntu?
103592
I removed Windows 7 and installed Ubuntu Server 12.04, but when the computer starts a black screen for Windows Boot Manager appears that looks like this:  Windows Boot Manager   Windows failed to start. A recent hardware or software change might be the cause.   To fix the problem:  &nbsp;&nbsp;1. Insert your Windows installation disc and restart your computer.  &nbsp;&nbsp;2. Choose your language settings, and then click "Next." &nbsp;&nbsp;3. Click "repair your computer."  If you don't have this disc, contact your system administrator or computer manufacturer for assistance.   &nbsp;&nbsp;Status: 0xc0000225  &nbsp;&nbsp;Info: The boot selection failed because a required device is inaccessible.  I want to remove it and I don't know how to do it.