[357.007452] EXT-fs (sdg1) write access unavailable, cannot proceed

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

Hello Chris
Don't worry, please reply here.

The bug/issue is reported in
the terminal when downloading updates from "main server" I can only tell
you what it reported. I am an interested a user of ubuntu; not a
programmer or developer.

Can you please run in a terminal

sudo apt-get clean

then run Update Manager to see if it fixes?
Thanks
Fabio

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.

Can you post the output of the following commands, run from natty:

mount

Very sorry, not smart enough to post outputs, wish I was though. lol

On Tue, 2011-04-12 at 00:27 +0000, Phillip Susi wrote:
> Can you post the output of the following commands, run from natty:
>
> mount
>

Umm... highlight the text with your mouse, choose copy, and then paste here?

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
>

So you don't have an sdg in natty but update-grub still complains about it? And Maverick complains about sdc, which is a usb disk? Can you run update-grub with that disk unplugged and see what happens? Also can you post the output of this command from natty:

sudo blkid

Yes Phillip, Iam using the standard email evolution but it does not have
a problem. I sent the reply to your personal because it was in the
header; I thought this was the correct thing to do, sorry if not. Natty
is very buggy, (to be expected). I'm always willing to assist but very
much out of my depth with the complexities. I think its better for me to
wait for the final release.

On Tue, 2011-04-12 at 22:41 -0400, Phillip Susi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 04/12/2011 06:41 PM, Chris wrote:
> > Hi Phillip, I don’t think you have got it right yet; if I run Natty all
> > three drives are not recognised and the drive order is changed because
> > of this. The same happens when I run Maverick, all drives not recognised
> > and drive order is changed.
>
> Chris, you appear to be using evolution as your mail client, is this
> correct? When you hit reply to the mail from the bug ( not this one,
> but the one you replied to before ), it should be sending the mail to
> the bug ( <email address hidden> ). Is this not the case? If it is
> not, then evolution has a serious bug. Instead of replying to the mail,
> please click the link at the bottom to open the bug in a web browser and
> reply there so the message is attached to the bug report instead of
> going to me directly.
>
> Part of the confusion here seems to be because half of your replies have
> been sent via private email so the picture you get when reading the bug
> report is very confusing.
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAk2lDWsACgkQJ4UciIs+XuJ6EgCdECg8bqdkMCN+SfkUEM1e4UdO
> qzYAn2EuO51FthQ9PTQ3U+wNu6xtZAwT
> =6NwI
> -----END PGP SIGNATURE-----

[Expired for Ubuntu because there has been no activity for 60 days.]