Ubuntu Bionic Boot Failure googleapis

I recently updated my laptop that has Ubuntu installed on it to hopefully update it to 18.04 but upon boot I got stuck on something like, “Holding Gnome”, I forget what it was. But now I’m in the recovery mode root console and when I type

apt-get update 

I get

Err:1 https://storage.google.apis.com/bazel-apt stable InRelease    Could not resolve 'storage.google.apis.com' Reading package lists... Done W: Failed to fetch https://storage.googleapis.com/bazels-apt/dists/stable/InRelease Could not resolve 'storage.googleapis.com' W: Some index files failed to download. They have been ignored, or old ones used instead. 

I don’t know what to do from here. I was getting other linux-generic issues but I think I fixed those and now I’m stuck with this one. Any suggestions?

Ubuntu dual boot window 10 dissappear, with only window boot manager in automatic repair

I have tried these solutions and looked for others but they didnt work. 1) Update grub in terminal. 2) Boot repair in usb and select recommended repair

I dont really know what to do to get back my window 10 and I am a total newbie at this. After Boot repair, My GNU grub only shows ubuntu, advanced option for ubuntu, window bootmanager which always lead me to automatic repair failed, and some other window recovery that doesnt work as well.

My window is in /dev/sda3 but I cant find it on my grub.

I can leave my report in boot repair. https://pastebin.com/KGfFK3B1 Hope someone can kindly help me out I would be extremely grateful to you.

Choosing between /dev/sda and /dev/sdb for boot loader installation

I am a Windows 10 user and I would like to try Ubuntu 18.04.3 LTS. I use Windows 10 to my 595 GB disk 0 (C:) and I wish to install Ubuntu on my empty 595 GB disk 1 (D:). My aim is to select which operating system to use on every startup. Therefore, I shrunk disk disk 1 (D:) and created an unallocated 200.20 GB partition in order to install there Ubuntu. I booted into Ubuntu using a USB Ubuntu bootable drive. In the partitions table, I clicked the 214 gb free space, and chose the following partitions for installation (I haven’t made any change yet or proceed to the installation).

/dev/sda   TYPE        SIZE    USED    SYSTEM /dev/sda1  ntfs       209 MB   42 MB  Windows 10 /dev/sda2  ntfs       424 GB  108 MB /dev/sda5  swap         9 GB /dev/sda6  ext4/       20 GB /dev/sda7  ext4/home  185 GB  /dev/sdb /dev/sdb1  ntfs       639 GB  581 GB  /dev/sdb2  ntfs       300 GB  448 MB 

You can see that I partitioned the free space to /dev/sda5, /dev/sda6 and /dev/sda7.


Questions

  1. How can I know which drives are /dev/sda and /deb/sdb? Since Windows 7 is installed on disk 0 (C:) and having used already 543 GB there, while disk 1 (D:) is empty, I suppose that /dev/sdb is disk 0 (C:) and that /dev/sda is disk disk 1 (D:). Is that correct? Furthermore, as the free space which was in disk 1 (D:) became /dev/sda5, /dev/sda6 and /dev/sda7, I assume again that disk 1 (D:) is /dev/sda. Are my thoughts correct?
  2. a) May someone explain to me what is the device for boot loader installation? Do I already have such a device? If so, how can I find which it is?

    b) I must choose to select either /dev/sda or /dev/sdb. The installer defaulted to dev/sda. Does it matter which I choose? Will a wrong choice affect my windows installation or files on disk 0 (C:)? Is it possible that I won’t be able to boot on Windows 10 if I choose wrong?

  3. In the worst case that something goes wrong with the boot loader installation, can I fix that problem booting from my USB bootable drive or I will have to reinstall Windows 10?

Note: There are similar questions here and here. The first link troubles me, the second link doesn’t give details for the boot loader installation, and both links don’t answer all my questions.

Thank you in advance for any help!

Convert unallocated space to usable on a dual boot system

So I have dual booted my 1 TB hard disk with Windows and Ubuntu.

The disk partition looks as following Disk Partition

As you can see there is 326 GB of unallocated space that is not usable. It is an MBR disk so I am aware that the maximum number of partitions can be 4. Current primary partitions run contain the following:

  • Partition 2 /dev/sda2 Windows Filesystem
  • Partition 5 /dev/sda5 Linux Filesystem
  • Partition 6 /dev/sda6 Linux Swap
  • Partition 7 /dev/sda7 Linux Files

Is it possible to make this space usable?

Please link any previously answered questions if this has already been answered.

The output of sudo fdisk -l is

