Comment 8 for bug 755355

On Tue, 2011-04-12 at 15:09 +0000, Phillip Susi wrote:
> Umm... highlight the text with your mouse, choose copy, and then paste
> here?
Natty Mount output; you can see that there is only /dev/sda1
I have /dev sda1 /dev/sdb1 and /dev/sdc1... I can rectify by running
"sudo update-grub" in Maverick but every time I use update manager in
Natty it screws up again...the two grubs seem to be incompatible...My
Maverick sdc1 drive is a 320 gig USB device, hope that helps.

> g0phd@g0phd-Uknown:~$ mount
> /dev/sda1 on / type ext4 (rw,errors=remount-ro,commit=0)
> proc on /proc type proc (rw,noexec,nosuid,nodev)
> none on /sys type sysfs (rw,noexec,nosuid,nodev)
> fusectl on /sys/fs/fuse/connections type fusectl (rw)
> none on /sys/kernel/debug type debugfs (rw)
> none on /sys/kernel/security type securityfs (rw)
> none on /dev type devtmpfs (rw,mode=0755)
> none on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
> none on /dev/shm type tmpfs (rw,nosuid,nodev)
> none on /var/run type tmpfs (rw,nosuid,mode=0755)
> none on /var/lock type tmpfs (rw,noexec,nosuid,nodev)
> binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
> gvfs-fuse-daemon on /home/g0phd/.gvfs type fuse.gvfs-fuse-daemon (rw,nosuid,nodev,user=g0phd)
> g0phd@g0phd-Uknown:~$
>
>
> I have communicated with Fabio Marconi <email address hidden> on the same issue and by explanation below
>
> Thank you for your kind response. I ran "sudo apt-get clean" & ran
> update manager...There was no detectable or visible response. I may be
> able to throw some light on the issue though?
>
> I have three hard drives on the same machine, Windowsxp, Maverick 10.1,
> and Natty Beta 1.
>
> I always keep the outgoing distro (mav) until the final release of the
> new distro is relatively bug free or stable.
>
> Maverick uses the Geode driver with ATI 2400 HD pro; while Natty is now
> using the newly supplied ATI fglrx driver's which was a major problem as
> Natty default driver hangs at boot time and you cannot see the monitor
> to pull in a new driver. Natty needs a driver choice at pre-install.
>
> My problem. For Natty boot time I ran "sudo update-grub" which gave
> error message, [357.007452] EXT-fs (sdg1) write access unavailable,
> cannot proceed. I then re-booted and ran Maverick with "sudo
> update-grub" I then got the error message [170.504403] EXT-fs
> (sdc1)write access unavailable, cannot proceed.
>
> Grub seems to be incompatible with the two competing distros; at boot
> time there was several old headers present so I ran "dpkg -l 'linux-*'
> | sed '/^ii/!d;/'"$(uname -r | sed "s/\(.*\)-\([^0-9]\
> +\)/\1/")"'/d;s/^[^ ]* [^ ]* \([^ ]*\).*/\1/;/[0-9]/!d' | xargs sudo
> apt-get -y purge" to clean them.
>
> I hope this helps you comprehend the issue...many thanks Chris.
>
> --
> You received this bug notification because you are a direct subscriber
> of the bug.
> https://bugs.launchpad.net/bugs/755355
>
> Title:
> [357.007452] EXT-fs (sdg1) write access unavailable, cannot proceed
>