Arch Linux

ButteryCrumpet

Member

Registered: 2018-01-16

Posts: 2

[Solved] No such device / Install kernel first after selecting Arch

Booted up today to Arch not booting up throwing an error
no such device 5c83b9da-5f18-43ee-b8a7-5d5447903851
not a recognised filesystem
install kernel first

I can boot into both my windows and ubuntu installations fine as they are on different partitions
Ubuntu's disk manager does not recognise my Arch partition anymore, neither does gparted giving this error:

Unable to detect file system! Possible reasons are:
- The file system is damaged
- The file system is unknown to GParted
- There is no file system available (unformatted)
- The device entry /dev/sdb6 is missing

It doesn't appear in blkid

/dev/sda1: LABEL="Recovery" UUID="5822982922980E5E" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="5ed65451-df91-4e17-a720-dd80de32f76f"
/dev/sda2: LABEL="ESP" UUID="069A-0918" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="d4e30b30-c651-4f25-9603-45040a46f7f5"
/dev/sda4: LABEL="Windows" UUID="C2FE9FADFE9F986D" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="438aca20-6384-44cc-921e-8646c89eb796"
/dev/sda5: UUID="F4BCCFE8BCCFA408" TYPE="ntfs" PARTUUID="0c19aac4-14f0-4787-80d7-26683fe24258"
/dev/sdb1: LABEL="DATA" UUID="0A06A26906A2560B" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="49f6005c-3a12-4409-b215-8b0352b92613"
/dev/sdb2: UUID="9BA7-D923" TYPE="vfat" PARTLABEL="EFI System Partition" PARTUUID="b925aeb5-78c3-4808-8dde-150284cb6392"
/dev/sdb3: LABEL="Push Button Reset" UUID="3E5AA6115AA5C5CD" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="fbb2711c-9e64-4f5a-9be2-9c6a5f55d2c0"
/dev/sdb4: LABEL="Ubuntu" UUID="65252ca1-d422-406d-ac17-46cd76c295fb" TYPE="ext4" PARTUUID="e33fc388-bbaa-4823-b6fd-676734164cb5"
/dev/sdb5: UUID="f05c5de1-b50c-4903-879f-2449c7c44ecf" TYPE="swap" PARTUUID="72d77ad0-89e4-417b-a62f-996824568eda"

But if I sudo blkid the partition I get

/dev/sdb6: PTUUID="9e073b42" PTTYPE="dos" PARTUUID="4660abcc-8a51-4ccf-9e50-cef6f78f98b1"

fdisk -l also shows /dev/sdb6/ partition even with the correct filesytem type

Disk /dev/sdb: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: E5209390-E94B-463B-AB67-0C84217B6AC8

Device          Start        End    Sectors  Size Type
/dev/sdb1        2048 1757450695 1757448648  838G Microsoft basic data
/dev/sdb2  1829378048 1830426623    1048576  512M EFI System
/dev/sdb3  1927258112 1953523711   26265600 12.5G Windows recovery environment
/dev/sdb4  1830426624 1893859327   63432704 30.3G Linux filesystem
/dev/sdb5  1893859328 1927258111   33398784 15.9G Linux swap
/dev/sdb6  1757450696 1829378047   71927352 34.3G Linux filesystem

So it seems to all be there just not mounting correctly on initial boot, it is sitting behind a large NTFS partition which can causes issues but it was fine until suddenly.
Any suggestions? Thanks

Last edited by ButteryCrumpet (2018-01-16 15:22:48)

fsckd

Forum Fellow

Registered: 2009-06-15

Posts: 4,173

Re: [Solved] No such device / Install kernel first after selecting Arch

The type in fdisk is the partition type, not the actual type of filesystem. You will need to fsck the filesystem to check for errors.

Is this a new installation? Have you been able to boot into it before?

---

aur S & M :: forum rules :: Community Ethos
Resources for Women, POC, LGBT*, and allies

ButteryCrumpet

Member

Registered: 2018-01-16

Posts: 2

Re: [Solved] No such device / Install kernel first after selecting Arch

You are right and I am dumb. A quick fsck and it brought it all back to life. Now just to track down what caused it, something always goes wonky if I spend too long in windows...
Thank a lot! Saved my a lot of hassle.