Announcement

Collapse
No announcement yet.

Kubuntu 12.04 no longer recognizes blank media

Collapse
This topic is closed.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Kubuntu 12.04 no longer recognizes blank media

    Suddenly my computer no longer recognizes blank media any disc that something on it is mounted and available, am unsure what to do next any suggestions are greatly appreciated, thanks from a linux noob

    #2
    Ok thought I better add some info still searching for clues my system was function just fine came back the next day went to burn another data disc and k3b says please insert an empty or appendable dvd or bluray disc , I dont think its hardware because both k3b and dolphin recognized a disc that has something already on it just not blank discs

    game disc
    xxxx@xxxxxx:~$ mount
    /dev/sda1 on / type ext4 (rw,errors=remount-ro)
    proc on /proc type proc (rw,noexec,nosuid,nodev)
    sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
    none on /sys/fs/fuse/connections type fusectl (rw)
    none on /sys/kernel/debug type debugfs (rw)
    none on /sys/kernel/security type securityfs (rw)
    udev on /dev type devtmpfs (rw,mode=0755)
    devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
    tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
    none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
    none on /run/shm type tmpfs (rw,nosuid,nodev)
    /dev/sdc1 on /media/sdc1 type ext3 (rw,noexec,nosuid,nodev,errors=remount-ro)
    binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
    /dev/sdb1 on /media/NMT-A-210 type ext3 (rw,nosuid,nodev,uhelper=udisks)
    /dev/sde1 on /media/XBMC#1 type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,b lksize=4096)
    /dev/sr0 on /media/THEPHANTOMMENACE type iso9660 (ro,nosuid,nodev,uid=1000,gid=1000,iocharset=utf8, mode=0400,dmode=0500,uhelper=udisks)

    blank dvd
    xxxx@xxxxxx:~$ mount
    /dev/sda1 on / type ext4 (rw,errors=remount-ro)
    proc on /proc type proc (rw,noexec,nosuid,nodev)
    sysfs on /sys type sysfs (rw,noexec,nosuid,nodev)
    none on /sys/fs/fuse/connections type fusectl (rw)
    none on /sys/kernel/debug type debugfs (rw)
    none on /sys/kernel/security type securityfs (rw)
    udev on /dev type devtmpfs (rw,mode=0755)
    devpts on /dev/pts type devpts (rw,noexec,nosuid,gid=5,mode=0620)
    tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
    none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
    none on /run/shm type tmpfs (rw,nosuid,nodev)
    /dev/sdc1 on /media/sdc1 type ext3 (rw,noexec,nosuid,nodev,errors=remount-ro)
    binfmt_misc on /proc/sys/fs/binfmt_misc type binfmt_misc (rw,noexec,nosuid,nodev)
    /dev/sdb1 on /media/NMT-A-210 type ext3 (rw,nosuid,nodev,uhelper=udisks)
    /dev/sde1 on /media/XBMC#1 type fuseblk (rw,nosuid,nodev,allow_other,default_permissions,b lksize=4096)


    checked fstab file

    # /etc/fstab: static file system information.
    #
    # Use 'blkid -o value -s UUID' to print the universally unique identifier
    # for a device; this may be used with UUID= as a more robust way to name
    # devices that works even if disks are added and removed. See fstab(5).
    #
    # <file system> <mount point> <type> <options> <dump> <pass>
    proc /proc proc nodev,noexec,nosuid 0 0
    /dev/sda1 / ext4 errors=remount-ro 0 1
    # swap was on /dev/sda5 during installation
    UUID=ae568b10-8982-4c44-8a4a-86407f996c9a none swap sw 0 0
    /dev/sdc1 /media/sdc1 ext3 errors=remount-ro,users 0 0

    I am still looking for other clues if you know of anything that i should try or look for let me know
    thanks

    Comment


      #3
      Two thoughts occur to me:

      1) Maybe you have some blank disks that are bad, or just incompatible with your drive.

      2) Even though it may read disks, it could still be a hardware problem - the drive's write laser may have failed, or simply be dirty. If the drive is a few years old, this may be the most likely possibility.
      sigpic
      "Let us think the unthinkable, let us do the undoable, let us prepare to grapple with the ineffable itself, and see if we may not eff it after all."
      -- Douglas Adams

      Comment


        #4
        Originally posted by HalationEffect View Post
        Two thoughts occur to me:

        1) Maybe you have some blank disks that are bad, or just incompatible with your drive.

        2) Even though it may read disks, it could still be a hardware problem - the drive's write laser may have failed, or simply be dirty. If the drive is a few years old, this may be the most likely possibility.


        Well you Just pegged it, as I sit here writing this K3b is burning a disc the answer was number 1, I opened spindle of dvds and pulled out another one threw it in and it is working , now one question how do I mark this as solved, and thank you HalationEffect, here I was looking for a software problem and it was simply a bad disc

        Comment


          #5
          Click on Thread Tools and click on Mark this thread as solved...
          Windows no longer obstructs my view.
          Using Kubuntu Linux since March 23, 2007.
          "It is a capital mistake to theorize before one has data." - Sherlock Holmes

          Comment


            #6
            Originally posted by JohnArgent View Post
            Well you Just pegged it, as I sit here writing this K3b is burning a disc the answer was number 1, I opened spindle of dvds and pulled out another one threw it in and it is working , now one question how do I mark this as solved, and thank you HalationEffect, here I was looking for a software problem and it was simply a bad disc
            Glad to be of help, and also glad it turned out to be bad disks rather than a hardware failure
            sigpic
            "Let us think the unthinkable, let us do the undoable, let us prepare to grapple with the ineffable itself, and see if we may not eff it after all."
            -- Douglas Adams

            Comment


              #7
              Originally posted by HalationEffect View Post
              Glad to be of help, and also glad it turned out to be bad disks rather than a hardware failure
              Yes but the bad thing is that it seems like the discs are not bad exactly Asus 24b1ts dvd writer does not like abunch of the discs in this spindle of TDK, which has never happenned before, but I take the disc out of my new pc and stick it in my older pc with a memorex dvd writer and no problems (bangs head against wall going AAAAAAGGGGHHHHH)

              Comment

              Working...
              X