Troubleshooting Storage Devices Flashcards
Boot Device
- SSD/ HD
- Removeable media CD/DVD
- Over network
Boot Issues
Troubleshooting “Boot Device Not Found” Errors:
When a system cannot locate a bootable device, you may encounter error messages such as:
- “Boot Device Not Found”
- “OS Not Found”
- “Invalid Drive Specification”
Steps to Diagnose and Resolve:
1. Check BIOS/UEFI Settings:
- Access the BIOS/UEFI and verify the boot order to ensure the correct device is set as the first boot priority.
- Confirm that the storage devices (e.g., HDD, SSD) are properly recognized.
2. Inspect Physical Connections:
- If a device is not detected:
- Ensure it is securely connected to the motherboard.
- Check that the device is receiving adequate power.
3. Evaluate Device Status:
- If recognized but still unbootable: The issue may be with the boot sector (e.g., MBR or GPT corruption).
- Check for signs of proper operation:
1. LED activity: Indicates drive activity.
2. For HDDs:
- Sound and movement: Listen for spinning or vibrations to confirm it is powered and operational. (Not applicable for SSDs.)
4. Common Causes:
- Boot order misconfiguration.
- Faulty physical connections or insufficient power.
- Corrupted boot records (MBR/GPT).
Boot Sector
- Is the first area thats going to be read from the UEFI/ BIOS when you’re booting up the system
- Helps system determine what the Partitions are on the stroage device so it can assign drive letters (“C: Drive”) to it and interact with those particitions
MBR
Master Boot Record (MBR): The Master Boot Record is a small, critical piece of data stored in the first sector of a storage device. It contains:
- Partition Information: Details about all partitions on the device.
- Boot Information: The location of the active bootable partition, which holds the boot sector.
How MBR Works:
- System Boot: When the system starts, it reads the first sector of the storage device containing the MBR.
- Partition Scan: The MBR identifies and retrieves information about all partitions.
- Locate Active Partition: It determines the active partition’s boot sector.
- Load Boot Loader: The system moves to the active boot sector to locate and execute the boot loader, which then loads the operating system.
GPT
Globally Unique ID Partition Table (GPT):
The GUID Partition Table is a modern partitioning scheme with several advantages over the Master Boot Record (MBR).
Key Features:
Supports Larger Partitions: GPT allows for significantly larger partitions than MBR.
Flexible Boot Locations: Unlike MBR, GPT does not restrict the boot process to the first sector of the drive. Boot information can be stored on any partition.
Improved Partition Identification: GPT uses unique identifiers for partitions, making them easier to manage.
Modern System Compatibility: Commonly used in systems with UEFI firmware, replacing the limitations of legacy BIOS/MBR setups.
Summary:
GPT provides enhanced flexibility, scalability, and reliability for modern storage devices, making it the preferred choice for newer systems.
Boot Loader
- Windows (Boot Configuration Data (BCD) (Store info about WIndows system and boot it up)
- Linux (GRUB/LILO)
Partition on a storage device
- The logical part of an entire drive (SSD or HD)
- Each part is called a partition
- Taking an entire drive (SSD or HD) and splitting it up into multiple logical parts
- Single partition
- Multiple partitions
- Windows (Single)
- Linux (Multiple)
Format storage devices boot information (Two Types)
- Master Boot Record (MBR)
- GUID Partition Table (GPT)
Troubleshooting a HD
Good
- Low level sound
Bad
- Clicking and grinding (Technical HD and back up immediately)
- Clicking (Usually Issue with read write head)
- Grinding (Read write head is pushing down too far into the platter and scrapping across the platter or could be platter it self and the bearings that allow it to spin are starting to fail
- If files have been fragmented - run a defragmentation tool to put files back together and reduce read/write times
Activity light on a storage device issue
Troubleshooting Storage Device LED Indicators:
- No LED Blinking During Read/Write:
- Indicates potential issues such as:- Faulty connection between the motherboard and storage device (check cables).
- Insufficient power supply to the device.
- Constant LED Blinking:
- Suggests high read/write activity, often caused by insufficient RAM.
- When RAM is low, the system uses the storage device for virtual memory (Page File or Swap Space), increasing storage load. - Solution:
- Add More RAM: Adding physical memory reduces reliance on virtual memory, lowering read/write operations on the storage device.
- This helps improve system performance and extends the lifespan of the storage device.
Missing drive
- disk management to detect
- Check UEFI/ BIOS
- IF not UEFI or Disk management may be mechanical
Read or write failure
- Error message “Cannot read to source disk or cannot write to source disk” (usually means Bad sectors on HDD or bad blocks on SSD
Sectors
HDDs
- Structure of a Hard Drive:
- The round platter of a hard drive is divided into sectors, which are small slices used to store data.
- Data is read/written by identifying the sector, track, and specific location within the track. - Bad Sectors:
- A bad sector is a damaged or corrupted area on the platter that cannot be used for reading or writing.
- Data stored on bad sectors may become unreadable or lost due to corruption. - Handling Bad Sectors:
- Use disk utilities (e.g., Check Disk on Windows or Linux tools) to:- Identify bad sectors.
- Attempt data recovery from damaged areas.
- Reallocate data to functional sectors.
Blocks
SSD
Blocks: small portions on a SSD that we can read and write to.
1. Identifying Bad Blocks:
- SSDs automatically detect bad blocks—areas of storage that can no longer reliably store data.
2. Using Spare Blocks:
- The SSD firmware reallocates data from bad blocks to spare blocks reserved at the end of the drive.
- This process ensures the SSD continues to function normally unless the data in the bad block is already lost or corrupted.
3. Exhaustion of Spare Blocks:
- Over time, the pool of spare blocks may deplete.
- Once exhausted, the SSD can no longer compensate for bad blocks, leading to degraded performance or complete failure.
4. Solution:
- Backup Data Regularly: Ensure critical data is backed up as the drive ages.
- Replace the SSD: When spare blocks are exhausted, it’s time to replace the SSD to avoid data loss.
Best practices
For Troubleshooting storag devices
- Aways have a good backup at all times
at a minimum do a full backup every single weeK
-
