<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Manilka Silini</title>
    <description>The latest articles on DEV Community by Manilka Silini (@zilini).</description>
    <link>https://dev.to/zilini</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4125716%2F94161649-a7d8-47d9-81e7-b13cca0c79cf.jpg</url>
      <title>DEV Community: Manilka Silini</title>
      <link>https://dev.to/zilini</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/zilini"/>
    <language>en</language>
    <item>
      <title>What Happens in Those Few Seconds Between Pressing the Power Button and Seeing the Windows Login Screen?</title>
      <dc:creator>Manilka Silini</dc:creator>
      <pubDate>Thu, 19 Nov 2026 09:18:03 +0000</pubDate>
      <link>https://dev.to/zilini/what-happens-in-those-few-seconds-between-pressing-the-power-button-and-seeing-the-windows-login-9ii</link>
      <guid>https://dev.to/zilini/what-happens-in-those-few-seconds-between-pressing-the-power-button-and-seeing-the-windows-login-9ii</guid>
      <description>&lt;p&gt;As an IT and Networking student, I wanted to break down the exact step-by-step logic of how modern UEFI (Non-CSM) systems boot up, why the FAT32 file system is still essential today, and how to recover when the system fails during the initial hardware check.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 1: Power On &amp;amp; The POST Process
&lt;/h3&gt;

&lt;p&gt;When you press the power button, the CPU immediately reads the &lt;strong&gt;UEFI (Unified Extensible Firmware Interface)&lt;/strong&gt; firmware code stored inside a Flash ROM chip on the motherboard.&lt;/p&gt;

&lt;p&gt;Using this firmware code, the system checks critical hardware components one by one—such as the &lt;strong&gt;RAM, Motherboard, GPU, and Keyboard&lt;/strong&gt;—to ensure everything is functioning properly. This diagnostic phase is called &lt;strong&gt;POST (Power-On Self-Test)&lt;/strong&gt;.&lt;/p&gt;

&lt;h3&gt;
  
  
  🛠️ What If POST Fails? (Step-by-Step Troubleshooting)
&lt;/h3&gt;

&lt;p&gt;If there is a hardware issue, the boot process halts immediately, often leaving you with a completely black screen. Here is how you can troubleshoot and recover a PC or laptop from a POST failure:&lt;/p&gt;

&lt;h4&gt;
  
  
  1. Basic Checks (Start Simple)
&lt;/h4&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Power Drain (Hard Reset):&lt;/strong&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Desktops:&lt;/strong&gt; Unplug the main power cable from the wall/PSU, press and hold the power button for &lt;strong&gt;15–20 seconds&lt;/strong&gt;, then plug it back in and power on.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Laptops:&lt;/strong&gt; Unplug the charger and hold the power button for &lt;strong&gt;30–40 seconds&lt;/strong&gt; to perform an internal power reset without needing to open the back cover to remove a built-in battery. &lt;em&gt;(Some laptops also have a tiny pin-hole reset button underneath—press it with a paperclip for 10 seconds).&lt;/em&gt; This drains trapped static electricity from the motherboard.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Disconnect Peripherals:&lt;/strong&gt; Unplug all external devices (USB flash drives, external hard drives, printers) and try booting again, as a faulty USB device can freeze the POST process.&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  2. Identify the Error Codes
&lt;/h4&gt;

&lt;p&gt;Even when the screen is blank, the motherboard communicates the problem—and you can use Google or AI tools to decode these signals &lt;em&gt;(just remember: tools can help you identify the error, but you need the hands-on skill to fix it!)&lt;/em&gt;:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Beep Codes:&lt;/strong&gt; The motherboard speaker emits specific patterns of short and long beeps (e.g., 1 long beep, 2 short beeps often points to a display/GPU issue).&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Diagnostic LEDs (Desktops):&lt;/strong&gt; Modern motherboards have small status LEDs labeled &lt;code&gt;CPU&lt;/code&gt;, &lt;code&gt;DRAM&lt;/code&gt;, &lt;code&gt;VGA&lt;/code&gt;, and &lt;code&gt;BOOT&lt;/code&gt;. Whichever light stays lit indicates the failing component.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Blink Codes (Laptops):&lt;/strong&gt; Since modern office laptops don't have visible internal motherboard LEDs, they use the Charging LED or &lt;code&gt;Caps Lock&lt;/code&gt; / &lt;code&gt;Num Lock&lt;/code&gt; blinking patterns (e.g., 2 amber blinks followed by 4 white blinks typically indicates a RAM error).&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  3. Reseating Hardware
&lt;/h4&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;RAM Reseating:&lt;/strong&gt; Turn off the power, remove the RAM sticks, gently clean the gold contact pins with a clean rubber eraser or dry cloth, blow out any dust from the RAM slots, and firmly push them back in until they click. If you have two sticks, test booting with just one stick at a time.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Graphics Card &amp;amp; Power Cables:&lt;/strong&gt; If you have a dedicated GPU, remove and reseat it. Also check that the 24-pin motherboard power cable and the 4/8-pin CPU power cable are tightly connected.&lt;/li&gt;
&lt;/ul&gt;

