ssh – virtmanager: install via netinstall of Debian, restart find the device does not boot, recovery mode can access

I've used virtmanager to create a virtual machine. The installation media is the Debian netinstaller (Version 10, buster). The installation works without problems. Restart failed: no boot device was found. Starting the recovery mode from the uninstaller image: All resources are available, the chroot instance is working properly.

# I used the recovery mode to reinstall grub:
grub-install /dev/sda
update-grub

I was waiting to see the grub dialog box during startup. I found the message "no boot device found"

How to do primary disk Windows, linux secondary alpine linux grub dual boot?

I decided to try to run linux alpine as a desktop system, intrigued by its minimalist nature.

Problem: I have to write grub on the MBR of the Windows disk sda, so that he looks at the / boot on the secondary drive sdb, and can boot Windows or Linux from the menu menu that it finds there. The current start of sda goes directly to Windows, the boot of sdb gives me a menu Grub, but the two options seem to go boot in Linux.

My configuration:

  • Windows 10 is on the main drive, / dev / sda
  • alpine 3.10.1 is on the secondary drive, / dev / sdb; with the / boot directory on the / dev / sdb1 partition.

I did:

# removes default bootloader, I don't think handles different disks
$ apk del syslinux

# install grub, bios version
$ apk add grub grub-bios
$ grub-install /dev/sdb

I have this in my / etc grub 40_custom file:

menuentry 'Windows 10' {
    set root='(hd0,msdos1)'
    chainloader +1
}

I saw some documentation that says do grub-install /dev/sda is installed on the MBR, but I'm worried that grub-install is not limited to that, and overwrites Windows, thinking that there is also a / boot directory to insert its files.

What bothers me is that I have encountered a lot of documents referring to a update-grub2 command, like this: https://wiki.alpinelinux.org/wiki/Installing_Alpine_on_HDD_dualbooting, which is nowhere on my alpine linux installation. I do not have the base either grub order, only grub-* orders. I therefore have the impression that the food has changed since the last time I used it directly (probably 10 years ago, so I'm a bit rusty), or maybe that There is something missing in the Alpine Package.

I probably miss something small because I feel that it is almost there, but not quite.

boot – How to remove screen msgs after the grub2 menu?

After the grub2 step, a black screen is displayed with the texts below. Then, Ubuntu 18.04 starts correctly.

[    0.940493] Couldn't get size: 0x800000000000000e
/dev/nvmen1p3: clean, 300714/1525920 files, 3457087/6103552 blocks
Started bpfilter
[    2.453984] PKCS#7 signature not signed with a trusted key
[    2.568940] PKCS#7 signature not signed with a trusted key
[    2.570752] PKCS#7 signature not signed with a trusted key
[    2.604204] PKCS#7 signature not signed with a trusted key

Questions:

  1. Can I avoid their appearance? If so, how? I've noticed that in grub2,
    ro quiet splash $vt_handoff has already been settled.
  2. I ran e2fsck -p /dev/nvmen1p3 and e2fsck -f /dev/nvmen1p3
    after booting boot disk Ubuntu 18.04 USB. Even after these
    the commands end successfully, the msg /dev/nvmen1p3: clean, 300714/1525920 files, 3457087/6103552 blocks still persist. How
    I solve this problem?
  3. How can I disable the appearance of the line Started bpfilter?
    I found an article about bpfilter here.

Thank you.

I install Open Social on Linux Centos 6 via composer and drush ops, I get a boot message failed

When I try to install the site with drush -y site-install social –db-url = mysql: // root: root @ db: 3306 / social, the bootstrap return failed. In Bootstraphook.php, line 32. Has anybody also encountered this problem? I created the mysql database. Can someone help?

After installing an optical drive in a computer, Ubuntu will not boot.

After installing an optical drive in a computer, Ubuntu will not boot. I receive a black screen, no error message. If I remove the drive it works again. The boot with recovery mode also hangs. Starting recovery

Live Boot Disk Utility

Is it possible to create a bootable version of an operating system (eg Ubuntu) on a USB drive from the Disk Utility. I tried to click restore, and then select an image (.iso). However, every time I run the USB key, it never starts.

lubuntu – Missing boot devices in the BIOS

A month ago, I installed Lubuntu 18.04 on my new Acer a315-21. I've downloaded the .iso, used Rufus to create a bootable USB key, and then installed on my hard drive. Everything worked well until today, when I pressed the F2 key to access the BIOS and find out that the boot priority order is completely empty (that 's all right). that is, that he displayed points). Even with a USB port (iso Puppy Linux etched with Rufus), it does not detect it. How can I boot into USB, and is this normal?

