@Scott - Today's updates cured my boot problem (the last mount time in
future), but I wanted to thank you while I was thinking of it. I also
miss the nice "Thank You!" button; I firmly believe the old adage that
one heart-felt "Well Done!" wipes out a hundred "Aw s*%#" 's."
Thank You!
--
diffic
Since we haven't heard off the original reporter in a little while, and
his issue was fixed separately (the last mount time in future thing),
and other comments have been positive, I'm going to mark this as fixed.
You do get a shell in case of bad fsck, but now exiting that shell
retries everythin
Scott,
I'm totally impressed, with the today's update the problem is solved.
As there was an upgrade to kernel (2.6.31-13.45) there would have been a
Superblock issue. - and was not.
And even my VBd is mounted correctly.
Congratulations and thank you verry much.
I still miss a VWD button (V
Next round
I went back to a version of Karmic where I could boot with the VBd.
I added your repository and manually made a
sudo apt-get install mountall
I made a ez_mt_before.log
I booted (hang)
I removed the VBd from fstab via life CD
I booted again. (no VBd mounted)
I did NOT make a mout -
Am Samstag, den 10.10.2009, 10:41 + schrieb Scott James Remnant:
> On Fri, 2009-10-09 at 16:28 +, Ernst Zlo wrote:
>
> > With or without your ~beta5: kernel 2.6.31-12 will hang with a VBd in
> > the /etc/fstab.
> >
> > Is the mountall.log of any interest for you, when the VBd is NOT moun
** Changed in: mountall (Ubuntu Karmic)
Status: Incomplete => Triaged
--
difficult to recover from filesystem errors
https://bugs.launchpad.net/bugs/432237
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
On Fri, 2009-10-09 at 16:28 +, Ernst Zlo wrote:
> With or without your ~beta5: kernel 2.6.31-12 will hang with a VBd in
> the /etc/fstab.
>
> Is the mountall.log of any interest for you, when the VBd is NOT mounted
> (which I am forced now, because otherwise my kernel won't work)?
>
> And af
After a walk with my dog my brain is either complete damaged or working
better:
IMHO Ubuntu is trying now to start a VBd wich only can work if the
VirtualBox Guestadditions are allready working, which are working AFTER
all harddisks are mounted.
And you can't start the VirtualBox Guestadditions w
Sorry, Scott.
With or without your ~beta5: kernel 2.6.31-12 will hang with a VBd in
the /etc/fstab.
Is the mountall.log of any interest for you, when the VBd is NOT mounted
(which I am forced now, because otherwise my kernel won't work)?
And afterwards I only can supply you with a mountall.log w
On Fri, 2009-10-09 at 15:16 +, Ernst Zlo wrote:
> And by typing this essay of #...@!* bugs it becomes clear to me: please
> give me ~beta6 because without ~beta5 nothing goes, with ~beta5 nothing
> goes either.
>
You haven't supplied your debug.log
Scott
--
Scott James Remnant
sc...@ubuntu.
I went back to the point before upgrading to 2.6.31.13
I installed your repository
I did
sudo apt-get -f install
sudo apt-get --fix-missing install
sudo apt-get clean
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get clean
sudo apt-get autoremove
I checked if the VirtualBox drive is in /
> > 1) A "filesystem last mounted in future" error is still treated as
> > serious enough to interrupt the boot process and require
> interaction
> > via mountall-shell. My view is that this is not appopriate because
> > this may well happen when Windows fiddles with the clock on a
> > dual
In the meantime I've upgraded to the new linux 2.6.31.13
And now I have the hanging without your repository as described above:
When trying to reboot it hangs with the white Ubuntu logo and no
errormessage till the moment when (as I am sure now because it fades
away) the scrensaver switches of the
On Fri, 2009-10-09 at 14:02 +, Ernst Zlo wrote:
> VirtualBox shared folder is to blame
> (which I mount in my /etc/fstab with the line
> extras /media/xtra vboxsf uid=1000,gid=1000,rw 0 0
> stops the photon torpedos ;-)
>
> When I remove the line everything's smooth and perfect.
>
I'd alrea
On Fri, 2009-10-09 at 13:45 +, Dave Martin wrote:
> However, I still have a couple of issues:
>
> 1) A "filesystem last mounted in future" error is still treated as
> serious enough to interrupt the boot process and require interaction via
> mountall-shell. My view is that this is not appopr
Hello Scott,
I'm one of the 5%.
VirtualBox shared folder is to blame
(which I mount in my /etc/fstab with the line
extras /media/xtra vboxsf uid=1000,gid=1000,rw 0 0
stops the photon torpedos ;-)
When I remove the line everything's smooth and perfect.
I've included a tar.gz where you see:
mo
Hi... rebooted again on armel:
Now, boot does resume after the mountall-shell exits *if* the shell
exits with status zero.
However, I still have a couple of issues:
1) A "filesystem last mounted in future" error is still treated as
serious enough to interrupt the boot process and require interac
Sure, this is a definite step forward; some teething problems are
inevitable.
Output from mountall (~boot4) --debug before reboot on armel attached.
Note that mountall doesn't appear to terminate in this case... is that
the expected behaviour?
I'll post further results after I reboot.
** Attach
Sorry about the issues with the previous PPA versions, as usual things
worked just fine when I tested it in the various rigs I have here - of
course it flatly failed when installed on normal systems because I
hadn't actually tested that ;)
I've uploaded a new ~boot4 version, this one feels much be
On Thu, 2009-10-08 at 15:14 +, Dave Martin wrote:
> > > By default, mountall throws a lot of "Read-only filesystem" errors
> > > while trying to clean /tmp, and drops to a root shell.
> > >
> > > Alternatively, if I remount the root filesystem read-write before
> > > running init, init (or
Hi there...
with ~boot3, I still seem to get the "read-only filesystem" errors, and
I still get dropped to a root shell.
I run mountall --debug towards the end of the log, in case that helps.
** Attachment added: "karmic-mountall.log"
http://launchpadlibrarian.net/33304112/karmic-mountall.lo
> > ** Attachment added: "mountall.log"
> >http://launchpadlibrarian.net/33292692/mountall.log
> >
> This log is not from the PPA, I'd prefer to see the log from the PPA.
Apologies... looks like I misunderstood your instructions there...
[...]
> > By default, mountall throws a lot of "Read-
On Thu, 2009-10-08 at 11:53 +, Dave Martin wrote:
> By default, mountall throws a lot of "Read-only filesystem" errors while
> trying to clean /tmp, and drops to a root shell.
>
> Alternatively, if I remount the root filesystem read-write before
> running init, init (or possibly mountall) app
On Thu, 2009-10-08 at 11:24 +, Dave Martin wrote:
> Before installing your update, running sudo mountall --debug on a booted
> system (this is mountall version 0.1.8) produces the attached output and
> appears to deadlock. The mountall process does not terminate.
>
> ** Attachment added: "mo
On Thu, 2009-10-08 at 11:17 +, Ernst Zlo wrote:
> I've installed your update:
> VirtualBox now hangs with the mounting of the shared folder. forever.
>
Thanks. I've fixed this issue, new upload to the PPA is pending.
Again, I would appreciate testing.
Scott
--
Scott James Remnant
sc...@ubu
After installing the updated mountall package on armel, I can't boot at
all...
By default, mountall throws a lot of "Read-only filesystem" errors while
trying to clean /tmp, and drops to a root shell.
Alternatively, if I remount the root filesystem read-write before
running init, init (or possibl
Nr 2
** Attachment added: "Bildschirmfoto-2.png"
http://launchpadlibrarian.net/33293011/Bildschirmfoto-2.png
--
difficult to recover from filesystem errors
https://bugs.launchpad.net/bugs/432237
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Scott
I've removed the line
sudo mount -t vboxsf -o uid=1000,gid=1000 extras /media/xtra
After that the boot resulted in this output (trying 3 rounds with no
better result)
** Attachment added: "Bildschirmfoto-1.png"
http://launchpadlibrarian.net/33293004/Bildschirmfoto-1.png
--
difficult t
No 3
this is the point of no return only STRG+ALT+DEL helps out and leads back to
here.
** Attachment added: "Bildschirmfoto-3.png"
http://launchpadlibrarian.net/33293088/Bildschirmfoto-3.png
--
difficult to recover from filesystem errors
https://bugs.launchpad.net/bugs/432237
You received t
Before installing your update, running sudo mountall --debug on a booted
system (this is mountall version 0.1.8) produces the attached output and
appears to deadlock. The mountall process does not terminate.
** Attachment added: "mountall.log"
http://launchpadlibrarian.net/33292692/mountall.lo
Scott
I've installed your update:
VirtualBox now hangs with the mounting of the shared folder. forever.
hehehe I've to reinstall as I suppose
(because I was silly enough to forget to make a snapshot. and yes this IS my
fault )
IMHO :^Þ
** Attachment added: "Bildschirmfoto2.png"
http://lau
Is there a recommended way to readily reproduce the problem? I'm happy
to test the new package but I haven't seen the problem in a while.
--
difficult to recover from filesystem errors
https://bugs.launchpad.net/bugs/432237
You received this bug notification because you are a member of Ubuntu
Bug
I've uploaded a new mountall package to the ubuntu-boot PPA:
https://launchpad.net/~ubuntu-boot/+archive/ppa
I would appreciate it if you could install this and try it out.
*BEFORE* you reboot though, could you run "sudo mountall --debug >
mountall.log 2>&1" and attach that to this bug - then aft
For me, when fsck requests manual intervention and drops you to a shell,
usplash now stays open so that all you see is an Ubuntu logo on a black
screen. I had to guess what the problem is, then switch virtual
consoles a few times to find the shell.
--
difficult to recover from filesystem errors
This has nothing to do with the "GNU R package for bootstrapping
functions from Davison and Hinkley"
** Changed in: mountall (Ubuntu Karmic)
Status: Triaged => In Progress
** Changed in: boot (Ubuntu Karmic)
Status: Confirmed => Invalid
--
difficult to recover from filesystem erro
It is kind of another bug but I think it's all being tracked here.
--
difficult to recover from filesystem errors
https://bugs.launchpad.net/bugs/432237
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-
I wre affected by this bug, too. I manually started fsck which worked
without problems. But on trying to continue booting by pressing CTRL+D
(as the error message says) mountall block the furter boot process:
Filesystem check failed.
A Maintenance shell will now be started.
CONTROL-D will
When I installed Karmic beta, I selected "Log-in and encrypt HDD". Now
the boot sequence complains about file system time in the future,
demands a manual fsck, bypasses the command prompt, then hangs
attempting to access the encrypted HDD. Keyboard inputs have no effect.
I've attached a screenshot
also, heres a log of times etc from me booting my system and looking at
the clocks more closely. thank god for the boot time speedups thats all
i have to say :D
so far what i think the problem is, ubuntu is reading the time wrong and
then "correcting" the hardware clock when it successfully boots,
here is the data iv gathered:
:~# date ( wrong, in the root shell that i was given after the system failed to
boot)
Sat Oct 3 22:50:39 EST 2009
real time:
@desktop:~$ date (correct, on my other computer)
Sat Oct 3 23:53:58 EST 2009
bios reports:
System time: 23:54:50 (correct, bios on the co
So, the packet we should not update is 'upstart'?
--
difficult to recover from filesystem errors
https://bugs.launchpad.net/bugs/432237
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu
One workaround I found was using the magic SysRq keys. With SysRq+R
SysRq+E I got to a root shell from where I could run fsck and reboot.
--
difficult to recover from filesystem errors
https://bugs.launchpad.net/bugs/432237
You received this bug notification because you are a member of Ubuntu
Bug
** Summary changed:
- system fails to boot if root partition has errors
+ difficult to recover from filesystem errors
--
difficult to recover from filesystem errors
https://bugs.launchpad.net/bugs/432237
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
43 matches
Mail list logo
