New answers tagged

0

The cause of this fault was found working with the manufacturer, it turned out to be a faulty BIOS revision. We both tested rolling back the BIOS and the problem disappeared. That should have been an early diagnosis step, but live and learn!


1

The accepted answer is wrong. The behaviour you see has nothing to do with Open Firmware and everything to do with yaboot. By default a small script (the "l for Linux, c for CDROM" screen) will be booted (via the tbxi attribute) before yaboot. That scripts blocks if no monitor is connected. The solution is pretty simple, edit the OF variable boot-device to ...


0

in you fstab file add the _netdev flag to the device so the boot process waits for the phyiscal volume to become ready, and retries the mount. so defaults becomes defaults,_netdev and make sure netfs is running on boot too chkconfig netfs on that should do it I hope


1

I've had a similar experience with an Areca 1883i (Firmware V1.53) in a Supermicro server running CentOS 6. The server crashed without reporting any error messages to the terminal while moving a 300GB directory between disk volumes. After a reboot using the power button the RAID controller got stuck at the "Waiting for F/W to become ready" screen. ...


1

I've written a tool that automates this chore, in case it helps anyone else: https://github.com/erichs/bootnukem.


2

This seems to be the root cause of my problems: http://www.heise.de/newsticker/meldung/Windows-7-Update-verhindert-Boot-auf-Asus-Mainboards-3198586.html (Sorry, the article is in german). Interestingly i never saw the red warning which is shown in the articel for some strange reason!?


3

The net.ipv6.ip_nonlocal_bind sysctl was added in kernel 4.3, so if you're running a more bleeding-edge system, you can now solve this problem directly with the sysctl, rather than working around the problem with init script hacks.


1

Seems like you forgot to call grub-install /dev/sda after replication partition table. As a simple workaround you can enter bios and tell it to boot first from /dev/sdb (second disk visible in bios). I suppose it's trying to boot from the first, /dev/sda. The thing is, first bootable partition isn't on md software raid (and it cannot be, because it's used ...


0

Nohup it is I guess: nohup bash_script_wrapper.sh /dev/null 2>&1 &


0

I think you have systemd at your disposal with Ubuntu 16.04 otherwise you can refer to upstart system in which you can write a conf file for your service. In this file you can specify that the service start only after one or more services. I found this article about upstart very useful Digital Ocean - The upstart event system


-2

Boot the system with kernel command line option hpsa.hpsa_allow_any=1 Refer this link for more details: https://www.novell.com/support/kb/doc.php?id=7014067


2

If you've arrived here, chances are you have two services where one depends upon the other but, because they're starting in the wrong order, the one with the dependency is failing to start. Suggestions about editing the symlinks are informative, in terms of illustrating how the startup sequence runs, and would work alright until someone did a "chkconfig on" ...


0

Wednesday 27th Well, I would have liked to find a solution but the server being down for 10 days I decided to upgrade it, deleted all evidences of the crime. Tried first a migration from jessie to testing. It failed. So I finally made a clean install of Debian Testing. No idea where the problem came from but almost sure it came after some update. Several ...


-2

basically it is a hardware error on your machine which is found in case of system can't detect Hard Disk Drive. Anyway you have need to 1. Reinsert HDD once again (both cable data cable as well as power cable). 2.configure 1st boot device Device HDD in boot order & then save it. 3.Check once again in BIOS setup if configuration is changed automatically ...


0

If you suspect an update is causing this issue (an assumption I agree with), here's how I'd trobuleshoot it: Install a fresh copy of Windows 7 on one of those machines. Apply all updates released before April 2016. Confirm the machine is still working; if it isn't, repeat the same process but stop earlier in the update list (f.e. before March 2016). ...


1

Do you recall if any of the updates you installed were a driver update for your mass storage controller? If a new/updated device driver for your mass storage controller is not working as expected, it could prevent Windows from booting off the hard drive. I would do another test. But this time before applying Windows Updates, disable driver updates using ...



Top 50 recent answers are included