hard drive not being seen error UID 1000 - Ubuntu

This is a discussion on hard drive not being seen error UID 1000 - Ubuntu ; the old problem hal-storage-fixed-mount refused uid 1000 nothing to do with NTFS this time, its an ext3 partition with opensuse 11.0 on it, which obviously mounts it fine! HELP i have tried loads of things!"!! cheers andrew...

+ Reply to Thread
Results 1 to 14 of 14

Thread: hard drive not being seen error UID 1000

  1. hard drive not being seen error UID 1000

    the old problem hal-storage-fixed-mount refused uid 1000

    nothing to do with NTFS this time, its an ext3 partition with opensuse
    11.0 on it, which obviously mounts it fine!

    HELP i have tried loads of things!"!!

    cheers andrew

  2. Re: hard drive not being seen error UID 1000

    grace illuminated alt.os.linux.ubuntu by typing:
    > the old problem hal-storage-fixed-mount refused uid 1000
    >
    > nothing to do with NTFS this time, its an ext3 partition with opensuse
    > 11.0 on it, which obviously mounts it fine!
    >
    > HELP i have tried loads of things!"!!
    >
    > cheers andrew


    Fstab issue.

    Post the output of

    cat /etc/fstab

    You've got a misconfiguration somewhere.

    --
    Moog

    “Are you going to come quietly, or do I have to use earplugs?”

  3. Re: hard drive not being seen error UID 1000

    Moog wrote:
    > grace illuminated alt.os.linux.ubuntu by typing:
    >> the old problem hal-storage-fixed-mount refused uid 1000
    >>
    >> nothing to do with NTFS this time, its an ext3 partition with opensuse
    >> 11.0 on it, which obviously mounts it fine!
    >>
    >> HELP i have tried loads of things!"!!
    >>
    >> cheers andrew

    >
    > Fstab issue.
    >
    > Post the output of
    >
    > cat /etc/fstab
    >
    > You've got a misconfiguration somewhere.
    >


    will try to attach fstab

    # /etc/fstab: static file system information.
    #
    #
    proc /proc proc defaults 0 0
    # /dev/sda1
    UUID=7623375c-2ef5-48bb-b446-cf5df086ed65 / ext3 defaults,errors=remount-ro 0 1
    # /dev/sda5
    UUID=df07f3a8-6a09-4e43-a916-5088e4cb259d none swap sw 0 0
    /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
    /dev/scd1 /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
    /dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0

  4. Re: hard drive not being seen error UID 1000

    Moog wrote:
    > grace illuminated alt.os.linux.ubuntu by typing:
    >> the old problem hal-storage-fixed-mount refused uid 1000
    >>
    >> nothing to do with NTFS this time, its an ext3 partition with opensuse
    >> 11.0 on it, which obviously mounts it fine!
    >>
    >> HELP i have tried loads of things!"!!
    >>
    >> cheers andrew

    >
    > Fstab issue.
    >
    > Post the output of
    >
    > cat /etc/fstab
    >
    > You've got a misconfiguration somewhere.
    >

    will do the backup too

    # UNCONFIGURED FSTAB FOR BASE SYSTEM


  5. Re: hard drive not being seen error UID 1000

    grace illuminated alt.os.linux.ubuntu by typing:
    > This is a multi-part message in MIME format.
    > --------------020301030800040908000408
    > Content-Type: text/plain; charset=ISO-8859-1; format=flowed
    > Content-Transfer-Encoding: 7bit
    >
    > Moog wrote:
    >> grace illuminated alt.os.linux.ubuntu by typing:
    >>> the old problem hal-storage-fixed-mount refused uid 1000
    >>>
    >>> nothing to do with NTFS this time, its an ext3 partition with opensuse
    >>> 11.0 on it, which obviously mounts it fine!
    >>>
    >>> HELP i have tried loads of things!"!!
    >>>
    >>> cheers andrew

    >>
    >> Fstab issue.
    >>
    >> Post the output of
    >>
    >> cat /etc/fstab
    >>
    >> You've got a misconfiguration somewhere.
    >>

    > will do the backup too
    >
    > --------------020301030800040908000408
    > Content-Type: text/plain;
    > name="fstab.pre-uuid"
    > Content-Transfer-Encoding: 7bit
    > Content-Disposition: inline;
    > filename="fstab.pre-uuid"
    >
    > # UNCONFIGURED FSTAB FOR BASE SYSTEM
    >
    > --------------020301030800040908000408--


    That's your fstab?

    No wonder you are having problems.

    Are you using some sort of third party disk management utility?

    Here's what an fastab should look like

    # /etc/fstab: static file system information.
    #
    #
    proc /proc proc defaults 0 0
    # /dev/sda6
    UUID=1d1642ed-04cf-417d-939a-1e6e6127519d / ext3
    errors=remount-ro 0 1
    # /dev/sda1
    UUID=6672D16672D13C0D /media/sda1 ntfs
    defaults,umask=007,gid=46 0 1
    # /dev/sda2
    UUID=3EAC94E3AC94974D /media/sda2 ntfs
    defaults,umask=007,gid=46 0 1
    # /dev/sda4
    UUID=D60056EF0056D659 /media/sda4 ntfs
    defaults,umask=007,gid=46 0 1
    # /dev/sda5
    UUID=a9b65e66-de06-4a6b-8efa-2c2542d360da none swap sw
    0 0
    /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0


    --
    Moog

    “Are you going to come quietly, or do I have to use earplugs?”

  6. Re: hard drive not being seen error UID 1000

    Moog wrote:
    > grace illuminated alt.os.linux.ubuntu by typing:
    >> This is a multi-part message in MIME format.
    >> --------------020301030800040908000408
    >> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
    >> Content-Transfer-Encoding: 7bit
    >>
    >> Moog wrote:

    not this one its the initial one , see the previous post

    andrew




    >>> grace illuminated alt.os.linux.ubuntu by typing:
    >>>> the old problem hal-storage-fixed-mount refused uid 1000
    >>>>
    >>>> nothing to do with NTFS this time, its an ext3 partition with opensuse
    >>>> 11.0 on it, which obviously mounts it fine!
    >>>>Spo
    >>>> HELP i have tried loads of things!"!!
    >>>>
    >>>> cheers andrew
    >>> Fstab issue.
    >>>
    >>> Post the output of
    >>>
    >>> cat /etc/fstab
    >>>
    >>> You've got a misconfiguration somewhere.
    >>>

    >> will do the backup too
    >>
    >> --------------020301030800040908000408
    >> Content-Type: text/plain;
    >> name="fstab.pre-uuid"
    >> Content-Transfer-Encoding: 7bit
    >> Content-Disposition: inline;
    >> filename="fstab.pre-uuid"
    >>
    >> # UNCONFIGURED FSTAB FOR BASE SYSTEM
    >>
    >> --------------020301030800040908000408--

    >
    > That's your fstab?
    >
    > No wonder you are having problems.
    >
    > Are you using some sort of third party disk management utility?
    >
    > Here's what an fastab should look like
    >
    > # /etc/fstab: static file system information.
    > #
    > #
    > proc /proc proc defaults 0 0
    > # /dev/sda6
    > UUID=1d1642ed-04cf-417d-939a-1e6e6127519d / ext3
    > errors=remount-ro 0 1
    > # /dev/sda1
    > UUID=6672D16672D13C0D /media/sda1 ntfs
    > defaults,umask=007,gid=46 0 1
    > # /dev/sda2
    > UUID=3EAC94E3AC94974D /media/sda2 ntfs
    > defaults,umask=007,gid=46 0 1
    > # /dev/sda4
    > UUID=D60056EF0056D659 /media/sda4 ntfs
    > defaults,umask=007,gid=46 0 1
    > # /dev/sda5
    > UUID=a9b65e66-de06-4a6b-8efa-2c2542d360da none swap sw
    > 0 0
    > /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
    >
    >


  7. Re: hard drive not being seen error UID 1000

    grace illuminated alt.os.linux.ubuntu by typing:
    > This is a multi-part message in MIME format.
    > --------------050103010801010504070008
    > Content-Type: text/plain; charset=UTF-8; format=flowed
    > Content-Transfer-Encoding: 7bit
    >
    > Moog wrote:
    >> grace illuminated alt.os.linux.ubuntu by typing:
    >>> the old problem hal-storage-fixed-mount refused uid 1000
    >>>
    >>> nothing to do with NTFS this time, its an ext3 partition with opensuse
    >>> 11.0 on it, which obviously mounts it fine!
    >>>
    >>> HELP i have tried loads of things!"!!
    >>>
    >>> cheers andrew

    >>
    >> Fstab issue.
    >>
    >> Post the output of
    >>
    >> cat /etc/fstab
    >>
    >> You've got a misconfiguration somewhere.
    >>

    >
    > will try to attach fstab
    >
    > --------------050103010801010504070008
    > Content-Type: text/plain;
    > name="fstab"
    > Content-Transfer-Encoding: base64
    > Content-Disposition: inline;
    > filename="fstab"
    >
    > IyAvZXRjL2ZzdGFiOiBzdGF0aWMgZmlsZSBzeXN0ZW0gaW5mb3 JtYXRpb24uCiMKIyA8Zmls
    > ZSBzeXN0ZW0+IDxtb3VudCBwb2ludD4gICA8dHlwZT4gIDxvcH Rpb25zPiAgICAgICA8ZHVt
    > cD4gIDxwYXNzPgpwcm9jICAgICAgICAgICAgL3Byb2MgICAgIC AgICAgIHByb2MgICAgZGVm
    > YXVsdHMgICAgICAgIDAgICAgICAgMAojIC9kZXYvc2RhMQpVVU lEPTc2MjMzNzVjLTJlZjUt
    > NDhiYi1iNDQ2LWNmNWRmMDg2ZWQ2NSAvICAgICAgICAgICAgIC AgZXh0MyAgICBkZWZhdWx0
    > cyxlcnJvcnM9cmVtb3VudC1ybyAwICAgICAgIDEKIyAvZGV2L3 NkYTUKVVVJRD1kZjA3ZjNh
    > OC02YTA5LTRlNDMtYTkxNi01MDg4ZTRjYjI1OWQgbm9uZSAgIC AgICAgICAgIHN3YXAgICAg
    > c3cgICAgICAgICAgICAgIDAgICAgICAgMAovZGV2L3NjZDAgIC AgICAgL21lZGlhL2Nkcm9t
    > MCAgIHVkZixpc285NjYwIHVzZXIsbm9hdXRvLGV4ZWMgMCAgIC AgICAwCi9kZXYvc2NkMSAg
    > ICAgICAvbWVkaWEvY2Ryb20xICAgdWRmLGlzbzk2NjAgdXNlci xub2F1dG8sZXhlYyAwICAg
    > ICAgIDAKL2Rldi9mZDAgICAgICAgIC9tZWRpYS9mbG9wcHkwIC BhdXRvICAgIHJ3LHVzZXIs
    > bm9hdXRvLGV4ZWMgMCAgICAgICAwCg==
    > --------------050103010801010504070008--


    This isn't the contents of your fstab (at least in a readable form)

    Open a terminal
    Applications -> Accessories -> Terminal

    Then type

    $ cat /etc/fstab

    (don't enter the $ sign. That simply signifies the terminal prompt)
    Copy and paste the output here.


    --
    Moog

    “Are you going to come quietly, or do I have to use earplugs?”

  8. Re: hard drive not being seen error UID 1000

    grace illuminated alt.os.linux.ubuntu by typing:

    >
    > not this one its the initial one , see the previous post
    >
    > andrew


    Andrew. Neither were fstab contents.

    See my other post.

    Cheers.

    --
    Moog

    “Are you going to come quietly, or do I have to use earplugs?”

  9. Re: hard drive not being seen error UID 1000

    Moog wrote:
    > grace illuminated alt.os.linux.ubuntu by typing:
    >
    >>
    >> not this one its the initial one , see the previous post
    >>
    >> andrew

    >
    > Andrew. Neither were fstab contents.
    >
    > See my other post.
    >
    > Cheers.
    >



    # /etc/fstab: static file system information.
    #
    #
    proc /proc proc defaults 0 0
    # /dev/sda1
    UUID=7623375c-2ef5-48bb-b446-cf5df086ed65 / ext3
    defaults,errors=remount-ro 0 1
    # /dev/sda5
    UUID=df07f3a8-6a09-4e43-a916-5088e4cb259d none swap sw
    0 0
    /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
    /dev/scd1 /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
    /dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0



    andrew

  10. Re: hard drive not being seen error UID 1000

    Moog schrieb:

    > grace illuminated alt.os.linux.ubuntu by typing:
    > Andrew. Neither were fstab contents.
    >
    > See my other post.


    The first one, you mean shows the following for me:

    ------------
    # /etc/fstab: static file system information.
    #
    # * * * * * *
    proc * * * * * */proc * * * * * proc * *defaults * * * *0 * * * 0
    # /dev/sda1
    UUID=7623375c-2ef5-48bb-b446-cf5df086ed65 / * * * * * * *
    ext3 * *defaults,errors=remount-ro 0 * * * 1
    # /dev/sda5
    UUID=df07f3a8-6a09-4e43-a916-5088e4cb259d
    none * * * * * *swap * *sw * * * * * * *0 * * * 0
    /dev/scd0 * * * /media/cdrom0 * udf,iso9660 user,noauto,exec 0 * * * 0
    /dev/scd1 * * * /media/cdrom1 * udf,iso9660 user,noauto,exec 0 * * * 0
    /dev/fd0 * * * */media/floppy0 *auto * *rw,user,noauto,exec 0 * * * 0
    ------------

    I guess it's an "advanced feature" to append base64(or whatever)-encoded
    files to postings. My KNode understood it for some reason.

    Andrwe, would you mind to add contents of text-files inline, in future?
    (The way like I did it here.) It's more compatible.

    HTH
    Andreas

  11. Re: hard drive not being seen error UID 1000

    andrew fox wrote:
    > Moog wrote:
    >> grace illuminated alt.os.linux.ubuntu by typing:
    >>
    >>>
    >>> not this one its the initial one , see the previous post
    >>>
    >>> andrew

    >>
    >> Andrew. Neither were fstab contents.
    >>
    >> See my other post.
    >> Cheers.
    >>

    >
    >
    > # /etc/fstab: static file system information.
    > #
    > #
    > proc /proc proc defaults 0 0
    > # /dev/sda1
    > UUID=7623375c-2ef5-48bb-b446-cf5df086ed65 / ext3
    > defaults,errors=remount-ro 0 1
    > # /dev/sda5
    > UUID=df07f3a8-6a09-4e43-a916-5088e4cb259d none swap sw
    > 0 0
    > /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
    > /dev/scd1 /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
    > /dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0
    >
    >
    >
    > andrew



    it doesnt mention sdb anywhere does it?

    andrew

    (grace grandad)

  12. Re: hard drive not being seen error UID 1000

    Andreas Wagner wrote:
    > Moog schrieb:
    >
    >> grace illuminated alt.os.linux.ubuntu by typing:
    >> Andrew. Neither were fstab contents.
    >>
    >> See my other post.

    >
    > The first one, you mean shows the following for me:
    >
    > ------------
    > # /etc/fstab: static file system information.
    > #
    > #
    > proc /proc proc defaults 0 0
    > # /dev/sda1
    > UUID=7623375c-2ef5-48bb-b446-cf5df086ed65 /
    > ext3 defaults,errors=remount-ro 0 1
    > # /dev/sda5
    > UUID=df07f3a8-6a09-4e43-a916-5088e4cb259d
    > none swap sw 0 0
    > /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
    > /dev/scd1 /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
    > /dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0
    > ------------
    >
    > I guess it's an "advanced feature" to append base64(or whatever)-encoded
    > files to postings. My KNode understood it for some reason.
    >
    > Andrwe, would you mind to add contents of text-files inline, in future?
    > (The way like I did it here.) It's more compatible.
    >
    > HTH
    > Andreas



    yep thats my fstab, and it doesnt mention the 2nd hard drive does it?
    sdb1 it would be, ( or D drive in dos) and it isnt ntfs it ext3

    cheers andrew
    i take it i can use a text editor like kate on this to get it shipshape??

  13. Re: hard drive not being seen error UID 1000

    andrew fox illuminated alt.os.linux.ubuntu by typing:
    > andrew fox wrote:
    >> Moog wrote:
    >>> grace illuminated alt.os.linux.ubuntu by typing:
    >>>
    >>>>
    >>>> not this one its the initial one , see the previous post
    >>>>
    >>>> andrew
    >>>
    >>> Andrew. Neither were fstab contents.
    >>>
    >>> See my other post.
    >>> Cheers.
    >>>

    >>
    >>
    >> # /etc/fstab: static file system information.
    >> #
    >> #
    >> proc /proc proc defaults 0 0
    >> # /dev/sda1
    >> UUID=7623375c-2ef5-48bb-b446-cf5df086ed65 / ext3
    >> defaults,errors=remount-ro 0 1
    >> # /dev/sda5
    >> UUID=df07f3a8-6a09-4e43-a916-5088e4cb259d none swap sw
    >> 0 0
    >> /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
    >> /dev/scd1 /media/cdrom1 udf,iso9660 user,noauto,exec 0 0
    >> /dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0


    That's better.

    > it doesnt mention sdb anywhere does it?


    No. It doesn't. So there's no surprise that you're having issues

    What do you get if you type in this into a terminal?
    $ sudo vol_id /dev/sdb1

    Any output, post it here.

    If there's no output, we're going to have to run Gparted to see what
    has happened.

    $ sudo apt-get install gparted

    System -> Administration -> Partition Editor
    /or/
    $ gparted

    Does the disk appear in there? If it does, what info does it give you?

    --
    Moog

    “Are you going to come quietly, or do I have to use earplugs?”

  14. Re: hard drive not being seen error UID 1000

    Andreas Wagner illuminated alt.os.linux.ubuntu by typing:
    > Moog schrieb:
    >
    >> grace illuminated alt.os.linux.ubuntu by typing:
    >> Andrew. Neither were fstab contents.
    >>
    >> See my other post.

    >
    > The first one, you mean shows the following for me:
    >
    > ------------
    > # /etc/fstab: static file system information.
    > #
    > # * * * * * *
    > proc * * * * * */proc * * * * * proc * *defaults * * * *0 * * * 0
    > # /dev/sda1
    > UUID=7623375c-2ef5-48bb-b446-cf5df086ed65 / * * * * * * *
    > ext3 * *defaults,errors=remount-ro 0 * * * 1
    > # /dev/sda5
    > UUID=df07f3a8-6a09-4e43-a916-5088e4cb259d
    > none * * * * * *swap * *sw * * * * * * *0 * * * 0
    > /dev/scd0 * * * /media/cdrom0 * udf,iso9660 user,noauto,exec 0 * * * 0
    > /dev/scd1 * * * /media/cdrom1 * udf,iso9660 user,noauto,exec 0 * * * 0
    > /dev/fd0 * * * */media/floppy0 *auto * *rw,user,noauto,exec 0 * * * 0
    > ------------
    >
    > I guess it's an "advanced feature" to append base64(or whatever)-encoded
    > files to postings. My KNode understood it for some reason.
    >
    > Andrwe, would you mind to add contents of text-files inline, in future?
    > (The way like I did it here.) It's more compatible.


    Interesting. Cheers Andreas.

    --
    Moog

    “Are you going to come quietly, or do I have to use earplugs?”

+ Reply to Thread