Re: Problem with kernel-image-3.10-2-amd64
Shane Johnson, 28.09.2013: I have been fighting this all night and was wondering if anyone else has been having problems as well? I am doing a new install via debootstrap to a lvm2 volume via the wheezy rescue disk. I got it running in wheezy then went to jessie and while I was running the 3.2 kernel from wheezy it booted fine. Then I upgraded the kernel to 3.10 in jessie and it says it can't find the volume goup. I have made sure that initrd is updated and grub is updated. Not sure on what the next step would be or if this is just a bug that I need to wait for it to be resolved or if I need to submit a bug? Is your initramfs-tools package also from jessie? There was recently a thread where somebody using wheezy with an encrypted disk over lvm upgraded to a 3.10 kernel from backports and had problems booting until also upgrading the initramfs-tools package to the version in backports. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131001115119.ga28...@cs.utexas.edu
Re: Problem with kernel-image-3.10-2-amd64
Everyone, Thank you for your help and suggestions. I was able to add rootdelay=5 to the kernel line and this resolved the issue for me. Sincerely. Shane On Mon, Sep 30, 2013 at 8:51 AM, Chris Bannister cbannis...@slingshot.co.nz wrote: On Mon, Sep 30, 2013 at 05:16:38PM +0300, Georgi Naplatanov wrote: I had impression that 'rootdelay=5' had solved your problem and that is why I gave you that link. If you read the thread, you will see it was not me. Also note, it was another poster (Hugo) who suggested that the OP try 'rootdelay=5' to see if it helped. To your question - if 'rootdelay=5' solves your problem then it's a known problem. Incorrect. A known problem is one that is explicitly documented for that specific version of software. I can see that language barriers may confuse the meaning of words. Think of the well known ports 1-1024 as an example of the use of the word known. It is the same usage in regards to a known bug. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130930145059.GA25109@tal -- Shane D. Johnson IT Administrator Rasmussen Equipment -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/caplo1l54pyo8avs3gnddw4yusukftsecm6q4d6sq15bk3zb...@mail.gmail.com
Re: Problem with kernel-image-3.10-2-amd64
On Mon, Sep 30, 2013 at 02:57:54AM +0300, Georgi Naplatanov wrote: On 09/30/2013 02:03 AM, Hugo Vanwoerkom wrote: Georgi Naplatanov wrote: On 09/29/2013 05:24 PM, Chris Bannister wrote: On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote: add 'rootdelay=5'(w/o the quotes) to the boot parameters. Is this a known problem for this kernel? Yes, it's written in the release notes. You have a link for that? http://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#boot-timing Sigh! If you read the OP: I got it running in wheezy then went to jessie and while I was running the 3.2 kernel from wheezy it booted fine. Then I upgraded the kernel to 3.10 in jessie and it says it can't find the volume goup. The link you give mentions neither jessie, nor kernel 3.10 in particular. So I presume it is not a known problem FOR THE 3.10 kernel? -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130930133150.GE22494@tal
Re: Problem with kernel-image-3.10-2-amd64
On 09/30/2013 04:31 PM, Chris Bannister wrote: On Mon, Sep 30, 2013 at 02:57:54AM +0300, Georgi Naplatanov wrote: On 09/30/2013 02:03 AM, Hugo Vanwoerkom wrote: Georgi Naplatanov wrote: On 09/29/2013 05:24 PM, Chris Bannister wrote: On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote: add 'rootdelay=5'(w/o the quotes) to the boot parameters. Is this a known problem for this kernel? Yes, it's written in the release notes. You have a link for that? http://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#boot-timing Sigh! If you read the OP: I got it running in wheezy then went to jessie and while I was running the 3.2 kernel from wheezy it booted fine. Then I upgraded the kernel to 3.10 in jessie and it says it can't find the volume goup. The link you give mentions neither jessie, nor kernel 3.10 in particular. So I presume it is not a known problem FOR THE 3.10 kernel? I had impression that 'rootdelay=5' had solved your problem and that is why I gave you that link. To your question - if 'rootdelay=5' solves your problem then it's a known problem. Best regards Georgi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/524987c6.50...@oles.biz
Re: Problem with kernel-image-3.10-2-amd64
Georgi Naplatanov wrote: On 09/30/2013 02:03 AM, Hugo Vanwoerkom wrote: Georgi Naplatanov wrote: On 09/29/2013 05:24 PM, Chris Bannister wrote: On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote: Shane Johnson wrote: I have been fighting this all night and was wondering if anyone else has been having problems as well? I am doing a new install via debootstrap to a lvm2 volume via the wheezy rescue disk. I got it running in wheezy then went to jessie and while I was running the 3.2 kernel from wheezy it booted fine. Then I upgraded the kernel to 3.10 in jessie and it says it can't find the volume goup. I have made sure that initrd is updated and grub is updated. Not sure on what the next step would be or if this is just a bug that I need to wait for it to be resolved or if I need to submit a bug? Thanks for your help. add 'rootdelay=5'(w/o the quotes) to the boot parameters. Is this a known problem for this kernel? Yes, it's written in the release notes. You have a link for that? Hugo http://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#boot-timing It's for wheezy, I didn't see you have a problem with newer kernel. That doesn't exactly cover the OP's case of LVM not being recognized by Debian kernel 3.10-2-amd64 and 3.10-3-amd64 as also addressed by http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=707286 because dm-mod is not loaded in time. Rootdelay=3 in my own case solves that. And it seems specifically having to do with those Debian kernels. I.e. my own kernels of 3.10.7 etc. don't have the problem. Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l2c2dq$e9f$1...@ger.gmane.org
Re: Problem with kernel-image-3.10-2-amd64
On Mon, Sep 30, 2013 at 05:16:38PM +0300, Georgi Naplatanov wrote: I had impression that 'rootdelay=5' had solved your problem and that is why I gave you that link. If you read the thread, you will see it was not me. Also note, it was another poster (Hugo) who suggested that the OP try 'rootdelay=5' to see if it helped. To your question - if 'rootdelay=5' solves your problem then it's a known problem. Incorrect. A known problem is one that is explicitly documented for that specific version of software. I can see that language barriers may confuse the meaning of words. Think of the well known ports 1-1024 as an example of the use of the word known. It is the same usage in regards to a known bug. -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130930145059.GA25109@tal
Re: Problem with kernel-image-3.10-2-amd64
On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote: Shane Johnson wrote: I have been fighting this all night and was wondering if anyone else has been having problems as well? I am doing a new install via debootstrap to a lvm2 volume via the wheezy rescue disk. I got it running in wheezy then went to jessie and while I was running the 3.2 kernel from wheezy it booted fine. Then I upgraded the kernel to 3.10 in jessie and it says it can't find the volume goup. I have made sure that initrd is updated and grub is updated. Not sure on what the next step would be or if this is just a bug that I need to wait for it to be resolved or if I need to submit a bug? Thanks for your help. add 'rootdelay=5'(w/o the quotes) to the boot parameters. Is this a known problem for this kernel? -- If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing. --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130929142414.GF6820@tal
Re: Problem with kernel-image-3.10-2-amd64
On 09/29/2013 05:24 PM, Chris Bannister wrote: On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote: Shane Johnson wrote: I have been fighting this all night and was wondering if anyone else has been having problems as well? I am doing a new install via debootstrap to a lvm2 volume via the wheezy rescue disk. I got it running in wheezy then went to jessie and while I was running the 3.2 kernel from wheezy it booted fine. Then I upgraded the kernel to 3.10 in jessie and it says it can't find the volume goup. I have made sure that initrd is updated and grub is updated. Not sure on what the next step would be or if this is just a bug that I need to wait for it to be resolved or if I need to submit a bug? Thanks for your help. add 'rootdelay=5'(w/o the quotes) to the boot parameters. Is this a known problem for this kernel? Yes, it's written in the release notes. Best regards Georgi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52483fe5.1050...@oles.biz
Re: Problem with kernel-image-3.10-2-amd64
Georgi Naplatanov wrote: On 09/29/2013 05:24 PM, Chris Bannister wrote: On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote: Shane Johnson wrote: I have been fighting this all night and was wondering if anyone else has been having problems as well? I am doing a new install via debootstrap to a lvm2 volume via the wheezy rescue disk. I got it running in wheezy then went to jessie and while I was running the 3.2 kernel from wheezy it booted fine. Then I upgraded the kernel to 3.10 in jessie and it says it can't find the volume goup. I have made sure that initrd is updated and grub is updated. Not sure on what the next step would be or if this is just a bug that I need to wait for it to be resolved or if I need to submit a bug? Thanks for your help. add 'rootdelay=5'(w/o the quotes) to the boot parameters. Is this a known problem for this kernel? Yes, it's written in the release notes. You have a link for that? Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l2abiv$lvi$1...@ger.gmane.org
Re: Problem with kernel-image-3.10-2-amd64
On 09/30/2013 02:03 AM, Hugo Vanwoerkom wrote: Georgi Naplatanov wrote: On 09/29/2013 05:24 PM, Chris Bannister wrote: On Sat, Sep 28, 2013 at 11:52:00AM -0500, Hugo Vanwoerkom wrote: Shane Johnson wrote: I have been fighting this all night and was wondering if anyone else has been having problems as well? I am doing a new install via debootstrap to a lvm2 volume via the wheezy rescue disk. I got it running in wheezy then went to jessie and while I was running the 3.2 kernel from wheezy it booted fine. Then I upgraded the kernel to 3.10 in jessie and it says it can't find the volume goup. I have made sure that initrd is updated and grub is updated. Not sure on what the next step would be or if this is just a bug that I need to wait for it to be resolved or if I need to submit a bug? Thanks for your help. add 'rootdelay=5'(w/o the quotes) to the boot parameters. Is this a known problem for this kernel? Yes, it's written in the release notes. You have a link for that? Hugo http://www.debian.org/releases/stable/amd64/release-notes/ch-upgrading.en.html#boot-timing It's for wheezy, I didn't see you have a problem with newer kernel. Best regards Georgi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5248be82.7000...@oles.biz
Re: Problem with kernel-image-3.10-2-amd64
Shane Johnson wrote: I have been fighting this all night and was wondering if anyone else has been having problems as well? I am doing a new install via debootstrap to a lvm2 volume via the wheezy rescue disk. I got it running in wheezy then went to jessie and while I was running the 3.2 kernel from wheezy it booted fine. Then I upgraded the kernel to 3.10 in jessie and it says it can't find the volume goup. I have made sure that initrd is updated and grub is updated. Not sure on what the next step would be or if this is just a bug that I need to wait for it to be resolved or if I need to submit a bug? Thanks for your help. add 'rootdelay=5'(w/o the quotes) to the boot parameters. Hugo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/l271f4$o5c$1...@ger.gmane.org
