Hot answers tagged

76

Obviously, memtest86+ cannot test the memory region which currently contains the memtest86+ executable code (but if there are memory errors in that region, it is very likely that the test itself will crash). However, memtest86+ is able to relocate its own code to a different address at runtime, and by using this trick it is able to test all memory which it ...


5

This definitely should work: $ docker-machine ssh default docker@default:~$ docker run -v /data --name mydata busybox true docker@default:~$ docker run --volumes-from mydata busybox sh -c "echo hello >/data/hello" docker@default:~$ docker run --volumes-from mydata busybox cat /data/hello hello docker@default:~$ exit $ docker-machine restart default ...


5

No, memtest can't test its own memory. However, it is so small (only some KB) that it hardly matters. EDIT: this statement is wrong since, as stated in the selected answer, memtest can dynamically relocate itself to test all user addressable memory. -- In theory, modern processor can, at boot time, configure part of their cache as programmable memory, from ...


4

I don't use boot2docker, but if /data gets wiped on reboot, that's where your volume is being stored (docker run -v /data:/var/lib/mysql), so it will be lost. What you're doing is also combining two different patterns for handling volume persistence. In order to get persistence, containers can mount volumes from a specified location on the host system (...


4

You can list all services and their status with this simple command: service --status-all From the manual: service --status-all runs all init scripts, in alphabetical order, with the status command. The status is [ + ] for running services, [ - ] for stopped services and [ ? ] for services without a 'status' command. This ...


4

for i in `find /etc/rc*.d -name S*`; do basename $i | sed -r 's/^S[0-9]+//'; done | sort | uniq Sample output: acpid anacron avahi-daemon boa bootlogd bootlogs bootmisc.sh checkfs.sh checkroot-bootclean.sh checkroot.sh cryptdisks cryptdisks-early dbus delayed-services hostname.sh hwclock.sh keyboard-setup killprocs kmod lightdm mountall-bootclean.sh ...


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.


3

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" ...


3

sudo systemctl enable docker did the trick.


3

I found the answer to this here: http://unix.stackexchange.com/questions/8409/how-can-i-avoid-run-fsck-manually-messages-while-allowing-experimenting-with-s Apparently, because the system clock is "broken," we have to put broken_system_clock = true in the [options] section of /etc/e2fsck.conf.


3

This bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754218 seems pretty relevant. The user describes a similar issue where his system hangs displaying "A start job is running for LSB: Raise network interfaces" message. They use the following steps to identify the cause of the issue: Enable the debug shell: systemctl enable debug-shell....


2

The server you're describing is an HP ProLiant DL380 G3 from ~2003. That means that you're working with a 12 year-old server, so there's ALWAYS potential for hardware failure with something of that vintage. The positive side is that you have a Integrated Lights-Out (ILO) interface on that server. The ILO will allow you to control the machine and see the ...


2

Use the following command to enable samba: $ sudo systemctl enable smbd.service nmbd.service Synchronizing state for smbd.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d smbd defaults Executing /usr/sbin/update-rc.d smbd enable Synchronizing state for nmbd.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d ...


2

You could mirror the drives with btrfs itself, instead of creating that fs on top of the software raid: mkfs.btrfs -d raid1 /dev/sdc /dev/sdd Otherwise try: umount /dev/md0 if mounted mdadm --stop /dev/md0 mdadm --assemble --scan mv /etc/mdadm/mdadm.conf /etc/mdadm/mdadm.conf.bak /usr/share/mdadm/mkconf > /etc/mdadm/mdadm.conf If ...


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!?


2

Because your boot loader (e.g. grub) won't know how to read from RAID-0 or RAID-5. Where did you find information that grub supports raid0? You should have a small RAID-1 /boot partition. UPDATE: I was wrong. Turns out grub does support raid1 and raid5. However, there's some confusion about what metadata formats it supports, so I guess warning in the ...


1