Disk /dev/loop0: 202.9 MiB, 212713472 bytes, 415456 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop1: 320.2 MiB, 335728640 bytes, 655720 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop2: 320.2 MiB, 335794176 bytes, 655848 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop3: 202.3 MiB, 212099072 bytes, 414256 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop4: 181.1 MiB, 189870080 bytes, 370840 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop5: 89 MiB, 93327360 bytes, 182280 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop6: 8.4 MiB, 8839168 bytes, 17264 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop7: 180.2 MiB, 188928000 bytes, 369000 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: dos Disk identifier: 0x6436f9fc  Device     Boot      Start        End   Sectors   Size Id Type /dev/sda1  *          2048    1026047   1024000   500M  7 HPFS/NTFS/exFAT /dev/sda2          1026048  686035516 685009469 326.7G  7 HPFS/NTFS/exFAT /dev/sda3       1323407360 1324374015    966656   472M 27 Hidden NTFS WinRE /dev/sda4       1324378110 1953523711 629145602   300G  5 Extended /dev/sda5       1324378112 1359499263  35121152  16.8G 83 Linux /dev/sda6       1359501312 1375123455  15622144   7.5G 82 Linux swap / Solaris /dev/sda7       1375125504 1953523711 578398208 275.8G 83 Linux  Partition 4 does not start on physical sector boundary.     Disk /dev/loop8: 85 MiB, 89128960 bytes, 174080 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop9: 88.7 MiB, 92983296 bytes, 181608 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop10: 8.4 MiB, 8835072 bytes, 17256 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes   Disk /dev/loop11: 8.6 MiB, 9019392 bytes, 17616 sectors Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes 

Android exploited – elevated privileges – SE Policy exploit – system as root – dual boot – living in my ramdisk. What now? [on hold]

Ive been chipping away at this for days and going in circles so I need to put this out there – somewhere.

My Samsung s9+ hasnt been acting properly for a long time – but in the past few weeks this thing has become a nightmare. Calls and messages come through sometimes days late or apparently days early as the time is changed routinely. The OS is constantly reverting back to some kind of stock image (android pie it is not) with settings completely reset. Weird errors have forced resetting several times and my photos have all been destroyed in random ways (faces altered, photos smudged, scratched out etc). Daily backups have been ignored.

I will attach some of the snide logs this thing generates as well as the init.rc and build.props (fstab goldfish files etc) – im not sure what is handy so i will wait for a response as i have most system documents. These system files and logs that show that adbd is placed in the privileged position pre init – it then discards any update or change installing instead from a hidden partition (or network – the thing is never offline or properly shut down). There it remaps me to a virtual disk and assumes root control of my operating system. I am not sure if it is timed or if there is someone behind it – but as i get close to removing the files (or think i do) it will pretend to brick for an hour or two and then suddenly leap into recovery mode.

Now im not concerned with the causes or what its doing. In its current condition i cant factory reset or erase with odin as it has positioned itself to respond to exactly this threat. Before the setup screen presents this thing has root access and is busy setting tasks and countdowns – similar behaviour is manifesting itself in my PC but i think this exploit has had longer to stretch out on the phone. Can anyone offer any assistance. Its sending me nuts being trapped fixing the damn thing.

Changing boot flag without booting into Ubuntu

So, I have been using Kubuntu and felt the urge to install Ubuntu. I think my computer cannot boot from USB drive so I used Unetbootin (unetbootin.github.io) to do it instead on my harddisk. I could not uninstall or format my /dev/sda3 where Kubuntu was installed as if I did it would remove the Ubuntu I was supposed to install as well. I installed Ubuntu on /dev/sda8 and saw it wasn’t booting, instead Kubuntu was booting so I changed the boot flag to /dev/sda8 and now my computer gives me the message ” Reboot and Select proper Boot device or insert Boot media in selected Boot device and press a key”. I’ll be really grateful if someone could help me as soon as possible.

Ubunt 18.04 & Windows 10 dual boot File corruption on boot/shutdown

So I’ve set up a desktop with Windows 10 and Ubuntu 18.04 (kernel version: 4.15.0-60-generic) for about a month and a half ago. The desktop contains both SSD & HDD, and when installing Ubuntu I divided the root partition / to half of the SSD, and /home partition to half of the HDD. (The computer had W10 before, and the partition space were allocated through W10) The computer also contains a Nvidia GTX1080 Graphic card.

About two weeks ago, the Ubuntu boot crashed and didn’t get past booting phase and went in to rescue mode. I’ve managed to boot it by removing file corruption fsck -y /dev/sdb2 in recovery mode (/dev/sdb2 is my HDD partition).

Since then, every time I reboot/shutdown my computer properly, The file system gets corrupt. It’s either one of the two cases: 1. on reboot it just crashes, and can be booted with the same step as above (fsck in rescue mode). 2. first reboot work, but upon Ubuntu login some files are corrupted. Notably files I’ve modified/created in the last session.

The file corruption seems to be isolated to the HDD only, and have so far not affected the SSD. I’m not sure if the problem is hardware related, if I did some partitioning wrong, or if the dual boot (W10) is causing the problem.

I’ve so far done the following:

  • Extended test with Smartmontools on /dev/sdb, with result “Completed without error”
  • Removed WSL from Windows 10, and checked for ext2fsd in W10 for uninstalling (Based on the solution from this question and this )
  • Removed the Windows partition in HDD from W10 (SSD partition is enough for my use)
  • Checked the output of journalctl -b after each boot. The following error did occur on all of them (but not all of them seems to be related):

kernel: ACPI Exception: AE_BAD_PARAMETER, Could not install PciConfig handler for Root Bridge PCI0 (20170831/evrgnini-245)

kernel: Couldn't get size: 0x800000000000000e

kernel: [drm:intel_bios_init [i915]] *ERROR* Unexpected child device config size 39 (expected 38 for VBT version 221)

gdm3[1565]: GLib: g_variant_new_string: assertion 'string != NULL' failed

Any tips or where I should start looking is appreciated! (and If additional info or terminal output is needed, I’ll add it asap)