Steam Deck
gravity17 2022년 3월 14일 오후 2시 30분
Can anyone help with this please? -- !! /dev/nvme0n1 does not exist -- no nvme drive detected?
I received my Steam Deck today, plugged it in, powered it on, added my wifi and account details. It did an update and rebooted into Steam Deck dashboard, it then prompted me with a BIOS update which completed successfully.

Rebooted back into dashboard, and I proceeded to start formatting my SD card, and was then just looking around the menus. Did not start downloading any games, or playing with any settings - literally just taking a look around.

The screen went black and it looked like it had shut down. I rebooted and was met with a "device not bootable - please restart system" error. Upon restarting I then get a dialog box telling me it cannot boot and press OK to enter set-up.

I then have 4 options:-

1. Reboot
2. Boot Manager
3. Boot from file
4. Settings

Reboot just does the same thing
Boot manager does not show me an NVME drive
Boot from file is empty
Settings work as expected

I download the image from the Steam recovery page and mount it using Rufus. I then use boot manager to boot from the USB stick.

I eventually get into a desktop mode, however when i try to Re-image I get the error:-

!! /dev/nvme0n1 does not exist -- no nvme drive detected?

I checked the partitions using KDE Partition Manager, but all it shows is the USB stick I am booted from and the SD card - no mention of the NVME.

Now to me this seems like the NVME drive is dead/not responding, but as I am not too familiar with Linux I wondered if there is anything else I can try.

There is a terminal with repair tools options, but I am not sure what I need to do in here (or whether there is anything I can do), the options are:-

Reinstallation tools can also be run in a terminal from:
~/tools/repair_device.sh

To mount the Steam Deck partitions directly in a chroot:
~/tools/repair_device.sh chroot

To make the system partitions writeable within the chroot, run:
steamos-readonly disable

When your changes are complete, you can reboot the Steam Deck and disconnect the USB device. To reboot, choose Restart from the Plasma system menu. Or in this terminal:
systemctl reboot

Can any of the above help, or do I just need to wait to hear back from Steam Support?

Thanks in advance!
gravity17 님이 마지막으로 수정; 2022년 3월 14일 오후 2시 40분
< >
전체 댓글 22개 중 1~15개 표시 중
kilésengati 2022년 3월 14일 오후 2시 47분 
It seems like a complex issue, you should contact Steam's support about it.
Yeezy 2022년 5월 21일 오후 3시 13분 
i have the same problem too, sorry it happened to you too but did you get any update on the fix, I'm still trying to resolve mines too
antonio.slara 2022년 7월 22일 오후 2시 10분 
Yeah i got this also... And it sucks. Anyone figured out any solution?
PopinFRESH 2022년 7월 22일 오후 2시 34분 
If you are not feint of heart and are confident in your technical hardware skills, you could try to remove the back cover, disconnect the battery from the mainboard, and remove the heatshield so you can access the M.2 slot. Then try to re-seat the SSD (assuming from the context of your post you have a 256GB or 512GB model). Then boot back into the recovery image and check to see if it is at least seeing the drive. If so proceed with re-imaging it.

Otherwise I'd suggest you contact Valve for an RMA

EDIT: Note there are a plethora of YouTube videos showing how to replace or upgrade the SSD which you can use for reference. You can also reference the iFixit guides.
PopinFRESH 님이 마지막으로 수정; 2022년 7월 22일 오후 2시 35분
gyromancy 2022년 8월 21일 오전 9시 00분 
I have the same issue. Did you make progress with support?
MROOD 2022년 8월 21일 오전 11시 31분 
damn

this looks bad and like a common issue

sucks that they use linux when like 0.1% people know how to use its commands and functions, should of stuck with windows

Send it back for an RMA
JimmyJames26 2022년 8월 21일 오후 7시 56분 
MROOD님이 먼저 게시:
damn

this looks bad and like a common issue

sucks that they use linux when like 0.1% people know how to use its commands and functions, should of stuck with windows

Send it back for an RMA

How did you come to the statistical conclusion that this is a common occurrence and how did you extrapolate that this is specifically a software issue (Linux) and not faulty hardware related?
PopinFRESH 2022년 8월 21일 오후 8시 06분 
JimmyJames26님이 먼저 게시:
MROOD님이 먼저 게시:
damn

this looks bad and like a common issue

sucks that they use linux when like 0.1% people know how to use its commands and functions, should of stuck with windows

Send it back for an RMA

How did you come to the statistical conclusion that this is a common occurrence and how did you extrapolate that this is specifically a software issue (Linux) and not faulty hardware related?

Oh, that's because they clearly live in clown world and have the jester stamp to show for it.

The message in the OP being referenced is the UEFI boot manager. The fact it can't find the NVMe drive its expecting is due to either a hardware failure or the SSD/eMMC isn't seated in the M.2 slot properly. Would have nothing to do with Linux or Windows and Windows would also not work regardless of what fictitious percentage is made up for people familiar with either operating system.
gyromancy 2022년 8월 22일 오전 2시 06분 
Support have been in touch and are arranging for a replacement for me which is great.
retrogunner 2022년 8월 22일 오후 1시 29분 
That sound like a serious issue requiring an RMA or a dealing with replacing the NVMe.

1. The NVMe is bolted down under tension to ensure the pins have a solid contact.

2. Booting to rescue / re-install media, gparted should see all block storage devices via their controllers. If the NVMe is not listed, it's not a properly presented block storage at device level.
- Remember, this is a rescue OS so you've not fiddled with anything.
- no matter how it's partition, you'd see the top-level, raw block storage. If not there, it's not there.

3. Physical hardware fails - even non-moving storage. There could be quality control issues, etc.

If you are operating the device under normal expectations, it should appear & operate as such. To have your NVMe "disappear" just after the first time device initialization (or later on while still under warrantee) and never have been case-cracked open, that's a bad sign.

You should always file a support ticket and be patient. As soon as you file your case, that milestone marks your support even if the day before the end of its manufacturers support.

Keep us posted. Good luck. Cheers, retro
Phitness 2022년 10월 14일 오후 4시 15분 
Anyone ever find a solution to this issue?
BOT Ankou 2022년 11월 20일 오전 10시 14분 
Same case here, the NVMe is recognize in the BIOS, but on the recovery tool and the partition manager, no NVMe found !
Melana Ted 2022년 12월 3일 오후 7시 34분 
Same issue...not even an hour out of the box.
donaldstmaurice 2022년 12월 31일 오후 12시 32분 
same here, thinking there are specific compatiblity issues with some nvme drives

i bought this from ebay:
SSSTC M.2 2230 512GB SSD S990 512GB NVMe PCIe 30MM SSD
JD Ros 2023년 1월 2일 오후 4시 15분 
This happened to me except it's with a WD SN740 2TB that I replaced the 64GB with.

It worked for a bit then went exactly like yours. But my 512GB nvme and 64GB emmc still works.

I tried the same SN740 drive on another steamdeck, it wasn't detected at all. But the drive is still detected on Windows (I'm on a dualboot setup). I think the drive borked itself for linux.
< >
전체 댓글 22개 중 1~15개 표시 중
페이지당 표시 개수: 1530 50

게시된 날짜: 2022년 3월 14일 오후 2시 30분
게시글: 22