&lt;h4&gt;
  
  
  4. CMOS Reset (Resetting UEFI Settings)
&lt;/h4&gt;

&lt;p&gt;If a POST failure happened right after changing UEFI settings (such as overclocking or setting an unsupported RAM speed), remove the small coin-shaped &lt;strong&gt;CMOS battery (CR2032)&lt;/strong&gt; on the motherboard for about &lt;strong&gt;5 minutes&lt;/strong&gt;, then reinsert it. This resets the UEFI firmware back to factory defaults.&lt;/p&gt;

&lt;h4&gt;
  
  
  5. Hardware Replacement
&lt;/h4&gt;

&lt;p&gt;If the system still fails POST after all these steps, the specific hardware component (RAM, PSU, or Motherboard) is physically faulty and needs to be replaced.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 2: Reading the GPT Partition Table
&lt;/h3&gt;

&lt;p&gt;Once POST succeeds, the UEFI firmware checks your bootable storage device (SSD, HDD, or bootable USB) and reads its &lt;strong&gt;GPT (GUID Partition Table)&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The GPT acts as a partition map. While drive letters like &lt;code&gt;C:&lt;/code&gt; and &lt;code&gt;D:&lt;/code&gt; are only assigned later by Windows, the GPT contains the exact starting and ending &lt;strong&gt;LBA (Logical Block Addressing)&lt;/strong&gt; locations and &lt;strong&gt;Partition Type GUIDs&lt;/strong&gt; for every partition on the drive—including the &lt;strong&gt;EFI System Partition (ESP)&lt;/strong&gt;, Windows OS partition, and Recovery partition.&lt;/p&gt;

&lt;p&gt;During this step, UEFI locates the ESP, which holds the crucial boot files needed to load the operating system.&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 3: Why FAT32 and Not NTFS?
&lt;/h3&gt;

&lt;p&gt;Modern operating systems run on NTFS because it supports advanced features like security permissions, encryption, and journaling. However, the EFI System Partition (ESP) is strictly formatted in &lt;strong&gt;FAT32&lt;/strong&gt;. Why?&lt;/p&gt;

&lt;p&gt;The answer comes down to hardware storage limits:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The UEFI firmware lives on a Flash ROM chip with a very small storage capacity (typically &lt;strong&gt;8MB to 32MB&lt;/strong&gt;).&lt;/li&gt;
&lt;li&gt;NTFS is a complex, proprietary file system. Including full NTFS drivers inside the UEFI firmware would consume too much space on that tiny Flash ROM chip.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;FAT32&lt;/strong&gt; is lightweight, open-standard, and universally supported across operating systems—allowing the UEFI firmware to easily read the partition without running out of chip space.&lt;/li&gt;
&lt;/ul&gt;

&lt;h3&gt;
  
  
  Step 4: Executing the &lt;code&gt;.efi&lt;/code&gt; Bootloader
&lt;/h3&gt;

&lt;p&gt;After reading the GPT map and accessing the FAT32-formatted ESP, the UEFI firmware locates and executes the operating system's bootloader file. On a Windows system, this file is &lt;code&gt;bootmgfw.efi&lt;/code&gt; (Windows Boot Manager).&lt;/p&gt;

&lt;h3&gt;
  
  
  Step 5: Handover to the Windows Kernel (NTFS)
&lt;/h3&gt;

&lt;p&gt;Once &lt;code&gt;bootmgfw.efi&lt;/code&gt; takes control, it loads the necessary NTFS file system drivers into memory. Now that the system can finally read NTFS partitions, the Windows Boot Manager locates the main Windows partition (&lt;code&gt;C:&lt;/code&gt;), loads the Windows Kernel (&lt;code&gt;ntoskrnl.exe&lt;/code&gt;), and hands over full control of the hardware to the operating system.&lt;/p&gt;

&lt;h3&gt;
  
  
  💡 Key Takeaway
&lt;/h3&gt;

&lt;blockquote&gt;
&lt;p&gt;The modern boot process is a clever chain of handoffs: a tiny, lightweight firmware on a Flash ROM chip uses a simple FAT32 partition to launch an &lt;code&gt;.efi&lt;/code&gt; bootloader, which then unlocks the complex NTFS world of your operating system. Understanding this flow not only demystifies how computers start—it gives you the exact roadmap to fix them when they don't!&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h3&gt;
  
  
  🤝 Open to Feedback!
&lt;/h3&gt;

