Error device `...` not found. Skipping fsck.

ThElitEyeS · 2014-03-25 12:01:27

Hey guys, when i try to boot arch while that device is attached:
I receive the following error:
Is there anyway to fix it ?

fstab

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/sdb2
UUID=8da5f695-2e59-4b20-ae82-218bb927846e	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/sdb4
UUID=d2e6aa46-e8d4-4a25-ab1a-321cf15092ec	/home     	ext4      	rw,relatime,data=ordered	0 2

# /dev/sdb3
UUID=80c1a8b8-2a3c-498c-90c1-c75e8ebe591a	none      	swap      	defaults  	0 0

Last edited by ThElitEyeS (2017-10-03 20:17:53)

WorMzy · 2014-03-25 12:09:33

Please change your images to links.

Why have you highlighted sdc in your first image? Are you trying to say that when you attach it, Arch cannot boot? If that is the case, I would guess that your BIOS prioritises removable media over HDDs, and your removable device has an incorrectly configured boot loader installed on it.

The solution to that would be to change your boot order in your BIOS (and optionally fix your removable device's bootloader).

Kartious · 2014-03-25 12:10:54

Are these all internal drives that you are using? Can you check Fstab?

Agree WorMzy his post is very vague on what the actual problem is

Last edited by Kartious (2014-03-25 12:12:52)

karol · 2014-03-25 12:31:53

WorMzy wrote:

Please change your images to links.

Fix these too https://bbs.archlinux.org/viewtopic.php?id=179038
https://wiki.archlinux.org/index.php/Fo … s_and_Code

ThElitEyeS · 2014-03-25 12:38:27

Kartious wrote:

Are these all internal drives that you are using? Can you check Fstab?
Agree WorMzy his post is very vague on what the actual problem is

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/sdb2
UUID=8da5f695-2e59-4b20-ae82-218bb927846e	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/sdb4
UUID=d2e6aa46-e8d4-4a25-ab1a-321cf15092ec	/home     	ext4      	rw,relatime,data=ordered	0 2

# /dev/sdb3
UUID=80c1a8b8-2a3c-498c-90c1-c75e8ebe591a	none      	swap      	defaults  	0 0

Last edited by ThElitEyeS (2014-03-25 12:42:58)

karol · 2014-03-25 12:39:47

When posting configs, code or command output, please use [ code ] tags https://bbs.archlinux.org/help.php#bbcode

like this

It makes the code more readable and - in case of longer listings - more convenient to scroll through.

Please read the Wiki forum rules before posting again.

WorMzy · 2014-03-25 13:00:38

When you changed the images, it looks like you broke the urls, they no longer work for me. However, you weren't getting past the initrd, so ignore fstab for now, the problem is related to your bootloader(s).

Edit: ignore this, your rootfs is mounted, so you're out of the initrd.

Edit edit: Your rootfs isn't mounted, I'm just confused.

Last edited by WorMzy (2014-03-26 10:50:13)

Kartious · 2014-03-25 13:00:47

WorMzy wrote:

Please change your images to links.
Why have you highlighted sdc in your first image? Are you trying to say that when you attach it, Arch cannot boot? If that is the case, I would guess that your BIOS prioritises removable media over HDDs, and your removable device has an incorrectly configured boot loader installed on it.
The solution to that would be to change your boot order in your BIOS (and optionally fix your removable device's bootloader).

ThElitEyeS wrote:

Kartious wrote:

Are these all internal drives that you are using? Can you check Fstab?
Agree WorMzy his post is very vague on what the actual problem is

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/sdb2
UUID=8da5f695-2e59-4b20-ae82-218bb927846e	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/sdb4
UUID=d2e6aa46-e8d4-4a25-ab1a-321cf15092ec	/home     	ext4      	rw,relatime,data=ordered	0 2

# /dev/sdb3
UUID=80c1a8b8-2a3c-498c-90c1-c75e8ebe591a	none      	swap      	defaults  	0 0

You was clearly asked a few questions while trying to help you, just blindly ignoring them and giving vague responses is considered rude.

When you answer the questions given to you we can then make progress with your issue

Last edited by Kartious (2014-03-25 13:01:11)

karol · 2014-03-25 13:28:32

WorMzy wrote:

When you changed the images, it looks like you broke the urls, they no longer work for me..

+1

Firefox can't find the server at s27.posturl.org.

Run

lsblk -f

to get the UUIDs.

ThElitEyeS · 2014-03-25 15:06:53

WorMzy wrote:

Please change your images to links.
Why have you highlighted sdc in your first image? Are you trying to say that when you attach it, Arch cannot boot? If that is the case, I would guess that your BIOS prioritises removable media over HDDs, and your removable device has an incorrectly configured boot loader installed on it.
The solution to that would be to change your boot order in your BIOS (and optionally fix your removable device's bootloader).

I have highlighted is because its the one who cause the problem.
Before i boot i remove it, if it is attached i can't boot the error in the screenshot above will appear

The solution to that would be to change your boot order in your BIOS (and optionally fix your removable device's bootloader).

I choose to boot the arch linux device from boot menu.
I don't know what do you mean by this part.
and optionally fix your removable device's bootloader

Last edited by ThElitEyeS (2014-03-25 15:08:54)

ThElitEyeS · 2014-03-25 15:10:30

Kartious wrote:

WorMzy wrote:
Please change your images to links.
Why have you highlighted sdc in your first image? Are you trying to say that when you attach it, Arch cannot boot? If that is the case, I would guess that your BIOS prioritises removable media over HDDs, and your removable device has an incorrectly configured boot loader installed on it.
The solution to that would be to change your boot order in your BIOS (and optionally fix your removable device's bootloader).
ThElitEyeS wrote:
Kartious wrote:
Are these all internal drives that you are using? Can you check Fstab?
Agree WorMzy his post is very vague on what the actual problem is
# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/sdb2
UUID=8da5f695-2e59-4b20-ae82-218bb927846e	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/sdb4
UUID=d2e6aa46-e8d4-4a25-ab1a-321cf15092ec	/home     	ext4      	rw,relatime,data=ordered	0 2

# /dev/sdb3
UUID=80c1a8b8-2a3c-498c-90c1-c75e8ebe591a	none      	swap      	defaults  	0 0
You was clearly asked a few questions while trying to help you, just blindly ignoring them and giving vague responses is considered rude.
When you answer the questions given to you we can then make progress with your issue

Sorry brother i was on rush, you want fstab content right?
excuse my, my english is not that good if you meant another thing tell me

ThElitEyeS · 2014-03-25 15:12:08

karol wrote:

WorMzy wrote:
When you changed the images, it looks like you broke the urls, they no longer work for me..
+1
Firefox can't find the server at s27.posturl.org.
Run
lsblk -f
to get the UUIDs.

Fixed the Images.

[x@x ~]$ lsblk -f
NAME   FSTYPE LABEL           UUID                                 MOUNTPOINT
sda                                                                
├─sda1 ntfs   System Reserved 460EC7C90EC7B06B                     
└─sda2 ntfs                   04F4CAF3F4CAE5D0                     
sdb                                                                
├─sdb1                                                             
├─sdb2 ext4   root            8da5f695-2e59-4b20-ae82-218bb927846e /
├─sdb3 swap                   80c1a8b8-2a3c-498c-90c1-c75e8ebe591a [SWAP]
└─sdb4 ext4                   d2e6aa46-e8d4-4a25-ab1a-321cf15092ec /home
sdc                                                                
├─sdc1 ntfs   x x    D4B4D9A9B4D98E7C                     /run/media/x/x x
└─sdc4 udf    GParted-live    2014-02-20-09-30-51-00               
[x@x ~]$

Last edited by ThElitEyeS (2017-10-03 20:17:11)

karol · 2014-03-25 15:24:43

Can you boot with a different device attached to that post? Is it a USB3 post?
What is your hardware, you motherboard, what computer is it?

ThElitEyeS · 2014-03-25 15:34:19

karol wrote:

Can you boot with a different device attached to that post? Is it a USB3 post?
What is your hardware, you motherboard, what computer is it?

Yeah it is USB 3 and yes i can boot

EDIT: It happened again with SSD on sata 3

description: Desktop Computer
    product: MS-7818 (To be filled by O.E.M.)
       description: Motherboard
       product: Z87 MPOWER (MS-7818)
       vendor: MSI
       physical id: 0
       version: 1.0
       serial: To be filled by O.E.M.
       slot: To be filled by O.E.M.
     *-firmware
          description: BIOS
          vendor: American Megatrends Inc.
          physical id: 0
          version: V1.5
          date: 08/16/2013
          size: 64KiB
          capacity: 8128KiB

Last edited by ThElitEyeS (2017-10-03 20:18:21)

WorMzy · 2014-03-25 16:41:01

At the rootfs prompt seen in your second image, can you run, and post the output of:

uname -a
pacman -Q linux
systemctl status systemd-udevd
ls -l /dev/disk/by-uuid

ThElitEyeS · 2014-03-26 05:06:37

WorMzy wrote:

At the rootfs prompt seen in your second image, can you run, and post the output of:
uname -a
pacman -Q linux
systemctl status systemd-udevd
ls -l /dev/disk/by-uuid

This time the error is caused by SSD on sata 3 if i am not wrong

[root@z z]# lsblk -f
NAME   FSTYPE   LABEL          UUID                                   MOUNTPOINT
sda                                                                   
├─sda1 ext2                    e5535046-c4e1-481d-8152-865ab8d20047   
├─sda2                                                                
└─sda5 LVM2_mem                yJ9RLW-lMUM-SZg8-MA6N-0oRl-QlwN-bmtNhI 
  ├─ubuntu--vg-root
       ext4                    378de77b-0ec4-4c04-9998-26ddded5c3fc   
  └─ubuntu--vg-swap_1
       swap                    41c23045-3622-4227-93cb-8cf19a54061d   
sdb                                                                   
├─sdb1 ntfs     System Reserved
                               460EC7C90EC7B06B                       
└─sdb2 ntfs                    04F4CAF3F4CAE5D0                       
sdc                                                                   
├─sdc1                                                                
├─sdc2 ext4     root           8da5f695-2e59-4b20-ae82-218bb927846e   /
├─sdc3 swap                    80c1a8b8-2a3c-498c-90c1-c75e8ebe591a   [SWAP]
└─sdc4 ext4                    d2e6aa46-e8d4-4a25-ab1a-321cf15092ec   /home
sdd                                                                   
├─sdd1 ntfs     z z   D4B4D9A9B4D98E7C                       
└─sdd4 udf      GParted-live   2014-02-20-09-30-51-00                 
[root@z z]#

fstab

# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/sdb2
UUID=8da5f695-2e59-4b20-ae82-218bb927846e	/         	ext4      	rw,relatime,data=ordered	0 1

# /dev/sdb4
UUID=d2e6aa46-e8d4-4a25-ab1a-321cf15092ec	/home     	ext4      	rw,relatime,data=ordered	0 2

# /dev/sdb3
UUID=80c1a8b8-2a3c-498c-90c1-c75e8ebe591a	none      	swap      	defaults  	0 0

Last edited by ThElitEyeS (2017-10-03 20:17:36)

jasonwryan · 2014-03-26 05:13:58

The fix for this is in post #2:

WorMzy wrote:

I would guess that your BIOS prioritises removable media over HDDs, and your removable device has an incorrectly configured boot loader installed on it.
The solution to that would be to change your boot order in your BIOS (and optionally fix your removable device's bootloader).

ThElitEyeS · 2014-03-26 09:34:53

jasonwryan wrote:

The fix for this is in post #2:
WorMzy wrote:
I would guess that your BIOS prioritises removable media over HDDs, and your removable device has an incorrectly configured boot loader installed on it.
The solution to that would be to change your boot order in your BIOS (and optionally fix your removable device's bootloader).

If i wait a minute then i write exit it will continue normally

WorMzy · 2014-03-26 10:20:32

I suspect that you are using /dev/sd# syntax in your bootloader's configuration, which is causing the wrong filesystem to be mounted initially when the device order is altered. That would explain why you can't run pacman from the rootfs prompt, though I don't know why you're not getting the "rootfs mounted, but /sbin/init does not exist" message that normally goes hand-in-hand with that situation.

It also seems like your HDD is slow to appear when you have a removable device inserted. I don't know why this is.

You, personally, seem hung up on the cache mode messages, ignore these, they are nothing to worry about: https://bbs.archlinux.org/viewtopic.php?id=162471

From the rootfs prompt again, could you post the output of

cat /proc/cmdline
mount
ls /

ThElitEyeS · 2014-03-26 10:32:48

WorMzy wrote:

I suspect that you are using /dev/sd# syntax in your bootloader's configuration, which is causing the wrong filesystem to be mounted initially when the device order is altered. That would explain why you can't run pacman from the rootfs prompt, though I don't know why you're not getting the "rootfs mounted, but /sbin/init does not exist" message that normally goes hand-in-hand with that situation.
It also seems like your HDD is slow to appear when you have a removable device inserted. I don't know why this is.
You, personally, seem hung up on the cache mode messages, ignore these, they are nothing to worry about: https://bbs.archlinux.org/viewtopic.php?id=162471
From the rootfs prompt again, could you post the output of
cat /proc/cmdline
mount
ls /

ThElitEyeS · 2014-03-26 10:39:32

Also i made arch to boot first

WorMzy · 2014-03-26 11:04:20

Looks like I was wrong about your root partition being mounted, you're still in the initrd.

Also i made arch to boot first

So Arch is on the removable device?

I'm not sure if jasonwryan has seen something that confirmed my earlier theory, but it looks like your boot arguments and kernel are fine, so I now think the problem is either a BIOS bug (which may be solved with a BIOS update from your motherboard's manufacturer), or a udev bug (which is unlikely, but not impossible). You might be able to work around it in the meantime by adding rootdelay=50 to your kernel parameters, to give the device more time to show up before the initrd gives up.

Regarding your PM, no, I don't have Skype.

ThElitEyeS · 2014-03-26 11:07:00

WorMzy wrote:

Looks like I was wrong about your root partition being mounted, you're still in the initrd.
Also i made arch to boot first
So Arch is on the removable device?
I'm not sure if jasonwryan has seen something that confirmed my earlier theory, but it looks like your boot arguments and kernel are fine, so I now think the problem is either a BIOS bug (which may be solved with a BIOS update from your motherboard's manufacturer), or a udev bug (which is unlikely, but not impossible). You might be able to work around it in the meantime by adding rootdelay=50 to your kernel parameters, to give the device more time to show up before the initrd gives up.
Regarding your PM, no, I don't have Skype.

Yeah arch is on USB 3 flash memory [240GB]
i executed this in the terminal rootdelay=50 .
Do you have any idea about this ?
https://bbs.archlinux.org/viewtopic.php?id=179092

Last edited by ThElitEyeS (2014-03-26 11:08:45)

WorMzy · 2014-03-26 11:20:57

ThElitEyeS wrote:

i executed this in the terminal rootdelay=50 .

You misunderstood, it's not a command, its a kernel command line parameter, it needs to be added to your kernel line in your boot loader. See https://wiki.archlinux.org/index.php/Kernel_parameters

ThElitEyeS wrote:

Do you have any idea about this ?
https://bbs.archlinux.org/viewtopic.php?id=179092

No.

ThElitEyeS · 2014-03-26 11:22:55

WorMzy wrote:

ThElitEyeS wrote:
i executed this in the terminal rootdelay=50 .
You misunderstood, it's not a command, its a kernel command line parameter, it needs to be added to your kernel line in your boot loader. See https://wiki.archlinux.org/index.php/Kernel_parameters
ThElitEyeS wrote:
Do you have any idea about this ?
https://bbs.archlinux.org/viewtopic.php?id=179092
No.

Alright sorry for annoying & thanks for you support

Last edited by ThElitEyeS (2014-03-26 11:23:11)

Arch Linux

#1 2014-03-25 12:01:27

Error device `...` not found. Skipping fsck.

#2 2014-03-25 12:09:33

Re: Error device `...` not found. Skipping fsck.

#3 2014-03-25 12:10:54

Re: Error device `...` not found. Skipping fsck.

#4 2014-03-25 12:31:53

Re: Error device `...` not found. Skipping fsck.

#5 2014-03-25 12:38:27

Re: Error device `...` not found. Skipping fsck.

#6 2014-03-25 12:39:47

Re: Error device `...` not found. Skipping fsck.

#7 2014-03-25 13:00:38

Re: Error device `...` not found. Skipping fsck.

#8 2014-03-25 13:00:47

Re: Error device `...` not found. Skipping fsck.

#9 2014-03-25 13:28:32

Re: Error device `...` not found. Skipping fsck.

#10 2014-03-25 15:06:53

Re: Error device `...` not found. Skipping fsck.

#11 2014-03-25 15:10:30

Re: Error device `...` not found. Skipping fsck.

#12 2014-03-25 15:12:08

Re: Error device `...` not found. Skipping fsck.

#13 2014-03-25 15:24:43

Re: Error device `...` not found. Skipping fsck.

#14 2014-03-25 15:34:19

Re: Error device `...` not found. Skipping fsck.

#15 2014-03-25 16:41:01

Re: Error device `...` not found. Skipping fsck.

#16 2014-03-26 05:06:37

Re: Error device `...` not found. Skipping fsck.

#17 2014-03-26 05:13:58

Re: Error device `...` not found. Skipping fsck.

#18 2014-03-26 09:34:53

Re: Error device `...` not found. Skipping fsck.

#19 2014-03-26 10:20:32

Re: Error device `...` not found. Skipping fsck.

#20 2014-03-26 10:32:48

Re: Error device `...` not found. Skipping fsck.

#21 2014-03-26 10:39:32

Re: Error device `...` not found. Skipping fsck.

#22 2014-03-26 11:04:20

Re: Error device `...` not found. Skipping fsck.

#23 2014-03-26 11:07:00

Re: Error device `...` not found. Skipping fsck.

#24 2014-03-26 11:20:57

Re: Error device `...` not found. Skipping fsck.

#25 2014-03-26 11:22:55

Re: Error device `...` not found. Skipping fsck.

Board footer