Recently swapped from a ASROCK A320M HDV R4.0 to this new GIGABYTE B550M DS3H. Everything was working fine, and I got a new install of Windows. Now, neither of my old solid state drives are being detected, but they show up in Task Manager. I tried to initialize, and got the "This request cannot be completed because of an I/O device error." The parts worked just fine on a different board 10 minutes before the swap. Any help would be appreciated, thanks. Can call or stream, whatever is needed.
#Disks Unable to be Initialized
1 messages · Page 1 of 1 (latest)
my ssds are being detected by my motherboard and task manager but i cant intialize them, its like they're locked even though they've never been locked before and worked on my other pc 10 mins ago
@tall quartz
NVMe
Do you have another SSD in the new PC that works?
fresh install of windows on an nvme drive
Is it one of the two old ones
no, brand new
yes
Hmm
tried old cables, then put the ones that came with the motherboard on
also tried different SATA slots, neither worked
Are they all named C drive
Windows won't mount them if they all have the same drive letter
you cant put a letter on them until you intialize them
UEFI ..?
I mean your ide controller
Is there data on the old discs that you need?
yes
id like to set them up here without formatting
(and even then i cant format them currently, i dont have the option to)
Can you go to properties, advanced, and check what PIO Only is set to
On the ahci controller
Have you installed all the chipset drivers for the new motherboard?
i don't have advanced
Yeah then I'm thinking the same as osku
ill go look
did that already, sec
That might solve something
well, just grab em all and install, audio, chipset, lan, sata drivers
although the sata driver seems to be just a raid driver
Yeah
the others should be installed at least
put em in a folder, you'll need them later if you end up reinstalling
installed all
Fingers crossed
win 10 or 11?
10
good, the page was for win10 drivers
look like at least the lan driver for 11 is a different file
tried to boot twice, failed both times
geez
a bit worried now to be honest
now neither of the two ssds are showing as boot options when they did previously
yeah that's not great, try again until you get to the repair menu
still in repair
idk what its doing but its taking its sweet ass time but im scared to reboot
💯
Ugh I've had that happen to me a number of times, it's a pain
Trying to fix anything in windows causes 2 more problems
Im tempted to power it off
Inaccessible boot device hrmm.
But I don't want to in case something happens
If you do, go back to bios and check that nvme raid mode is set disabled
What LCD is that
stupid driver install shouldn't change that though..
Imagine tho
Oof
another inaccessible boot device
where would i find this..?
Maybe it's trying to boot from the wrong SSD?
no, only the nvme is accessible to boot from
Hm
settings / io ports / I think
this manual isnt helping me much either
just mentions that there is a setting, pretty much
bro boutta call linus himself
is there a menu called tweaker?
):
settings, under sata configuration?
finally made sense of these paragraphs, although the menu doesn't look the same, probablby different bios version
is the nvme raid mode there as well?
its disabled, yea
well hmm, I guess we hope windows can sort itself out, give it half an hour or something?
and if not, no harm no foul, just another fresh windows install
¯_(ツ)_/¯
I'd start with just the chipset though.. maybe check if there's a bios update available
Can you put this SSD in your old mobo
I did update the bios
and no need to touch the raid drivers
to f16a
Then transfer your files that way
yeah, ill probably end up buying another ssd as well anyways
where would i even move the files to if i cant get the ssds working on this pc
still diagnosing
Oof
no text?
starting to think there might be something off with the motherboard or cpu install, like some pins not connecting.
guess you'll try a new windows install in the morning
probably something to do with the f panel being wrong
i get flashed with "choose os" for 5 seconds before it selects on its own, and then proceeds into "getting ready" for several hours
made it back to windows
ssds still not accessible, its as if they're locked by some FTPM thing
did you ever sort this? lol @shut widget