&lt;p&gt;I am currently an IT &amp;amp; Networking student documenting what I learn along the way. If any &lt;strong&gt;Senior Engineers or experienced professionals&lt;/strong&gt; are reading this, I would genuinely appreciate it if you could point out any mistakes, share deeper technical insights, or let me know if I missed anything important in this boot process!&lt;br&gt;
&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frtsj46fjbzr5du63c25b.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Frtsj46fjbzr5du63c25b.jpg" alt=" " width="800" height="450"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>networking</category>
      <category>beginners</category>
      <category>microsoft</category>
      <category>tutorial</category>
    </item>
    <item>
      <title>How I Learned Server Infrastructure Through Logic</title>
      <dc:creator>Manilka Silini</dc:creator>
      <pubDate>Thu, 17 Sep 2026 16:04:50 +0000</pubDate>
      <link>https://dev.to/zilini/how-i-learned-server-infrastructure-through-logic-2gdi</link>
      <guid>https://dev.to/zilini/how-i-learned-server-infrastructure-through-logic-2gdi</guid>
      <description>&lt;p&gt;As I dive deeper into System Administration and DevSecOps, I decided to take a step back and analyze how Servers, Virtualization, and Operating Systems &lt;em&gt;actually&lt;/em&gt; work. &lt;/p&gt;

&lt;p&gt;Instead of just memorizing textbook definitions, I wanted to argue with the concepts. I wanted to ask &lt;strong&gt;"Why?"&lt;/strong&gt; &lt;/p&gt;

&lt;p&gt;Here is the fundamental logic I understood by questioning the basics.&lt;/p&gt;




&lt;h2&gt;
  
  
  1. The Physical Server Approach (Bare-Metal)
&lt;/h2&gt;

&lt;p&gt;At first glance, buying brand-new physical hardware seems like the absolute best option. Since the hardware connects directly to the Operating System, you get maximum, raw performance (for example, fully utilizing direct GPU power). &lt;/p&gt;

&lt;p&gt;But that raised a big question for me. &lt;/p&gt;

&lt;p&gt;Even if we buy a massively powerful server, if our application only uses 15% of the CPU capacity, the remaining 85% is just sitting there wasting electricity and money. &lt;/p&gt;

&lt;p&gt;&lt;strong&gt;The Single Point of Failure:&lt;/strong&gt; &lt;br&gt;
If we decide to save money by putting multiple systems on that single physical server, we create a massive risk. If a hardware fault occurs—or if the server gets hacked—the entire company goes offline instantly.&lt;/p&gt;




&lt;h2&gt;
  
  
  2. The Shift to Virtual Machines &amp;amp; Hypervisors
&lt;/h2&gt;

&lt;p&gt;This exact problem led me to Virtual Machines (VMs) and Hypervisors. But that raised another question: &lt;em&gt;If virtualization is the answer, does it mean we don't need physical hardware anymore?&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;Not at all. A VM is not a replacement for physical hardware; it is a smart way to logically divide and utilize physical hardware. We still absolutely need physical RAM, CPUs, and PCIe bandwidth.&lt;/p&gt;

&lt;p&gt;Instead of installing Windows or Linux directly on the bare metal, we install a &lt;strong&gt;Hypervisor&lt;/strong&gt; (like VMware or Hyper-V). &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;The Hypervisor acts as a "Manager." &lt;/li&gt;
&lt;li&gt;It allows us to run 3 completely isolated virtual servers inside one physical machine. &lt;/li&gt;
&lt;li&gt;Suddenly, hardware utilization jumps from 15% to 80%+. &lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Bonus:&lt;/strong&gt; Because of isolation, even if the Web VM gets hacked, the Database VM remains completely safe.&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  3. "If GUIs are so User-Friendly, why do Servers still use CLI?"
&lt;/h2&gt;

&lt;p&gt;For someone used to modern desktop operating systems, going back to a black screen (CLI) feels like a step backward. But questioning OS history and security revealed two critical reasons:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Resource Overhead:&lt;/strong&gt; GUIs exist for human convenience, but rendering graphics wastes massive amounts of RAM and CPU. Servers don't need pretty interfaces; they need &lt;strong&gt;maximum performance and automation&lt;/strong&gt;. &lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Security &amp;amp; Attack Surface:&lt;/strong&gt; From a DevSecOps perspective, a GUI introduces hundreds of extra background packages, drivers, and dependencies. More code directly translates to a larger &lt;strong&gt;Attack Surface&lt;/strong&gt; with more potential vulnerabilities. A headless CLI server stays lightweight, highly secure, and much easier to patch.&lt;/li&gt;
&lt;/ul&gt;




&lt;h3&gt;
  
  
  Final Thoughts
&lt;/h3&gt;

&lt;p&gt;Learning technology isn't about memorization. It’s about understanding the problems of the past to appreciate the solutions of the present.&lt;/p&gt;




&lt;h3&gt;
  
  
  🗣️ Over to You!
&lt;/h3&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;To the Senior SysAdmins &amp;amp; DevSecOps Engineers:&lt;/strong&gt; What production realities, edge cases, or nuances did I miss in my breakdown? I'd love to learn from your real-world experience!&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;To fellow learners:&lt;/strong&gt; What was your biggest "aha!" moment when learning server architecture?&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Let’s discuss in the comments below!&lt;/p&gt;

</description>
      <category>beginners</category>
      <category>networking</category>
      <category>sysadmin</category>
      <category>virtualization</category>
    </item>
  </channel>
</rss>
