system not booting after upgrading the kernel
 

2012/1/13 সাজেদুর রহিম জোয়ারদার <toshazed@gmail.com>:
> Dear Asif
>
> I hope you got your cursor blinking right here, after (initramfs)
>
> 2012/1/13 Asif Iqbal <vadud3@gmail.com>
>>
>> My system is not booting to OS after upgrading the kernel from
>> 2.6.32-36 to 2.6.32-37 on ubuntu lucid 64bit LTS
>>
>> ---------------
>> --------------------
>> -------------------------
>> (initramfs)
>
>
> type "exit" and press enter to go on.
>
> Hope you server will boot up and work as usual. Let us know the updates
> onwards. :)

yes, typing exit at the (initramfs) boots the system OK. However, I filed a bug

https://launchpad.net/bugs/916175

Thanks for your help


>
>
> With Regards
> --
> রিং/ring
> +8801671411437
>
> মহাসচিব / General Secretary
> ফাউন্ডেশন ফর ওপেন সোর্স সলিউশনস বাংলাদেশ / Foundation for Open Source
> Solutions Bangladesh
>
> প্রধান সমন্বয়ক, "পেঙ্গুইন মেলা - ২০১১" ।। ব্যক্তিগত ব্লগঃ রিং-দ্য ডন 'র
> ব্লগ ।। সদস্য, লিনাক্স মিন্ট বাংলাদেশ ।। সদস্য, উবুন্টু বাংলাদেশ
>
> --
> ubuntu-users mailing list
> ubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-users
>



--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

system not booting after upgrading the kernel
 

On Fri, Jan 13, 2012 at 7:31 PM, Asif Iqbal <vadud3@gmail.com> wrote:
> On Fri, Jan 13, 2012 at 12:26 PM, Ioannis Vranos
>>
>> Keep the Shift key pressed, when booting, to make GRUB 2 menu appear.
>> There select the previous kernel to boot.
>
> booted from the previous kernel and that worked fine
>
>>
>> After booting with the previous kernel, try to reinstall the latest
>> installed kernel packages using Synaptic (search for the string
>> 2.6.32-37).
>
> its a lucid server.

sudo apt-get update

sudo apt-get install --reinstall linux-headers-2.6.32-37

sudo apt-get install --reinstall linux-headers-2.6.32-37-generic


The most important: sudo apt-get install --reinstall
linux-image-2.6.32-37-generic


--
Ioannis Vranos

http://cppsoftware.binhoster.com

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

system not booting after upgrading the kernel
 

On Fri, Jan 13, 2012 at 3:43 PM, Ioannis Vranos
<ioannis.vranos@gmail.com> wrote:
> On Fri, Jan 13, 2012 at 7:31 PM, Asif Iqbal <vadud3@gmail.com> wrote:
>> On Fri, Jan 13, 2012 at 12:26 PM, Ioannis Vranos
>>>
>>> Keep the Shift key pressed, when booting, to make GRUB 2 menu appear.
>>> There select the previous kernel to boot.
>>
>> booted from the previous kernel and that worked fine
>>
>>>
>>> After booting with the previous kernel, try to reinstall the latest
>>> installed kernel packages using Synaptic (search for the string
>>> 2.6.32-37).
>>
>> its a lucid server.
>
> sudo apt-get update
>
> sudo apt-get install --reinstall linux-headers-2.6.32-37
>
> sudo apt-get install --reinstall linux-headers-2.6.32-37-generic

