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

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


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.


1

I know that this is a very old question but I just found out that if the server has an SSL certificate in IIS, this might happen. So, removing the IIS SSL certificate would fix it (at least for me). This is based on my on practical experience, and I got the idea from: ...


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



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