Boot with the network cable unplugged. Without the server plugged the server will boot without trying to connect with the DNS/DC that is no longer available. Once the server is booted log in with either local credentials or cached domain credentials (if there are any) and edit the network configuration removing reference to any resources that are ...


1

So I finally found some documentation on HPs website that helped me narrow the issue to the Power Distribution board. Apparently there are 12 LEDs on the motherboard. None of them light up. http://h20564.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c01726637#N102BA And this page tells the minimum hardware configuration: http://h20564.www2.hpe.com/...


1

If your machine boots correctly now, I'd move the rescue kernels out of /boot into your home directory (or any other place really) and reboot, make sure it works and then remove them and then rerun yum update. You shouldn't need that many rescue kernels or any if your machine boots correctly Edit: Now, the fun part is if it doesn't boot correctly after ...


1

I met similar situation. but finally I solved it. I tried 2 way. (1) all requires update sudo yum update (2) wait login to finish all initialization on AmazonLinux


1

I will answer my own question. In short: upgrading from GRUB1.99 to GRUB 2.02 beta2 SOLVED the problem. Somehow GRUB's module mdraid1x from GRUB1.99 could not correctly detect RAID when the drives were connected to the new controller. I am not sure what is the exact difference between the SATA controllers. One thing however is that even though neither of ...


1

This ended up on being a long trail with a simple answer. The systems use mdadm to create a level 5 raid pv. Dracut was updated as part of the upgrade from fc21 to fc22 along with the kernel. The intitial boot command line in grub.cfg had a rd.lvm.lv option. This caused the fc22 dracut stop looking for dm arrays early in the boot process. Removing the rd.lvm....


1

Just use bcdedit /bootsequence <guid>. See the following article if you need more details: https://technet.microsoft.com/en-us/magazine/ff700231.aspx


1

PowerShell is your best friend in this case. Create a remote session on the server and get-services - status running would get the same result and can be used on a whole bunch of servers by using Invoke-command Or use the Server Manager application and Connect to the remote server using the correct credentials. There is a section specifically for ...


1

Open up the Services console (services.msc) on your PC using an account that has permissions on the target server (shift+right-click to run as different user). Right-click on the left panel where it says "Services (local)" and input the name of the target server. BAM! There you go.


1

I'll answer this myself, since I've figured out what happened. Turns out HP MicroServer Gen7 servers don't have true hardware RAID. As Michael Hampton's instinct pointed out, the device name looked like a "Fake RAID" device name. The CentOS installer realised this somehow and when I selected the disk that was labelled with "BIOS RAID Set (mirror)", it ...


1

Do you get a POST signal/beep code on boot? Modern motherboards often have a small LCD to display the code. Documentation for the motherboard should list the possible codes. If no -> time to start replacing hardware (typically the motherboard is broken or not powered correctly) If yes, and it is bad -> Debug from there, depending on the code If yes, and ...


1

You need to change the boot order in the BIOS. Depending on your BIOS, this could be in 1 of 2 places. Some will list all drives together, in this case simply move your internal HDD to the top of the list (or at least above the external drive). A different style of BIOS may have one list for internal drives and a separate list for ordering different types ...


1

Set the network filesystems to have the _netdev option in /etc/fstab. UUID=1b4fe7c0-b5fc-4b6d-9c1f /var ext4 defaults 1 2 UUID=b6fcc760-8230-4981-99a6 swap swap defaults 0 0 UUID=a69a5084-247d-4b62-b835 /data xfs noatime,_netdev 1 2 tmp


1

Type: gdm3 into the command line. This should start the gui. If this does not work: login to tty1 apt-get update apt-get upgrade -y apt-get install -f gdm3 UPDATE: I found some more to this workaround which may help you: apt-get install chkconfig chkconfig --level 2 gdm3 gdm3 Now the system should take you to the graphical mode. Other users also ...



Only top voted, non community-wiki answers of a minimum length are eligible