Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
Search - "diskpart"
-
*Opens devRant*
*sees everybody saying how great Linux is*
*Tries deepin OS*
*Keyboard backlight not working *
*Searches YouTube for a fix*
*Fixes the Backlight*
*Screen resolution set to 800*600 by defualt (monitor 1920*1080)*
*Grub decides there is no need for a windows entry*
*plugs in Windows USB*
*Opens cmd*
*diskpart*
*list disk*
*sel disk 0*
*list vol*
*sel vol 3*
*clean*
*boots into windows*
*Follows a guide to remove grub*
*Learns the lesson*
*Ooh OS X seems nice*
FML23 -
fdisk, cfdisk, diskpart and other tools CAN SUCK MY DICK.
I needed to restore my raspberry pi microsd from 200ish MB back to 16 GB and could find NO WAY of restoring it from my pc. maybe there is some ajbd -asdkasd -adkahdh IUYGFG_&38726283746 sdkfjksjf command that does that but I don't give a shit.
I plugged it into my camera instead. One second and my microsd was restored.
Canon doesn't care about your fancy partitions and other shit, it's just fucking blasting, it is like IN YO FACE. I love it.6 -
I upgraded a PC with an SSD and had to reinstall twice because windows thought it would be a good Idea just to use the boot partition of the old drive instead of creating a new one on the SSD.
I first noticed that something was weird because I could only delete the system and not the boot partition on the old drive using diskpart. I restarted the machine thinking it would help only for the bios to tell me there was no os on the ssd. I tried booting from the old hdd and sure enough, I landed on the desktop of the ssd install.
To resolve that I had to unplug the other drive, reinstall windows and only then I could boot normally.
60mins of my life wasted as I had just finished installing all the software...7 -
Tried to dual boot Arch with Windows yesterday.
Everything was going smoothly. Shrunk the C: partition, ran the installer, installed the OS fine. But it was still booting straight to Windows.
So I edited the BCD to point to Grub instead of Wilndows. Then the plan was to boot into Arch, find Windows, and add it to Grub, problem solved.
Wrong. I had forgotten to disable secure boot. Arch and Grub were booting in BIOS mode, but Windows was UEFI. Grub couldn't boot or even see Windows.
So now I was stuck with just Arch. So I flashed a Windows drive, booted from that, automatic startup repair failed. Opened up the command prompt, tried to rebuild the BCD from there. Surely I can just rebuild it and forget about trying to dual boot right? I just want to get back to being able to use my PC.
Wrong again. Didn't find Windows. Had to get rid of the BCD file before I could rebuild it, but couldn't find it. Found out that I could use diskpart to mount the system partition and assign it a drive letter, renamed the BCD, rebuilt it, and finally was able to reboot into Windows.
Learn from my arrogance. First time Linux users should not attempt to install Arch, let alone do it alongside Windows on the same disk.4 -
Everytime I write clean in diskpart and press enter, I feel like I am pressing the nuclear bomb switch
-
I got a new computer recently. I got it with an evo 970. I tried installing the Samsung controller software so that I can view the health of the drive.
No go. Why?
Looked around and everywhere they are saying turn off raid. I checked in bios. Says my drive is not in a raid volume.
Okay, now what?
Look at manual of laptop maker. Says there is a mode that allows you to use either VMD or RAID on the drive. Apparently I was in VMD mode. I had already backed up the computer at this point. Yes, I suspected this was coming. So I changed the mode.
No boot.
Okay, I have Aomei backup and linux boot disk I made using Aomei. Linux boot disk won't boot... Well fuck.
Luckily I have my old computer and a Windows 10 install disk. I install Windows 10 again, install Aomei and proceed to try and restore.
4 hours later... I dunno how long. I went to bed.
Wake up and test.
No boot.
I try disk repair.
No go.
So I boot into Windows 10 install disk to look at partitions. 5 or 6 fucking partitions. It has installed 3 partitions into the space of one.
Delete all the fucking partitions. Cause fuck you!
Okay, lets try this again.
I make a window pe boot disk this time.
It boots.
I do restore while I am at work.
I get home.
No boot.
Check partitions and find only 2. Better than last time.
I try disk repair.
No go.
Search the net. Literally: "Aomei restore no boot"
Someone says, just assign drive letter with drive C using diskpart.
Seriously?! Disk repair couldn't figure this shit out by context?
Seriously doubting this solution.
Solution works...
Now, I am an engineer/programmer/computer genius. I have been learning how to fix this shit for over 30 years.
How the fuck is Joe Bloe ever going to fix an issue like this? I feel sorry for the technically un-inclined. I honestly don't know how neither Aomei nor Microsoft cannot solve restoring disk images by setting a drive letter. How did this not get backed up by Aomei? How did this not get detected as one of the most common problems with a disk restore? Why has this been a problem with Aomei restore for over 3 years? I love Aomei. It works most of the time. But this is terrible. The tech world is definitely a shit show at this point in time.
I also read that VMD actually makes the communication to the drive a bunch faster. Not sure if the samsung drivers do the same. So there may be a tradeoff. Oh well. I can see the temperature of my drives now! Woot!2 -
So i got another reason to hate windows.
During decrypting bitlocked external hard drive it got disconnected and guess what the partitions didn't showed up in windows and everytime i connected hard drive windows get stuck. I thought the drive and all data of about 300gb is gone. None of the softwares worked (Also tried diskpart to list disks but it got stuck too). After about a week i live booted linux distro and guess what hard drive is working perfectly in linux.
And decryption was also successful without interruption.
Linux never disappoints.2 -
Wasted 8 hours today trying to convince Windows to boot.
Yesterday I deleted two unused partitions. Today no OS booted up. Guess what, diskpart (think parted for Windows) reindexes GPT partitions on any modification. So when I deleted partition #1, my EFI System Partition, previously #2, became #1. But UEFI was still trying to boot from partition #2.
Linux booted after recreating UEFI boot entry. 1 minute job, no tools required. Windows, though... Bootrec /rebuildbcd failed, bcdedit failed, recreating ESP from scratch failed spectacularly. Finally I made a clean install just to get proper ESP and restored OS from backup.
Dammit, Windows. Why do you have to make things that hard.4