Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #190858 > unrolled thread
| Started by | Elisabetta Falivene <e.falivene@ilabroma.com> |
|---|---|
| First post | 2018-01-09 22:20 +0100 |
| Last post | 2018-01-15 15:30 +0100 |
| Articles | 3 on this page of 23 — 7 participants |
Back to article view | Back to linux.debian.user
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
System won't boot anymore after upgrade to jessie Elisabetta Falivene <e.falivene@ilabroma.com> - 2018-01-09 22:20 +0100
Re: System won't boot anymore after upgrade to jessie deloptes <deloptes@gmail.com> - 2018-01-09 23:00 +0100
Re: System won't boot anymore after upgrade to jessie Elisabetta Falivene <e.falivene@ilabroma.com> - 2018-01-10 11:40 +0100
Re: System won't boot anymore after upgrade to jessie deloptes <deloptes@gmail.com> - 2018-01-10 19:50 +0100
Re: System won't boot anymore after upgrade to jessie Felix Miata <mrmazda@earthlink.net> - 2018-01-10 22:00 +0100
Re: System won't boot anymore after upgrade to jessie Greg Wooledge <wooledg@eeg.ccf.org> - 2018-01-10 22:20 +0100
Re: System won't boot anymore after upgrade to jessie deloptes <deloptes@gmail.com> - 2018-01-11 01:10 +0100
Re: System won't boot anymore after upgrade to jessie Greg Wooledge <wooledg@eeg.ccf.org> - 2018-01-11 14:50 +0100
Re: System won't boot anymore after upgrade to jessie deloptes <deloptes@gmail.com> - 2018-01-11 20:30 +0100
Re: System won't boot anymore after upgrade to jessie David Wright <deblis@lionunicorn.co.uk> - 2018-01-12 23:20 +0100
Re: System won't boot anymore after upgrade to jessie deloptes <deloptes@gmail.com> - 2018-01-12 23:30 +0100
Re: System won't boot anymore after upgrade to jessie deloptes <deloptes@gmail.com> - 2018-01-13 01:50 +0100
Re: System won't boot anymore after upgrade to jessie Don Armstrong <don@debian.org> - 2018-01-09 23:00 +0100
Re: System won't boot anymore after upgrade to jessie Elisabetta Falivene <e.falivene@ilabroma.com> - 2018-01-10 11:30 +0100
Re: System won't boot anymore after upgrade to jessie Sven Hartge <sven@svenhartge.de> - 2018-01-10 12:40 +0100
Re: System won't boot anymore after upgrade to jessie Elisabetta Falivene <e.falivene@ilabroma.com> - 2018-01-10 14:00 +0100
Re: System won't boot anymore after upgrade to jessie Sven Hartge <sven@svenhartge.de> - 2018-01-10 17:50 +0100
Re: System won't boot anymore after upgrade to jessie Elisabetta Falivene <e.falivene@ilabroma.com> - 2018-01-11 11:50 +0100
Re: System won't boot anymore after upgrade to jessie Sven Hartge <sven@svenhartge.de> - 2018-01-11 13:10 +0100
Re: System won't boot anymore after upgrade to jessie Elisabetta Falivene <e.falivene@ilabroma.com> - 2018-01-11 14:00 +0100
Re: System won't boot anymore after upgrade to jessie Elisabetta Falivene <e.falivene@ilabroma.com> - 2018-01-15 13:00 +0100
Re: System won't boot anymore after upgrade to jessie Sven Hartge <sven@svenhartge.de> - 2018-01-15 15:30 +0100
Re: System won't boot anymore after upgrade to jessie Elisabetta Falivene <e.falivene@ilabroma.com> - 2018-01-15 15:30 +0100
Page 2 of 2 — ← Prev page 1 [2]
| From | Elisabetta Falivene <e.falivene@ilabroma.com> |
|---|---|
| Date | 2018-01-15 13:00 +0100 |
| Message-ID | <v8bAJ-11k-5@gated-at.bofh.it> |
| In reply to | #190903 |
[Multipart message — attachments visible in raw view] — view raw
In the end, changing in /etc/initramfs-tools/conf.d/driver-policy MODULES=dep to MODULES=most and and then update-initramfs -u -k 3.16.0.4-amd64 (in my case it was that the problematic kernel) did the trick. My debian is booting correctly again! Thank you very much to all of you! Elisabetta 2018-01-10 17:39 GMT+01:00 Sven Hartge <sven@svenhartge.de>: > Elisabetta Falivene <e.falivene@ilabroma.com> wrote: > > >>> Unfortunately is already 'most'. > > >> Please check if you have a file /etc/initramfs-tools/conf.d/ > driver-policy > >> or any other file containing a different configuration. Anything in > >> /etc/initramfs-tools/conf.d/ takes precedence over the main config file. > > > Thank you, it was "dep" indeed! > > Then remove those additional files, check that MODULES=most is set in > /etc/initramfs-tools/initramfs.conf, do a "update-initramfs -u -kall", > and you should be good to go. > > > Reading here, though I think they were talking about ubuntu, ( > > https://ubuntuforums.org/showthread.php?t=1365365) there is a module to > > manage raid called dmraid. Maybe including that could solve the problem? > > No, dmraid is for Controller-based SoftRAID, often used with Windows. > > S° > > -- > Sigmentation fault. Core dumped. > >
[toc] | [prev] | [next] | [standalone]
| From | Sven Hartge <sven@svenhartge.de> |
|---|---|
| Date | 2018-01-15 15:30 +0100 |
| Message-ID | <v8dVT-2Lv-1@gated-at.bofh.it> |
| In reply to | #191121 |
Elisabetta Falivene <e.falivene@ilabroma.com> wrote: > In the end, changing in > /etc/initramfs-tools/conf.d/driver-policy > MODULES=dep to MODULES=most and > and then > update-initramfs -u -k 3.16.0.4-amd64 (in my case it was that the > problematic kernel) > did the trick. As I said: you are better of if you just remove the file, so you (or any other admin) doesn't get confused again, because the value from initramfs.conf is silently overridden by the value in conf.d/driver-policy. Grüße, Sven. -- Sigmentation fault. Core dumped.
[toc] | [prev] | [next] | [standalone]
| From | Elisabetta Falivene <e.falivene@ilabroma.com> |
|---|---|
| Date | 2018-01-15 15:30 +0100 |
| Message-ID | <v8dVT-2Lv-3@gated-at.bofh.it> |
| In reply to | #191133 |
[Multipart message — attachments visible in raw view] — view raw
You're right! Thanks 2018-01-15 15:19 GMT+01:00 Sven Hartge <sven@svenhartge.de>: > Elisabetta Falivene <e.falivene@ilabroma.com> wrote: > > > In the end, changing in > > /etc/initramfs-tools/conf.d/driver-policy > > MODULES=dep to MODULES=most and > > and then > > update-initramfs -u -k 3.16.0.4-amd64 (in my case it was that the > > problematic kernel) > > did the trick. > > As I said: you are better of if you just remove the file, so you (or any > other admin) doesn't get confused again, because the value from > initramfs.conf is silently overridden by the value in > conf.d/driver-policy. > > Grüße, > Sven. > > -- > Sigmentation fault. Core dumped. > >
[toc] | [prev] | [standalone]
Page 2 of 2 — ← Prev page 1 [2]
Back to top | Article view | linux.debian.user
csiph-web