IMPLEMENTING MASS STORAGE
INSTALL O.S. ONTO A NEW DRIVE.
THAT'S HOW YOU PARTITION & FORMAT a new drive
Example: Windows costs money. "ubuntu" on Linux is open source
**PARTITIONING & FORMATTING
must happen before you use any new mass storage drive!**
.
.
.
.
.
.
.
.
.
RAID LEVELS / FILE STORAGE:
RAID 0 (striping) = 2 drives sharing bits of data from a big file.
SPEEDS THINGS UP
.
RAID 1 (mirroring) = 2 drives share identical bits
via mirroring each other on both drives.
Protects against losing everything. Necessary? It's REDUNDANT. Slows things down
.
RAID 5 (striping w/parity) = uses 3 drives.
First two drives save the old RAID 0 way
but new 3rd drive saves a weird "math parity." clones files via binary math
.
RAID 6 = uses 4 drives.
First two drives save the old RAID 0 way
but new drives make "math parity" clones of file (via binary math)
**Two drives can fail and everything will still be saved**
.
RAID 10 (striping mirrors) = 4 drives with 2 mirrored pairs
(2 on one side keep top half and 2 on the other side keep bottom half)
.
.
.
.
.
.
[] FILE example
_ ^ _ ^
.
.
.
.
.
.
.
.
.
.
Decide or configure "RAID" via hardware & software
Cool companies make "proprietary RAIDS" (sinology) to plug in hundreds of DRIVES and perform crazy combinations of RAID 0 through RAID 0+1
.
.
.
.
.
.
.
.
.
.
HARDWARE RAID
You can tell a motherboard not to treat a cluster of hard drives as AHCI
(regular individual hard drives) but as a "RAID ARRAY" where they all share load.
.
.
.
.
motherboards have their own SYSTEM SETUP
just to tinker with "RAID ARRAYS"
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Troubleshooting MASS STORAGE HARD DRIVES
1. Back stuff up (clouds, thumb drives, etc)
2. Mental re-install?
Re-trace your mental steps of installing the drive and you might remember what you missed.
3. Triple check
.
.
.
.
.
.
.
.
.
.
.
.
Types of errors with MASS STORAGE
.
.
"Read/write failure" - the DRIVE might be at end of its lifespan
S.M.A.R.T. = SMART tech is built into all HDs,
"Slow performance" usually caused by not enough RAM
.
.
"Loud clicking" noise in HD.
TINK TINK sound. Terminal HD death. Replace it, ya dingus
.
.
"Failure to boot" make sure boot order is correct via SYSTEM SETUP
You can also use WIN-RE (windows recovery)
.
.
"DRIVE NOT RECOGNISED"
maybe a formatting problem. just reformat if nothing important is saved on it
.
.
"O.S. not found" 99% certain something fucked up boot order.
Check via SYSTEM SETUP
CORRUPTED OS can cause loads of reboots. Like overheating causes reboots.
"continuous reboots"
COMPTIA EXAM tries to trick you with complicated wording
.
.
"APPEARS TO BE INCORRECT DEVICE" = something fucked up boot order
Check via SYSTEM SETUP
Comments
Post a Comment