It seems this bug was a result of saying 'NO' to change to a modified
version of mountkernfs.sh during a dist-upgrade. Can you confirm this?
Marking the bug as Invalid because of it. Please reopen it if you feel
the issue is still not addressed. In any case, this bug should be
against 'initscripts
I also have to change
$ cd /etc/init.d
$ sudo mv mountdevsubfs.sh.dpkg-dist mountdevsubhs.sh
--
[Intrepid] GRUB Boot mkdir / rm permission problems
https://bugs.launchpad.net/bugs/250189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I manage to see where is the mount error.
The problem raised at file /etc/rcS.d/S01mounkernfs.sh. This file calls
a function called domount
I put some echo lines to debug and some "read CONTINUE" to stop
execution
It seems theres is and Incorrect use of mount when executing:
mount -n -t tm
Weird problem...
My system stills have problems after desinstalling virtualbox a
reinstall and reconfiguring kernel too...
The weird think is that sometimes boots up correctly and sometines not.
I quit at /boot/grub/menu.lst the quiet option. If during boot I changed
to Virtual Consoles: Crtl+Alt
I had VirtualBox installed too, and the same DKMS error messages. I removed
VirtualBox without reinstalling it and reconfigured the kernel as you've
done, but it didn't fix the problem. It seems there are troubles with file
systems other than ext3, so I installed Intrepid on another partition. I ha
More info and how I solved this problem
At /var/log/messages there is a message That says Cannot find map file
I change to Virtual Console. Entre username an password and I remount
root:
$ sudo mount -o remount,rw /
I recovered network by typing:
$ sudo dhclient eth0
I do a:
$ sudo ap
Ditto here like Thorsten... fine in recovery mode and selecting
resume... but not when using regular boot option. What gives?
--
[Intrepid] GRUB Boot mkdir / rm permission problems
https://bugs.launchpad.net/bugs/250189
You received this bug notification because you are a member of Ubuntu
Bugs,
I'm getting the same warnings as Thorsten Kunz. Fresh 8.10 install.
--
[Intrepid] GRUB Boot mkdir / rm permission problems
https://bugs.launchpad.net/bugs/250189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing li
I get an error very similar to what others are seeing on a fresh 8.10 Release
install on my laptop.
I get this during boot (manually typed so might not be 100% accurate):
[...]
* Setting up resolvconf...
rm: cannot remove `/etc/resolvconf/run/interface/*`: Read-only file system
/etc/rcS.d/S07reso
Please excuse my persistence. Googling around I found that names for IDE
and SATA devices were merged since Feisty (/dev/hda being treated as
/dev/sda). I got this changes only after upgrading to Intrepid, and I
think it's causing more troubles than benefits. I think I've set up
every file: /etc/fs
A fresh install is not a real solution, but it could let us understand the
source of the problem. I'm running Kubuntu for 2 years, when I discovered
Dapper, and I sincerely would rather not to reinstall.
What is really strange in this kernel is that it always says "could not find
map file", alt
I don't get this error anymore. I reinstalled Hardy, then upgraded to
Intrepid
--
[Intrepid] GRUB Boot mkdir / rm permission problems
https://bugs.launchpad.net/bugs/250189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
File System gets mounted in read only mode with older kernels as well.
Upgrade to 8.10 RC made boot hang at half of the process, earlier than
before.
--
[Intrepid] GRUB Boot mkdir / rm permission problems
https://bugs.launchpad.net/bugs/250189
You received this bug notification because you are a
I get file system mounted in read only mode even with 2.6.27-7-generic. I still
can boot from recovery mode, but my whole system is screwed up. Also,
/etc/blkid.tab shows different drives than /etc/fstab. Fixing drive names
doesn't resolve it, but screws up drives even more (e.g.: /dev/sda becam
Still getting these messages when booting 2.6.27-3
--
[Intrepid] GRUB Boot mkdir / rm permission problems
https://bugs.launchpad.net/bugs/250189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lis
Still getting these messages when booting 2.6.27-1 using recovery boot.
Can't boot 2.6.27-2 Fully updated alpha5 as of today.
** Changed in: linux (Ubuntu)
Status: Fix Released => Confirmed
--
[Intrepid] GRUB Boot mkdir / rm permission problems
https://bugs.launchpad.net/bugs/250189
You r
The 2.6.27 solved the problem here, thanks, please reset to Confirmed if
you are still experiencing the problem.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
[Intrepid] GRUB Boot mkdir / rm permission problems
https://bugs.launchpad.net/bugs/250189
You received this
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
Prevents X from starting here as well.
** Changed in: linux (Ubuntu)
Importance: Undecided => High
--
[Intrepid] GRUB Boot mkdir / rm permission problems
https://bugs.launchpad.net/bugs/250189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to U
$ cat /etc/fstab
# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
#
proc /proc proc defaults 0 0
# Entry for /dev/hdb1 :
UUID=7e99f2b0-3c6b-4d5a-bd87-3be01a378ec6 / ext3 defaults,errors=remount-ro 0 1
# Entry for /d
Two more things:
1) This bug didn't have a package assigned to it, so I have filed it under
"linux" which is for the kernel.
2) For future reference, please don't confirm your own bugs, it is up to others
to confirm your bug for you. Since Richard and I both experienced read only
file systems,
No, it looks normal (ext3 is basically ext2 with journaling added - ext3
partitions can be mounted as ext2).
--
[Intrepid] GRUB Boot mkdir / rm permission problems
https://bugs.launchpad.net/bugs/250189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
>>You may need to cross reference the contents of fstab to the output of
>> sudo blkid
[EMAIL PROTECTED]:~$ cat /etc/fstab
# /etc/fstab: static file system information.
#
#
proc/proc procdefaults0 0
# /dev/sda1
UUID=7a352281-d258-4f93-ac5d-51
This afternoon I booted Intrepid after a few days of rest, X couldn't
start and dropped me to a TTY. Tried to reconfigure X, found I had a
read only filesystem, so I ran fsck and all checked out. My fstab file
UUIDs still matched with blkid, so I rebooted and all was well. I saw
on your UF post
** Changed in: ubuntu
Status: New => Confirmed
--
[Intrepid] GRUB Boot mkdir / rm permission problems
https://bugs.launchpad.net/bugs/250189
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@
I'm also getting:
mkdir: cannot create directory
'/lib/modules/2.6.26-4-generic/volatile/':read only file system
Also when it states Setting up Networking - it will wait for about a
minute or until I press any key before continuing to boot.
--
[Intrepid] GRUB Boot mkdir / rm permission problems
** Tags added: intrepid
--
[Intrepid] GRUB Boot mkdir / rm permission problems
https://bugs.launchpad.net/bugs/250189
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.com
https://lists
27 matches
Mail list logo
