1 |
On Thu, May 28, 2015 at 2:11 PM, <covici@××××××××××.com> wrote: |
2 |
> |
3 |
> > Also, as Rich said, if you wait it's possible that systemd (and/or |
4 |
dracut) |
5 |
> > will drop you into a rescue shell anyway. Unfortunately, thanks to very |
6 |
> > slow hardware in the wild, the timeout has been increased to three |
7 |
minutes, |
8 |
> > and I believe those are *per hardware unit*. So if you have five disks, |
9 |
in |
10 |
> > theory it could take fifteen minutes to get you to a rescue shell. |
11 |
> |
12 |
> Thanks much. Does the rescue target try to mount all the disks? Also, |
13 |
> I would still like to get in touch with the dracut devs -- although I |
14 |
> may never make that particular mistake again, but maybe other things |
15 |
> will happen. |
16 |
|
17 |
As I said in my previous mail: emergency mounts the root filesystem |
18 |
read-only; rescue mounts all the filesystems read/write. If dracut cannot |
19 |
mount the root filesystem, it *WILL* drop you to a shell, but it will take |
20 |
some time while all the timeouts expire. This could be *several* minutes |
21 |
depending on hardware. |
22 |
|
23 |
The dracut mailing list is in [1]. |
24 |
|
25 |
Regards. |
26 |
|
27 |
[1] http://vger.kernel.org/vger-lists.html#initramfs |
28 |
-- |
29 |
Canek Peláez Valdés |
30 |
Profesor de asignatura, Facultad de Ciencias |
31 |
Universidad Nacional Autónoma de México |