yes i can't also boot after the .14 kernel also, and still .12 works for me also. I'm adding the .14 to the description.
** Summary changed: - GUTSY - Won't boot after update - .13 kernel won't boot - trying to boot up a disk that doesn't exist. -More info Added Tue Oct. 9 2007 - uname, version, dmesg, lspci-vvnn logs added + GUTSY - Won't boot after update - .13 & .14 kernel won't boot - trying to boot up a disk that doesn't exist. -More info Added Tue Oct. 9 2007 - uname, version, dmesg, lspci-vvnn logs added ** Description changed: Note: the .13 kernel was fine until after some updates earlier today which somehow killed it. after an update a few minutes ago - I keep up with the updates just about every day and it fails after assuming drive write cache, so I also went into grub and selected recovery mode and it stops after .13 in recovery mode: 25.067306 sd 0:0:0:0 [sda] Attached SCSI Removable disk. .13 when booted up normally stops at the following: 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through I noticed also several things the 54.XXXX numbers randomly change on each reboot also the loading seems a bit slow before drive cache. However if I boot up with the .12 kernel all works fine and everything works, so what i'm assuming is that it is looking for an non-existant SCSI removable disk which is not there and never was there and booted up fine before the updates and even boots up after choosing the .12 kernel. okay more info. on the system and the file is html i used the command in terninal lshw -html >lshw.html what that does it output all proc info into the lshw.htm file in the home folder in one big html file. It is attached on the comment below. Adding: I also noticed the diff. between the two the .13 kernel has again 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through while the .12 kernel has X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through the x's are a place holder for numbers which I don't believe change on the .12 kernel, however also noticing that .13 says all 0's while the .12 kernel has a number 4 instead of a zero and still continues to boot fine may give an indication as to why it's not booting up my computer with the .13 kernel. + + + ......... + I added also .14 to the description because it won't boot up with that either - and the same thing happends also adding that it never shows before write cache like on .12 the hibernation trying to restore resume lines and goes straight to the assuming write cache line. That happens on both .13 and .14/ ** Description changed: Note: the .13 kernel was fine until after some updates earlier today which somehow killed it. after an update a few minutes ago - I keep up with the updates just about every day and it fails after assuming drive write cache, so I also went into grub and selected recovery mode and it stops after .13 in recovery mode: 25.067306 sd 0:0:0:0 [sda] Attached SCSI Removable disk. .13 when booted up normally stops at the following: 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through I noticed also several things the 54.XXXX numbers randomly change on each reboot also the loading seems a bit slow before drive cache. However if I boot up with the .12 kernel all works fine and everything works, so what i'm assuming is that it is looking for an non-existant SCSI removable disk which is not there and never was there and booted up fine before the updates and even boots up after choosing the .12 kernel. okay more info. on the system and the file is html i used the command in terninal lshw -html >lshw.html what that does it output all proc info into the lshw.htm file in the home folder in one big html file. It is attached on the comment below. Adding: I also noticed the diff. between the two the .13 kernel has again 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through while the .12 kernel has X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through the x's are a place holder for numbers which I don't believe change on the .12 kernel, however also noticing that .13 says all 0's while the .12 kernel has a number 4 instead of a zero and still continues to boot fine may give an indication as to why it's not booting up my computer with the .13 kernel. ......... - I added also .14 to the description because it won't boot up with that either - and the same thing happends also adding that it never shows before write cache like on .12 the hibernation trying to restore resume lines and goes straight to the assuming write cache line. That happens on both .13 and .14/ + I added also .14 to the summary title because it won't boot up with that either - and the same thing happends also adding that it never shows before write cache like on .12 the hibernation trying to restore resume lines and goes straight to the assuming write cache line. That happens on both .13 and .14/ ** Description changed: Note: the .13 kernel was fine until after some updates earlier today which somehow killed it. after an update a few minutes ago - I keep up with the updates just about every day and it fails after assuming drive write cache, so I also went into grub and selected recovery mode and it stops after .13 in recovery mode: 25.067306 sd 0:0:0:0 [sda] Attached SCSI Removable disk. .13 when booted up normally stops at the following: 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through I noticed also several things the 54.XXXX numbers randomly change on each reboot also the loading seems a bit slow before drive cache. However if I boot up with the .12 kernel all works fine and everything works, so what i'm assuming is that it is looking for an non-existant SCSI removable disk which is not there and never was there and booted up fine before the updates and even boots up after choosing the .12 kernel. okay more info. on the system and the file is html i used the command in terninal lshw -html >lshw.html what that does it output all proc info into the lshw.htm file in the home folder in one big html file. It is attached on the comment below. Adding: I also noticed the diff. between the two the .13 kernel has again 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through while the .12 kernel has X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through the x's are a place holder for numbers which I don't believe change on the .12 kernel, however also noticing that .13 says all 0's while the .12 kernel has a number 4 instead of a zero and still continues to boot fine may give an indication as to why it's not booting up my computer with the .13 kernel. ......... - I added also .14 to the summary title because it won't boot up with that either - and the same thing happends also adding that it never shows before write cache like on .12 the hibernation trying to restore resume lines and goes straight to the assuming write cache line. That happens on both .13 and .14/ + I added also .14 to the summary title because it won't boot up with that either - and the same thing happens also adding that it never shows before write cache like on .12 the hibernation trying to restore resume lines and goes straight to the assuming write cache line. This happens on both .13 and .14. ** Description changed: Note: the .13 kernel was fine until after some updates earlier today which somehow killed it. after an update a few minutes ago - I keep up with the updates just about every day and it fails after assuming drive write cache, so I also went into grub and selected recovery mode and it stops after .13 in recovery mode: 25.067306 sd 0:0:0:0 [sda] Attached SCSI Removable disk. .13 when booted up normally stops at the following: 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through I noticed also several things the 54.XXXX numbers randomly change on each reboot also the loading seems a bit slow before drive cache. However if I boot up with the .12 kernel all works fine and everything works, so what i'm assuming is that it is looking for an non-existant SCSI removable disk which is not there and never was there and booted up fine before the updates and even boots up after choosing the .12 kernel. okay more info. on the system and the file is html i used the command in terninal lshw -html >lshw.html what that does it output all proc info into the lshw.htm file in the home folder in one big html file. It is attached on the comment below. Adding: I also noticed the diff. between the two the .13 kernel has again 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through while the .12 kernel has X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through the x's are a place holder for numbers which I don't believe change on the .12 kernel, however also noticing that .13 says all 0's while the .12 kernel has a number 4 instead of a zero and still continues to boot fine may give an indication as to why it's not booting up my computer with the .13 kernel. ......... - I added also .14 to the summary title because it won't boot up with that either - and the same thing happens also adding that it never shows before write cache like on .12 the hibernation trying to restore resume lines and goes straight to the assuming write cache line. This happens on both .13 and .14. + I added also .14 to the summary title because it won't boot up with that either - and the same thing happens just as before. + + Also it never shows kinit trying to resume from image mesage before + write cache like it does on .12 and like I said goes straight to the + Assuming write cache part. Again This happens on both .13 and .14. ** Summary changed: - GUTSY - Won't boot after update - .13 & .14 kernel won't boot - trying to boot up a disk that doesn't exist. -More info Added Tue Oct. 9 2007 - uname, version, dmesg, lspci-vvnn logs added + GUTSY - Won't boot after update - .13 & .14 kernel won't boot - trying to boot up a disk that doesn't exist.& USB drive -More info Added Tue Oct. 9 2007 - uname, version, dmesg, lspci-vvnn logs added ** Description changed: Note: the .13 kernel was fine until after some updates earlier today which somehow killed it. after an update a few minutes ago - I keep up with the updates just about every day and it fails after assuming drive write cache, so I also went into grub and selected recovery mode and it stops after .13 in recovery mode: 25.067306 sd 0:0:0:0 [sda] Attached SCSI Removable disk. .13 when booted up normally stops at the following: 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through I noticed also several things the 54.XXXX numbers randomly change on each reboot also the loading seems a bit slow before drive cache. However if I boot up with the .12 kernel all works fine and everything works, so what i'm assuming is that it is looking for an non-existant SCSI removable disk which is not there and never was there and booted up fine before the updates and even boots up after choosing the .12 kernel. okay more info. on the system and the file is html i used the command in terninal lshw -html >lshw.html what that does it output all proc info into the lshw.htm file in the home folder in one big html file. It is attached on the comment below. Adding: I also noticed the diff. between the two the .13 kernel has again 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through while the .12 kernel has X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through the x's are a place holder for numbers which I don't believe change on the .12 kernel, however also noticing that .13 says all 0's while the .12 kernel has a number 4 instead of a zero and still continues to boot fine may give an indication as to why it's not booting up my computer with the .13 kernel. ......... I added also .14 to the summary title because it won't boot up with that either - and the same thing happens just as before. Also it never shows kinit trying to resume from image mesage before write cache like it does on .12 and like I said goes straight to the Assuming write cache part. Again This happens on both .13 and .14. + + + .................. + Update: + + Okay so i think i know what it is dong ,well I went to try out + something. U see I have a usb centon 1gb disk plugged in all the time + and well i unplugged, rebooted and well it just stopped after loading + please wait and didn't show anything else not even the sd and 4 zeros + and didn't even show Assuming Drive Write Cache. + + I plugged back in the USB drive while it shoing nothing but please wait + and then that assuming Drive Write Cache came up however the .14 with it + not plugged in was a bit slower showing the loading part and the .13 was + a bit quicker. So i know believe it's trying to boot up my USB drive for + some odd reason and hanging on that. However in the end both again show + that they are trying to boot off my non- bootable usb drive and then + hangs after that and if it's not plugged it just hangs at please wait + and goes no further. ** Summary changed: - GUTSY - Won't boot after update - .13 & .14 kernel won't boot - trying to boot up a disk that doesn't exist.& USB drive -More info Added Tue Oct. 9 2007 - uname, version, dmesg, lspci-vvnn logs added + GUTSY - Won't boot after update - .13 & .14 kernel won't boot - trying to boot up a disk that doesn't exist - possibly and USB drive -More info Added Tue Oct. 9 2007 - uname, version, dmesg, lspci-vvnn logs added ** Summary changed: - GUTSY - Won't boot after update - .13 & .14 kernel won't boot - trying to boot up a disk that doesn't exist - possibly and USB drive -More info Added Tue Oct. 9 2007 - uname, version, dmesg, lspci-vvnn logs added + GUTSY - Won't boot after update - Tries to boot A USB Drive and then hangs if none is inserted then it just hangs. ** Summary changed: - GUTSY - Won't boot after update - Tries to boot A USB Drive and then hangs if none is inserted then it just hangs. + GUTSY - Won't boot after update - Tries to boot A USB Drive and then hangs if none is inserted then it just hangs with or without it inserted. ** Summary changed: - GUTSY - Won't boot after update - Tries to boot A USB Drive and then hangs if none is inserted then it just hangs with or without it inserted. + GUTSY - Wo't boot after update - Tries to boot A USB FLASH/PEN Drive and then hangs if none is inserted then it just hangs with or without it inserted. ** Summary changed: - GUTSY - Wo't boot after update - Tries to boot A USB FLASH/PEN Drive and then hangs if none is inserted then it just hangs with or without it inserted. + GUTSY - Wo't boot after update - Tries to boot A USB FLASH/PEN Drive and then hangs if none is inserted then it just hangs with or without it inserted with both .13 & .14 kernels - .12 is unaffected. ** Summary changed: - GUTSY - Wo't boot after update - Tries to boot A USB FLASH/PEN Drive and then hangs if none is inserted then it just hangs with or without it inserted with both .13 & .14 kernels - .12 is unaffected. + GUTSY - Won't boot after update - Tries to boot A USB FLASH/PEN Drive and then hangs if none is inserted then it just hangs with or without it inserted with both .13 & .14 kernels - .12 is unaffected. ** Description changed: Note: the .13 kernel was fine until after some updates earlier today which somehow killed it. after an update a few minutes ago - I keep up with the updates just about every day and it fails after assuming drive write cache, so I also went into grub and selected recovery mode and it stops after .13 in recovery mode: 25.067306 sd 0:0:0:0 [sda] Attached SCSI Removable disk. .13 when booted up normally stops at the following: 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through I noticed also several things the 54.XXXX numbers randomly change on each reboot also the loading seems a bit slow before drive cache. However if I boot up with the .12 kernel all works fine and everything works, so what i'm assuming is that it is looking for an non-existant SCSI removable disk which is not there and never was there and booted up fine before the updates and even boots up after choosing the .12 kernel. okay more info. on the system and the file is html i used the command in terninal lshw -html >lshw.html what that does it output all proc info into the lshw.htm file in the home folder in one big html file. It is attached on the comment below. Adding: I also noticed the diff. between the two the .13 kernel has again 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through while the .12 kernel has X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through the x's are a place holder for numbers which I don't believe change on the .12 kernel, however also noticing that .13 says all 0's while the .12 kernel has a number 4 instead of a zero and still continues to boot fine may give an indication as to why it's not booting up my computer with the .13 kernel. ......... I added also .14 to the summary title because it won't boot up with that either - and the same thing happens just as before. Also it never shows kinit trying to resume from image mesage before write cache like it does on .12 and like I said goes straight to the Assuming write cache part. Again This happens on both .13 and .14. .................. Update: - Okay so i think i know what it is dong ,well I went to try out - something. U see I have a usb centon 1gb disk plugged in all the time - and well i unplugged, rebooted and well it just stopped after loading - please wait and didn't show anything else not even the sd and 4 zeros - and didn't even show Assuming Drive Write Cache. + Okay so i think i know what it is doing ,well I went to try out + something. U see I have a usb centon 1gb flash/pen disk plugged in all + the time and well i unplugged, and rebooted into the .13 and .14 kernels + to do a test and see if that is what was causing it, and well it just + stopped after loading please wait and didn't show anything else not even + the sd and 4 zeros and didn't even show Assuming Drive Write Cache. - I plugged back in the USB drive while it shoing nothing but please wait + I plugged back in the USB drive while it showing nothing but please wait and then that assuming Drive Write Cache came up however the .14 with it not plugged in was a bit slower showing the loading part and the .13 was a bit quicker. So i know believe it's trying to boot up my USB drive for some odd reason and hanging on that. However in the end both again show that they are trying to boot off my non- bootable usb drive and then hangs after that and if it's not plugged it just hangs at please wait and goes no further. ** Description changed: Note: the .13 kernel was fine until after some updates earlier today which somehow killed it. after an update a few minutes ago - I keep up with the updates just about every day and it fails after assuming drive write cache, so I also went into grub and selected recovery mode and it stops after .13 in recovery mode: 25.067306 sd 0:0:0:0 [sda] Attached SCSI Removable disk. .13 when booted up normally stops at the following: 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through I noticed also several things the 54.XXXX numbers randomly change on each reboot also the loading seems a bit slow before drive cache. However if I boot up with the .12 kernel all works fine and everything works, so what i'm assuming is that it is looking for an non-existant SCSI removable disk which is not there and never was there and booted up fine before the updates and even boots up after choosing the .12 kernel. okay more info. on the system and the file is html i used the command in terninal lshw -html >lshw.html what that does it output all proc info into the lshw.htm file in the home folder in one big html file. It is attached on the comment below. Adding: I also noticed the diff. between the two the .13 kernel has again 54.245577 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through 54.257543 sd 0:0:0:0 [sda] Assuming Drive Cache: Write Through while the .12 kernel has X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through X.XXXX sd 4:0:0:0 [sda] Assuming Drive Cache: Write Through the x's are a place holder for numbers which I don't believe change on the .12 kernel, however also noticing that .13 says all 0's while the .12 kernel has a number 4 instead of a zero and still continues to boot fine may give an indication as to why it's not booting up my computer with the .13 kernel. ......... I added also .14 to the summary title because it won't boot up with that either - and the same thing happens just as before. Also it never shows kinit trying to resume from image mesage before write cache like it does on .12 and like I said goes straight to the Assuming write cache part. Again This happens on both .13 and .14. .................. Update: Okay so i think i know what it is doing ,well I went to try out something. U see I have a usb centon 1gb flash/pen disk plugged in all the time and well i unplugged, and rebooted into the .13 and .14 kernels to do a test and see if that is what was causing it, and well it just stopped after loading please wait and didn't show anything else not even the sd and 4 zeros and didn't even show Assuming Drive Write Cache. I plugged back in the USB drive while it showing nothing but please wait and then that assuming Drive Write Cache came up however the .14 with it not plugged in was a bit slower showing the loading part and the .13 was - a bit quicker. So i know believe it's trying to boot up my USB drive for + a bit quicker. So i now believe it's trying to boot up my USB drive for some odd reason and hanging on that. However in the end both again show that they are trying to boot off my non- bootable usb drive and then hangs after that and if it's not plugged it just hangs at please wait and goes no further. + + oh and the drive is vfat and I did/going to attach my fstab info and + grub list in a zip format. -- GUTSY - Won't boot after update - Tries to boot A USB FLASH/PEN Drive and then hangs if none is inserted then it just hangs with or without it inserted with both .13 & .14 kernels - .12 is unaffected. https://bugs.launchpad.net/bugs/150739 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
