New answers tagged boot
When upgrading kernel, always have at least one known-good kernel (meaning a kernel that you have already succesfuly booted). As long as you have access to the console, so you can manually switch to this known-good, its fine to change the default kernel to your newly installed. If you do not have access to the console, you probably should use grub's ...
A workaround is to edit /etc/fstab to use the _netdev mount option. From mount man page: _netdev The filesystem resides on a device that requires network access (used to prevent the system from attempting to mount these filesystems until the network has been enabled on the system). Other possibilities are to use the ...
Instead of doing it manually, like suggested in the other answers, you could also change the init script. Just add such a line to the header: # chkconfig: 35 90 10 This will instruct chkconfig to add the service to the runlevels 3 and 5, with a start position of 90 and a kill position of 10.
Not sure if you have RAID or something there, but I think your problem is caused due to the fact that the disk with boot records is on a different position now, and the BIOS is trying to boot from the former position. Either re-swap the disk like they where before, or change your Boot Order Settings at BIOS. Maybe you disks are not correctly plugged in, ...
Yes. Windows Server 2008 R2 and newer has a technology that specifically works this way. It's called Direct Access. It's easier to setup in most network architectures under Server 2012. The client must be Windows 7 Enterprise or Ultimate, or Windows 8 Enterprise. It uses IPSec and HTTPS; it works based on the machine containing a cert from your domain, and ...
Boot to just a command line by adding init=/bin/bash to the kernel arguments in the boot loader. Open a shell in a new VT by typing openvt -- /bin/bash Continue the original boot sequence by typing exec /sbin/init in the first bash shell. Once the boot sequence stall you can switch to the shell opened by openvt and start collecting information about the ...
Setting the permission of / to 755 worked for me. So check first with root@ubuntu:/# cd / root@ubuntu:/# ls -ld Permissions should be "drwxr-xr-x" (755).
You can use qemu to test your initramfs files. qemu-kvm -kernel /boot/vmlinuz-3.19.3-200.fc21.x86_64 \ -initrd /boot/initramfs-3.19.3-200.fc21.x86_64.img \ -hda foo The system will obviously fail to boot since the hda option points to a dummy file. It should be enough to prove that an initramfs is bootable, though. Provide a valid qcow image if in ...
I use this utility: chkdskall You can use chkdsk in a batch file by echoing the Y and piping it to chkdsk as follows: echo Y | chkdsk c: /f
Top 50 recent answers are included