hi,
sorry for the big 'lag' but i did not have the chance to give intrepid a
go until now. it seems - however - that the aforementioned bug is no
longer present in the current ubuntu release. at least it did not show
up until now, that is, after ~10 regular shutdowns.
--
root FS not cleanly
I am setting the status to Fix Released. If the bug appears again please
reopen this bug report.
** Changed in: linux (Ubuntu)
Status: Incomplete = Fix Released
--
root FS not cleanly unmounted on SSD
https://bugs.launchpad.net/bugs/260807
You received this bug notification because you
** This bug is no longer flagged as a security issue
--
root FS not cleanly unmounted on SSD
https://bugs.launchpad.net/bugs/260807
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
The Intrepid Ibex 8.10 Beta release was most recently announced -
http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27
Ubuntu kernel. It would be great if you could test and verify if this
is still an issue. The status is being set to Incomplete until we
receive further
Hi roots,
The linux-ubuntu-modules package was actually merged with the linux
kernel source package beginning with the Intrepid Ibex development cycle
so it no longer exists for Intrepid. Thanks.
--
root FS not cleanly unmounted on SSD
https://bugs.launchpad.net/bugs/260807
You received this
i would go with the 2.6.27 kernel only for the first. i just downloaded
linux-headers-2.6.27-1-generic_2.6.27-1.2_i386.deb
linux-image-2.6.27-1-generic_2.6.27-1.2_i386.deb
linux-restricted-modules-2.6.27-1-generic_2.6.27-1.1_i386.deb
from http://packages.ubuntu.com but i can't seem to find any
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
well there's bad news - i had already tried to find something in the logfiles
but to no avail - they do resume just after the kernel-induced reboot after the
initial fsck. furthermore, i now recognized that after such crashy shutdown,
fsck does not only find errors but also had died with error
ok, i got a bit further into it. first of all, i found that kernel
logging was delayed per - switch in /etc/syslog.conf. i removed that
and now kern.log shows some strange news on shutdown:
Aug 25 09:10:50 machineone kernel: [ 2013.680949] sd 5:0:0:0: [sdb]
Synchronizing SCSI cache
Aug 25
if you're asking for why i am using ext2: amongst one of the
recommendations for SSDs i found that using a non-journaling fs would be
more convenient, because it reduces the write access to the drive, which
- due to the writing-weakness inherent in flash technology - should have
an impact on both
after a bit more of testing, i found that this occurs only on shutdown
(gnome shutdown button, shutdown -h now, halt), not if i let ubuntu
reboot and power off the system manually before grub starts.
--
root FS not cleanly unmounted on SSD
https://bugs.launchpad.net/bugs/260807
You received this
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately we can't fix it without more information.
Please include the following additional information, if you have not already
done so (pay attention to lspci's additional options), as required by the
hi,
thanks for your quick reply. here's the info you requested:
sudo uname -a
Linux machineone 2.6.24-21-generic #1 SMP Tue Aug 12 13:37:22 UTC 2008 i686
GNU/Linux
dmesg and lspci outputs are attached.
if there's any more info i may provide, please let me know.
p.s. well i'm sure you would
** Attachment added: lspci-vvnn.log
http://launchpadlibrarian.net/17046647/lspci-vvnn.log
--
root FS not cleanly unmounted on SSD
https://bugs.launchpad.net/bugs/260807
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
It would be useful to have a log file from the crash. Can you reproduce
the crash on shutdown, then start your computer again and attach the
file /var/log/kern.log. If I am right, this file contains all the logs
from the last 24 hours and after the crash the log is hopefully written
to disk.
--
15 matches
Mail list logo