enter the description of the image here

Please note that encryption is enabled, Lubuntu is now at 18.04 and everything is working properly inside Lubuntu (that is, the drive is detected).

16.04 – Blank black screen partly through the boot after replacing the HD

I just replaced the hard disk of my home server with a larger disk, and I am now in a weird state, not enough started. I'm using Ubuntu 16.04 LTS (yeah yeah, I know I need to update).

The procedure I used was as follows:

  1. Run an update.
  2. Restarted to make sure it worked.
  3. To close.
  4. Removal of the old HD hard drive from the server (called "Yemaya").
  5. Put the old and the new HD into a totally different computer (called "Darth").
  6. Started Darth from a live USB key from CloneZilla.
  7. Has a peripheral device clone gone from the old hard drive to the new hard drive?
  8. Darth Farm.
  9. Started Darth on a GParted live USB key.
  10. Developed the partitions on the new hard drive to occupy the available space.
  11. Stop Darth.
  12. Removed both hard drives from Dark.
  13. Put the new HD in Yemaya.
  14. Hung and lit.

It's good:

Photo of the POST-ing system BIOS screen.

It starts to start:

Photo of the system boot.

I allowed the fsck to run; no errors were reported each time I tried it.

Aaaa and at that moment, he moves on to a blank and black screen.

The system is there. If I let it sit for about five minutes, the monitor will eventually lose the signal and start looking for one. But if I press a key on the keyboard, the monitor immediately finds a signal and continues to display an empty black screen. So that answers the keyboard entry.

I tried SSH, but it did not work. I can not ping. All that is wrong is before the network starts.

I can restart it by pressing CTRL + ALT + DEL. When I do it, he shows me the Ubuntu shutdown screen:

Image of the system shutdown.

And then he restarts. I can start it in recovery mode:

System image in recovery mode

I checked dmesgbut it was not interesting to say. All my partitions mounted well. Everything in the recovery mode console seems to work normally.

It's as if it should be a problem with the video driver, but how? I did not touch that! The data on the disk is a bit-by-bit copy of the original. The only thing that changed was the capacity of the disc.

The system is rather old. Equipment:

  • Motherboard: Intel D945GSEJT Johnstown
  • CPU: integrated Atom processor (N270 at 1.333 GhZ, one core, 512 KB – cache)
  • RAM: 2 GB of the fastest card
  • Original HD: Western Digital Scorpio Black WD3200BEKT 320GB 7200 rpm
  • New HD: Western Digital Scorpio Black WD7500BPKT 750GB at 7,200rpm

recovery mode – How to copy / modify data from a Samsung Galaxy S2 progressive boot (GT-I9100)

The Samsung Galaxy S2 (GT-I9100) that I have on hand has been turned off after heating up in standby. When you try to restart it, it was in a bootloop: as usual, it displays "Samsung Galaxy S2 GT-I9100", then the brand of the provider, then "Samsung". But by the time he normally asked for the PIN, he was showing the vendor's brand again and was looping.

It is possible to switch to recovery mode. Among other things (see below), it says "E: Error in /data/log/recovery_log.txt (there is no space left on the device)".

The phone was running the latest firmware (Android 4.1.2). (At least, I'm sure it was the most recent version.)

Can I try to restart it without losing any data? For example, it may not start because the / data partition is full. Is it possible to delete files from this partition when device startup is not possible?

If this is not possible, is it possible to back up all data (including application data and internal "USB" storage) without losing data?

It seems that the installation of a different recovery ROM allows to save the data. However, I read that installing a different recovery on an S2 with a ROM in stock will prevent the system from booting. In this case, it does not start anyway. But if it is possible to solve the problem by freeing space on the / data partition, can the original system be restored?

Some things I've observed might be useful (or not):

Recovery mode says "Android system recovery <3e>"at the top and" # MANUAL MODE # "," – Application of multi-CSC … "," Application of CSC code: DIM "and" Multi-CDC application successfully applied "in the middle, just above the space error output described above.

When it turns on the phone, the provider sends SMS to anyone who tried to call the number while the phone was off. Even if the phone is starting up in a loop, such a notification has been sent.

Boot Css datetimepicker bug Css

	
	$('.datetimepicker').datepicker({}); //Fecha
	
	 $('.datetimepickerH').datetimepicker({format: 'LT'}); //Hora