should I run `sudo apt-get install --reinstall
linux-headers-2.6.32-37-server' rather?

>
>
> The most important: sudo apt-get install --reinstall
> linux-image-2.6.32-37-generic
>
>
> --
> Ioannis Vranos
>
> http://cppsoftware.binhoster.com
>
> --
> ubuntu-users mailing list
> ubuntu-users@lists.ubuntu.com
> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users



--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--
ubuntu-users mailing list
ubuntu-users@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-users

system not booting after upgrading the kernel
 

On 13.01.2012 18:36, Asif Iqbal wrote:
> On Fri, Jan 13, 2012 at 12:09 PM, Asif Iqbal <vadud3@gmail.com> wrote:
>> My system is not booting to OS after upgrading the kernel from
>> 2.6.32-36 to 2.6.32-37 on ubuntu lucid 64bit LTS
>>
>> [ 82.750869] scsi: killing requests for dead queue
>> [ 82.750940] scsi: killing requests for dead queue
>> [ 82.751020] scsi: killing requests for dead queue
>> [ 82.751087] scsi: killing requests for dead queue
>> [ 82.751157] scsi: killing requests for dead queue
>> [ 82.751235] scsi: killing requests for dead queue
>> [ 83.201503] scsi: killing requests for dead queue
>> [ 83.201559] scsi: killing requests for dead queue
>> [ 83.201625] scsi: killing requests for dead queue
>> [ 83.201848] sd 3:0:0:0: Attached scsi generic sg1 type 0
>> [ 83.201861] sd 3:0:0:0: [sda] 143134720 512-byte logical blocks:
>> (73.2 GB/68.2 GiB)
>> [ 83.201876] sd 3:0:0:0: [sda] Write Protect is off
>> [ 83.201905] sd 3:0:0:0: [sda] Write cache: disabled, read cache:
>> enabled, supports DPO and FUA
>> [ 83.202019] sd 3:0:1:0: Attached scsi generic sg2 type 0
>> [ 83.202066] sd 3:0:1:0: [sdb] 143134720 512-byte logical blocks:
>> (73.2 GB/68.2 GiB)
>> [ 83.202088] sd 3:0:1:0: [sdb] Write Protect is off
>> [ 83.202094] sda:
>> [ 83.202137] sd 3:0:2:0: Attached scsi generic sg3 type 0
>> [ 83.202165] sd 3:0:1:0: [sdb] Write cache: disabled, read cache:
>> enabled, supports DPO and FUA
>> [ 83.202184] sd 3:0:2:0: [sdc] 143134720 512-byte logical blocks:
>> (73.2 GB/68.2 GiB)
>> [ 83.202201] sd 3:0:2:0: [sdc] Write Protect is off
>> [ 83.202229] sd 3:0:2:0: [sdc] Write cache: disabled, read cache:
>> enabled, supports DPO and FUA
>> [ 83.202301] sda1 sda2
>> [ 83.202349] sd 3:0:3:0: Attached scsi generic sg4 type 0
>> [ 83.202408] sdb:
>> [ 83.202419] sd 3:0:3:0: [sdd] 143134720 512-byte logical blocks:
>> (73.2 GB/68.2 GiB)
>> [ 83.202440] sd 3:0:3:0: [sdd] Write Protect is off
>> [ 83.202477] sd 3:0:3:0: [sdd] Write cache: disabled, read cache:
>> enabled, supports DPO and FUA
>> [ 83.202506] sdb1 sdb2
>> [ 83.202526] sdc:
>> [ 83.202580] sd 3:0:4:0: Attached scsi generic sg5 type 0
>> [ 83.202648] sdc1
>> [ 83.202735] sd 3:0:5:0: Attached scsi generic sg6 type 0
>> [ 83.202868] sd 3:0:6:0: Attached scsi generic sg7 type 0
>> [ 83.202991] sd 3:0:7:0: Attached scsi generic sg8 type 0
>> [ 83.203084] scsi 3:1:0:0: Attached scsi generic sg9 type 0
>> [ 83.203175] scsi 3:1:1:0: Attached scsi generic sg10 type 0
>> [ 83.203265] scsi 3:1:2:0: Attached scsi generic sg11 type 0
>> [ 83.203349] scsi 3:1:3:0: Attached scsi generic sg12 type 0
>> [ 83.203439] scsi 3:1:4:0: Attached scsi generic sg13 type 0
>> [ 83.203529] scsi 3:1:5:0: Attached scsi generic sg14 type 0
>> [ 83.203631] scsi 3:1:6:0: Attached scsi generic sg15 type 0
>> [ 83.203725] scsi 3:1:7:0: Attached scsi generic sg16 type 0
>> [ 83.203818] scsi 3:3:0:0: Attached scsi generic sg17 type 13
>> [ 83.203931] scsi 3:3:1:0: Attached scsi generic sg18 type 13
>> [ 83.652273] sd 3:0:4:0: [sde] 143134720 512-byte logical blocks:
>> (73.2 GB/68.2 GiB)
>> [ 83.652295] sd 3:0:4:0: [sde] Write Protect is off
>> [ 83.652324] sd 3:0:4:0: [sde] Write cache: disabled, read cache:
>> enabled, supports DPO and FUA
>> [ 83.662740] sd 3:0:5:0: [sdf] 143134720 512-byte logical blocks:
>> (73.2 GB/68.2 GiB)
>> [ 83.662752] sd 3:0:5:0: [sdf] Write Protect is off
>> [ 83.662776] sd 3:0:5:0: [sdf] Write cache: disabled, read cache:
>> enabled, supports DPO and FUA
>> [ 86.157374] sd 3:0:6:0: [sdg] 143134720 512-byte logical blocks:
>> (73.2 GB/68.2 GiB)
>> [ 86.157386] sd 3:0:6:0: [sdg] Write Protect is off
>> [ 86.157410] sd 3:0:6:0: [sdg] Write cache: disabled, read cache:
>> enabled, supports DPO and FUA
>> [ 86.170053] sd 3:0:7:0: [sdh] 143134720 512-byte logical blocks:
>> (73.2 GB/68.2 GiB)
>> [ 86.170064] sd 3:0:7:0: [sdh] Write Protect is off
>> [ 86.170087] sd 3:0:7:0: [sdh] Write cache: disabled, read cache:
>> enabled, supports DPO and FUA
>> [ 86.661916] sdd:
>> [ 86.661982] sd 3:0:0:0: [sda] Attached SCSI removable disk
>> [ 86.662049] sdd1
>> [ 86.662065] sdh:
>> [ 86.662336] sd 3:0:2:0: [sdc] Attached SCSI removable disk
>> [ 86.662389] sdh1
>> [ 86.662413] sdg:
>> [ 86.662418] sd 3:0:1:0: [sdb] Attached SCSI removable disk
>> [ 87.166186] sde: sdg1
>> [ 87.478768] sde1
>> [ 87.478933] sd 3:0:7:0: [sdh] Attached SCSI removable disk
>> [ 87.507117] sdf: sdf1
>> [ 87.507292] sd 3:0:6:0: [sdg] Attached SCSI removable disk
>> [ 87.689976] sd 3:0:4:0: [sde] Attached SCSI removable disk
>> [ 87.689997] sd 3:0:3:0: [sdd] Attached SCSI removable disk
>> [ 87.690325] sd 3:0:5:0: [sdf] Attached SCSI removable disk
>> [ 87.912605] md: bind<sdc1>
>> [ 87.946695] md: bind<sdf1>
>> [ 87.980220] md: bind<sda2>
>> [ 88.013967] md: bind<sda1>
>> ALERT! /dev/disk[ 88.062014] md: bind<sdb1>
>> /by-uuid/08febc8[ 88.096453] md: bind<sdb2>
>> 5-9ce2-40ac-a354[ 88.145336] md: bind<sdh1>
>> -e006f709a586 do[ 88.193902] raid1: raid set md0 active with 2 out
>> of 2 mirrors
>> es not exist. Dr[ 88.280220] md0: detected capacity change from 0 to
>> 31999328256
>> opping to a shel[ 88.367718] raid1: raid set md1 active with 2 out
>> of 2 mirrors
>> l!
>>
>>
>> BusyBox [ 88.368534] md0:v1.13.3 (Ubuntu
>> 1:1.13.3-1ubuntu[ 88.491525] md1: detected capacity change from 0 to
>> 41283420160
>> 11) built-in she[ 88.491626] unknown partition table
>> [ 88.491771] ses 3:3:0:0: Attached Enclosure device
>> ll (ash)
>> Enter [ 88.491780] ses 3:3:1:0: Attached Enclosure device
>> 'help' for a lis[ 88.788890] md: bind<sdg1>
>> t of built-in co[ 88.789441] md1:mmands.
>>
>> (init unknown partition table
>> ramfs) [ 88.989019] md: bind<sdd1>
>> [ 89.189178] md: bind<sde1>
>> [ 89.223307] raid10: raid set md10 active with 6 out of 6 devices
>> [ 89.295336] md10: detected capacity change from 0 to 219836645376
>> [ 89.369302] md10: unknown partition table
>>
>> (initramfs)
>>
>>
>> Any idea how to get it fixed?
>>
>
>
>
Not seeing things completely bad. The "unkown partition" message is normal for
setups which have LVM volumes directly on the whole disk (and/or md devices
doing the same). Since there are some messages from the md setup in between the
recovery shell starting, could a little more waiting (rootdelay=) help?

-Stefan

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam

system not booting after upgrading the kernel
 

On Mon, Jan 16, 2012 at 4:34 AM, Stefan Bader
<stefan.bader@canonical.com> wrote:
> On 13.01.2012 18:36, Asif Iqbal wrote:
>> On Fri, Jan 13, 2012 at 12:09 PM, Asif Iqbal <vadud3@gmail.com> wrote:
>>> My system is not booting to OS after upgrading the kernel from
>>> 2.6.32-36 to 2.6.32-37 on ubuntu lucid 64bit LTS
>>>
>>> [ * 82.750869] scsi: killing requests for dead queue
>>> [ * 82.750940] scsi: killing requests for dead queue
>>> [ * 82.751020] scsi: killing requests for dead queue
>>> [ * 82.751087] scsi: killing requests for dead queue
>>> [ * 82.751157] scsi: killing requests for dead queue
>>> [ * 82.751235] scsi: killing requests for dead queue
>>> [ * 83.201503] scsi: killing requests for dead queue
>>> [ * 83.201559] scsi: killing requests for dead queue
>>> [ * 83.201625] scsi: killing requests for dead queue
>>> [ * 83.201848] sd 3:0:0:0: Attached scsi generic sg1 type 0
>>> [ * 83.201861] sd 3:0:0:0: [sda] 143134720 512-byte logical blocks:
>>> (73.2 GB/68.2 GiB)
>>> [ * 83.201876] sd 3:0:0:0: [sda] Write Protect is off
>>> [ * 83.201905] sd 3:0:0:0: [sda] Write cache: disabled, read cache:
>>> enabled, supports DPO and FUA
>>> [ * 83.202019] sd 3:0:1:0: Attached scsi generic sg2 type 0
>>> [ * 83.202066] sd 3:0:1:0: [sdb] 143134720 512-byte logical blocks:
>>> (73.2 GB/68.2 GiB)
>>> [ * 83.202088] sd 3:0:1:0: [sdb] Write Protect is off
>>> [ * 83.202094] *sda:
>>> [ * 83.202137] sd 3:0:2:0: Attached scsi generic sg3 type 0
>>> [ * 83.202165] sd 3:0:1:0: [sdb] Write cache: disabled, read cache:
>>> enabled, supports DPO and FUA
>>> [ * 83.202184] sd 3:0:2:0: [sdc] 143134720 512-byte logical blocks:
>>> (73.2 GB/68.2 GiB)
>>> [ * 83.202201] sd 3:0:2:0: [sdc] Write Protect is off
>>> [ * 83.202229] sd 3:0:2:0: [sdc] Write cache: disabled, read cache:
>>> enabled, supports DPO and FUA
>>> [ * 83.202301] *sda1 sda2
>>> [ * 83.202349] sd 3:0:3:0: Attached scsi generic sg4 type 0
>>> [ * 83.202408] *sdb:
>>> [ * 83.202419] sd 3:0:3:0: [sdd] 143134720 512-byte logical blocks:
>>> (73.2 GB/68.2 GiB)
>>> [ * 83.202440] sd 3:0:3:0: [sdd] Write Protect is off
>>> [ * 83.202477] sd 3:0:3:0: [sdd] Write cache: disabled, read cache:
>>> enabled, supports DPO and FUA
>>> [ * 83.202506] *sdb1 sdb2
>>> [ * 83.202526] *sdc:
>>> [ * 83.202580] sd 3:0:4:0: Attached scsi generic sg5 type 0
>>> [ * 83.202648] *sdc1
>>> [ * 83.202735] sd 3:0:5:0: Attached scsi generic sg6 type 0
>>> [ * 83.202868] sd 3:0:6:0: Attached scsi generic sg7 type 0
>>> [ * 83.202991] sd 3:0:7:0: Attached scsi generic sg8 type 0
>>> [ * 83.203084] scsi 3:1:0:0: Attached scsi generic sg9 type 0
>>> [ * 83.203175] scsi 3:1:1:0: Attached scsi generic sg10 type 0
>>> [ * 83.203265] scsi 3:1:2:0: Attached scsi generic sg11 type 0
>>> [ * 83.203349] scsi 3:1:3:0: Attached scsi generic sg12 type 0
>>> [ * 83.203439] scsi 3:1:4:0: Attached scsi generic sg13 type 0
>>> [ * 83.203529] scsi 3:1:5:0: Attached scsi generic sg14 type 0
>>> [ * 83.203631] scsi 3:1:6:0: Attached scsi generic sg15 type 0
>>> [ * 83.203725] scsi 3:1:7:0: Attached scsi generic sg16 type 0
>>> [ * 83.203818] scsi 3:3:0:0: Attached scsi generic sg17 type 13
>>> [ * 83.203931] scsi 3:3:1:0: Attached scsi generic sg18 type 13
>>> [ * 83.652273] sd 3:0:4:0: [sde] 143134720 512-byte logical blocks:
>>> (73.2 GB/68.2 GiB)
>>> [ * 83.652295] sd 3:0:4:0: [sde] Write Protect is off
>>> [ * 83.652324] sd 3:0:4:0: [sde] Write cache: disabled, read cache:
>>> enabled, supports DPO and FUA
>>> [ * 83.662740] sd 3:0:5:0: [sdf] 143134720 512-byte logical blocks:
>>> (73.2 GB/68.2 GiB)
>>> [ * 83.662752] sd 3:0:5:0: [sdf] Write Protect is off
>>> [ * 83.662776] sd 3:0:5:0: [sdf] Write cache: disabled, read cache:
>>> enabled, supports DPO and FUA
>>> [ * 86.157374] sd 3:0:6:0: [sdg] 143134720 512-byte logical blocks:
>>> (73.2 GB/68.2 GiB)
>>> [ * 86.157386] sd 3:0:6:0: [sdg] Write Protect is off
>>> [ * 86.157410] sd 3:0:6:0: [sdg] Write cache: disabled, read cache:
>>> enabled, supports DPO and FUA
>>> [ * 86.170053] sd 3:0:7:0: [sdh] 143134720 512-byte logical blocks:
>>> (73.2 GB/68.2 GiB)
>>> [ * 86.170064] sd 3:0:7:0: [sdh] Write Protect is off
>>> [ * 86.170087] sd 3:0:7:0: [sdh] Write cache: disabled, read cache:
>>> enabled, supports DPO and FUA
>>> [ * 86.661916] *sdd:
>>> [ * 86.661982] sd 3:0:0:0: [sda] Attached SCSI removable disk
>>> [ * 86.662049] *sdd1
>>> [ * 86.662065] *sdh:
>>> [ * 86.662336] sd 3:0:2:0: [sdc] Attached SCSI removable disk
>>> [ * 86.662389] *sdh1
>>> [ * 86.662413] *sdg:
>>> [ * 86.662418] sd 3:0:1:0: [sdb] Attached SCSI removable disk
>>> [ * 87.166186] *sde: sdg1
>>> [ * 87.478768] *sde1
>>> [ * 87.478933] sd 3:0:7:0: [sdh] Attached SCSI removable disk
>>> [ * 87.507117] *sdf: sdf1
>>> [ * 87.507292] sd 3:0:6:0: [sdg] Attached SCSI removable disk
>>> [ * 87.689976] sd 3:0:4:0: [sde] Attached SCSI removable disk
>>> [ * 87.689997] sd 3:0:3:0: [sdd] Attached SCSI removable disk
>>> [ * 87.690325] sd 3:0:5:0: [sdf] Attached SCSI removable disk
>>> [ * 87.912605] md: bind<sdc1>
>>> [ * 87.946695] md: bind<sdf1>
>>> [ * 87.980220] md: bind<sda2>
>>> [ * 88.013967] md: bind<sda1>
>>> ALERT! /dev/disk[ * 88.062014] md: bind<sdb1>
>>> /by-uuid/08febc8[ * 88.096453] md: bind<sdb2>
>>> 5-9ce2-40ac-a354[ * 88.145336] md: bind<sdh1>
>>> -e006f709a586 do[ * 88.193902] raid1: raid set md0 active with 2 out
>>> of 2 mirrors
>>> es not exist. Dr[ * 88.280220] md0: detected capacity change from 0 to
>>> 31999328256
>>> opping to a shel[ * 88.367718] raid1: raid set md1 active with 2 out
>>> of 2 mirrors
>>> l!
>>>
>>>
>>> BusyBox [ * 88.368534] *md0:v1.13.3 (Ubuntu
>>> 1:1.13.3-1ubuntu[ * 88.491525] md1: detected capacity change from 0 to
>>> 41283420160
>>> 11) built-in she[ * 88.491626] *unknown partition table
>>> [ * 88.491771] ses 3:3:0:0: Attached Enclosure device
>>> ll (ash)
>>> Enter [ * 88.491780] ses 3:3:1:0: Attached Enclosure device
>>> 'help' for a lis[ * 88.788890] md: bind<sdg1>
>>> t of built-in co[ * 88.789441] *md1:mmands.
>>>
>>> (init unknown partition table
>>> ramfs) [ * 88.989019] md: bind<sdd1>
>>> [ * 89.189178] md: bind<sde1>
>>> [ * 89.223307] raid10: raid set md10 active with 6 out of 6 devices
>>> [ * 89.295336] md10: detected capacity change from 0 to 219836645376
>>> [ * 89.369302] *md10: unknown partition table
>>>
>>> (initramfs)
>>>
>>>
>>> Any idea how to get it fixed?
>>>
>>
>>
>>
> Not seeing things completely bad. The "unkown partition" message is normal for
> setups which have LVM volumes directly on the whole disk (and/or md devices
> doing the same). Since there are some messages from the md setup in between the
> recovery shell starting, could a little more waiting (rootdelay=) help?
>
> -Stefan

this did not show much promise with rootdelay
http://askubuntu.com/questions/15515/disk-by-uuid-not-detected-initramfs-boot-failure

I will give it a try anyways.

--
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

--
ubuntu-server mailing list
ubuntu-server@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server
More info: https://wiki.ubuntu.com/ServerTeam