Re: timed out waiting for device dev-disk-by\x2duuid after disk failure on btrfs raid1

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, Jan 04, 2020 at 11:38:05PM +0100, Georg Großmann wrote:
> Dear btrfs community,
> 
> I wanted to use a setup with Open Suse Tumbleweed together with with a
> btrfs raid 1 on two disks in my virtual box. I want a system that can
> still boot if one of the disks fails so I installed a bootloader to each
> of the disks in /dev/sda1 and /dev/sdb1.
> 
> I then used /dev/sda2 and /dev/sdb2 for the btrfs raid 1. After
> unplugging one disk, the boot process always fails with the message
> "timed out waiting for device dev-disk-by\x2duuid". I found a mailing
> list here
> https://lists.freedesktop.org/archives/systemd-devel/2014-May/019217.html
> which pretty well describes my problem. Unfortunately, I can't find an
> appropriate solution there. Since this mailing list is from 2014, has
> there been some progress in the meantime? Or is this the expected
> behaviour and the user has to help himself out manually?

   With a missing device, you need to mount with the "degraded" mount
option. The current advice is that this should be a manual process.
If the FS in question includes the root filesystem, this will involve
editing the mount options passed to the kernel in the bootloader (GRUB
allows you to do this at boot time).

   Hugo.

-- 
Hugo Mills             | vi vi vi: the Editor of the Beast.
hugo@... carfax.org.uk |
http://carfax.org.uk/  |
PGP: E2AB1DE4          |



[Index of Archives]     [Linux Filesystem Development]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux