My bd-re drive is reading only cd

I have Toshiba Qosmio x870-14m with a blueray drive Mat**bleep**a BD-MLT UJ260. For some reason, the drive stop reading dvds.after i reboot the system, it`s recognize the dvd, but after ejecting and put back again, doesn`t work.  i`ve tryed all the solution which i found on web, still no result. i `ve made a system recovery, and was working for a few hours, then again stop reading dvd`s. i went at the center where i bought the laptop, and they they told me it`s a windows issue. a friend bought the same laptop as mine and have the same issue, so i don`t think it`s a hardware problem. in the bd-re properties it`s showing as cd-rom, maybe this is the issue? how do i change that? i`m waiting for suggestions... thank you for your time and sorry for my english!

You can try the Microsoft fixit for CD/DVD drives here - Fix problems with CD or DVD drives that can’t read or write media
If your Toshiba laptop has the Toshiba application installer you can use it to re install your DVD or Blu-ray software.
A system restore is not as thorough as recovering to out of box, reset on Windows 8 and 8.1.
Toshiba would recommend to un install and then re install the software and test, if that does not work you would be suggested to recover to out of box state or reset the laptop and test. If those two things do not work (the software) then it would suggest that it would be a hardware issue. (the Blu-ray drive).  
S70-ABT2N22 Windows 7 Pro & 8.1Pro, C55-A5180 Windows 8.1****Click on White “Kudos” STAR to say thanks!****

Similar Messages

  • My external hard drive is read only

    Hey guys,
    I'm just transferring stuff from a windows pc and i had all my music on my external hard drive. Well i set my default iTunes folder back to my external on my new mac but my hard drive is read only so it won't let me download anything after i buy it. How can i change it from read only?
    Thanks

    If the external drive is formatted NTFS, OSX can read but not write to it.
    MacFUSE is supposed to add NTFS write support to OSX
    <http://julipedia.blogspot.com/2007/03/ntfs-readwrite-support-for-mac-os-x.html> , but it may be safer to copy the data from the drive, the re-format it to Mac Extended (or FAT32 if you still want to use in on Windows). Re-formatting will erase the disk, so save the data first.

  • I am connecting an external USB HDD and I can see it on my Apple Macbook Air. BUT this drive is READ only. How can I write to it?

    I am connecting an external USB HDD and I can see it on my Apple Macbook Air. BUT this drive is READ only. How can I write to it?

    Drive Partition and Format
    1.Open Disk Utility in your Utilities folder.
    2. After DU loads select your hard drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
    3. Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Click on the Options button, set the partition scheme to GUID then click on the OK button. Set the format type to Mac OS Extended (Journaled.) Click on the Partition button and wait until the process has completed.
    4. Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
    5. Set the format type to Mac OS Extended (Journaled.) Click on the Security button, check the button for Zero Data and click on OK to return to the Erase window.
    6. Click on the Erase button. The format process can take up to several hours depending upon the drive size.
    Steps 4-6 are optional but should be used on a drive that has never been formatted before, if the format type is not Mac OS Extended, if the partition scheme has been changed, or if a different operating system (not OS X) has been installed on the drive.

  • Error says my External backup hard drive is read only

    I have a WD External drive that I use for my Time Machine backup. I turned on the computer today and it says it cannot backup because the drive is read only. It appears on the desktop and in the Finder window. When I open Time Machine preferences, it's identified as the backup disk. But when I choose "backup now", I get that message (it's read only).
    Do I have to partition this again using Disk Utility or is there a simpler solution? Thank you,

    See #C6 in [Time Machine - Troubleshooting|http://web.me.com/pondini/Time_Machine/Troubleshooting.html] (or use the link in *User Tips* at the top of this forum).

  • External Hard Drive Becomes Read Only

    I have a LaCie Hard Drive that Time Machine has been backing up to for about 4 days now. All of a sudden, the external hard drive is read only. When I go into Get Info for the hard drive, I can't even change the read/write permissions - it's all grayed out. This is the second time it's happened. The first time was on a Western Digital MyBook. TM fried that drive. At least this drive hasn't disappeared like the last time.
    I've now changed the Time Machine backup to my second hard drive on my Mac Pro (which is screaming along, as opposed to the FW800 [!!] backup on my La Cie, whose file transfers are slo-o-o-w).
    The idea behind backing up onto the external was so that if I ever needed to leave during a fire or earthquake, I could bring this with me and not worry if my computer was destroyed. Insurance would replace the computer, and I could replace my system.
    If it weren't formatted properly, it wouldn't have been backing up for the last few days.
    Can anyone help?
    Message was edited by: Theresa Mesa

    Thank you to everyone who has posted about this issue -- it just happened to me AGAIN this morning (this is my 3rd time), after I installed the 10.5.2 update. The first two times were right after I hooked up my external Iomega 500GB drive to use with Time Machine and I thought it was something I was doing. Then it seemed to work fine for a couple months so I thought the problem was over. Guess not! It is frustrating because I just lost about 2 months worth of backups. So finally I searched Apple's discussion forums and saw that I am not alone. However, no one was really posting a solution other than to say "reformat the drive".
    So I did a Google search about this topic and encountered the following article. I have just gone through the steps he outlines and although I won't know for awhile if it works, I figure at this point it can't hurt to try. I hope this proves useful to others as well. (One note -- in his article, he says to skip the Erase tab and go right to the Partition tab. If you don't see the Partition tab, first erase your corrupt Time Machine backup disk and then follow his steps.)
    http://gizmodo.com/gadgets/apple/leopard-disk-utility-format-issue-screws-with-t ime-machine-but-theres-an-easy-fix-316573.php
    Cheers ~
    Message was edited by: sneebish

  • External hard drive becomes "read only" and won't let Time Machine back up

    I have an external hard drive for back up, and it has been working fine until recently.
    There is a version of 10.6.6 loaded on it also.
    The back up will fail every few days. When I do some checking, the back up drive is "read only" but I am not able to switch it to read/write. I cannot repair it with Disk Utility as the repair buttons are grayed out.
    I can run DiskWarrior and it will fix it, but it runs super slow and takes all the memory to do it. I can barely use my e mail while it's running.
    Anyone know what's going on?

    System log says:
    3/27/11 8:01:19 AM com.apple.backupd-auto[1559] Not starting scheduled Time Machine backup - time machine destination not resolvable.
    It's read only because:
    A: I cannot do repairs under Disk Utility, the buttons are grayed out.
    B: I right click and "Get Info" and if I click on the lock icon, nothing happens.
    C: The disk is not listed in the Time Machine backups.
    I will try to take better notes the next time it happens and give you the exact messages.
    There is another drive daisy chained to this external drive which holds my music. The music drive does not have a Mac OS installed on it and is only for storage. It works properly.

  • How do I change permissions on my seagate expansion drive from read only to read and write?  Thank you!

    I don't seem to be able to change the permissions on my Seagate 1TB Expansion Drive from read only to read and write.
    Are there expansion drives compatible with both Windows and Mac as I have a Windows computer at work and use my Mac at home?
    Thanks

    It is a question of formats.  That drive probably is formatted for Windows.  You will have to reformat it to ExFAT on the PC, then it will work both on the Mac and the PC. 
    REFORMATTING ERASES ALL DATA ON A DISK!
    There is a software option which will allow you to write to the HDD with reformatting:
    http://www.paragon-software.com/home/ntfs-mac/
    Ciao.

  • TS1550 OSX Upgrade (Mountain Lion) turned external drive to "read-only" and now I can not do back-ups on time machine.  How do I fix this?

    I recently upgraded to mountain lion, latest version OS and now my external drives are read-only.  They are formatted Mac OS Extended and I have been using one of them for Time Machine.  How do I fix?
    Thanks

    http://pondini.org/TM/C6.html

  • Time Machine once worked, now external hard drive is "read only"

    I have a 2005 iMac G5, running OS X 10.5. Had some power issues, and reinstalled (and archived) my OS a couple of time.
    Recently purchased Western Digital 1TB external hard drive for back up. It worked once or twice, but now shows "read only" status.
    Disk Utility won't do anything, because it's read only (can't repair, erase, partition or convert).
    Hard drive works on PC running Windows 7, and newer Mac with Snow Leopard, just not the one computer I need it for. Any suggestions?

    This may help:
    What to do if Time Machine reports you don't have permission
    This was posted in the Apple Discussions by V.K. I have only modified it slightly to be more generic.
    The problem seems to be that 10.5.6 changes permissions on a file so that even the root user doesn't have write peivileges. I have no idea why they did this. The workaround suggested in [an]other post will probably work, too, but i did something less drastic. Instead of deleting the file I changed permissions on it, and it worked just fine. An added benefit is that the permission change seems to stick, so you don't have to delete the file every time you change a drive.
    [Open the Terminal application in your Utilities folder. At the prompt [enter] the following command:
    sudo chmod 644 /volumes/"TM drive name"/.xxxxxxxxxxxx
    The name of the file .xxxxxxxxxxxx is based on the MAC address of your computer and will be different for every computer. Put the name of the TM drive in the above and keep the quotes.
    You'll have to enter your admin password (which you won't see) which is normal.
    This was edited by Kappy just for cleanup.
    Enable Finder to Show Invisible Files and Folders
    Open the Terminal application in your Utilities folder. At the prompt enter or paste the following command line then press RETURN.
    defaults write com.apple.finder AppleShowAllFiles TRUE
    To turn off the display of invisible files and folders enter or paste the following command line and press RETURN.
    defaults write com.apple.finder AppleShowAllFiles FALSE
    Alternatively you can use one of the numerous third-party utilities such as TinkerTool or ShowHideInvisibleFiles - VersionTracker or MacUpdate.
    Also visit the User Tips found at the top of this forum's Topics list: Time Machine User Tips.

  • [Solved] Laptop Suspend puts Hard Drive into Read-Only

    My problem is that s2ram brings back X (and the virtual console, if I'm on one), but never the hard drive.
    s2ram -f -a 1 suspends just like s2ram -f. -a 2 and 3 just make a high pitched sound.
    I tried both http://wiki.archlinux.org/index.php/Suspend_to_RAM and http://wiki.archlinux.org/index.php/Pm-utils methods.
    I updated my BIOS drivers but that didn't help
    s2disk works perfectly.
    This is a COMPAQ Presario CQ60-215DX
    Here is my log of the trouble during resume:
    ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    sd 3:0:0:0: [sda] Starting disk
    ata4.00: qc timeout (cmd 0xec)
    ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata4.00: revalidation failed (errno=-5)
    ata3.00: qc timeout (cmd 0xa1)
    ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata3.00: revalidation failed (errno=-5)
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata3.00: qc timeout (cmd 0xa1)
    ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata3.00: revalidation failed (errno=-5)
    ata3: limiting SATA link speed to 1.5 Gbps
    ata4.00: qc timeout (cmd 0xec)
    ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata4.00: revalidation failed (errno=-5)
    ata4: limiting SATA link speed to 1.5 Gbps
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    ata4: SATA link up <unknown> (SStatus 103 SControl 310)
    And my full log:
    Linux version 2.6.30-ARCH (root@T-POWA-LX) (gcc version 4.4.1 (GCC) ) #1 SMP PREEMPT Fri Jul 31 07:30:28 CEST 2009
    Command line: root=/dev/disk/by-uuid/9ae7dfa5-74b2-41e2-89bc-b344bbf47109 ro
    KERNEL supported cpus:
    Intel GenuineIntel
    AMD AuthenticAMD
    Centaur CentaurHauls
    libata version 3.00 loaded.
    pata_amd 0000:00:06.0: version 0.4.1
    pata_amd 0000:00:06.0: setting latency timer to 64
    scsi0 : pata_amd
    scsi1 : pata_amd
    ata1: PATA max UDMA/133 cmd 0x1f0 ctl 0x3f6 bmdma 0x30c0 irq 14
    ata2: PATA max UDMA/133 cmd 0x170 ctl 0x376 bmdma 0x30c8 irq 15
    ahci 0000:00:09.0: version 3.0
    ACPI: PCI Interrupt Link [LSI0] enabled at IRQ 22
    ahci 0000:00:09.0: PCI INT A -> Link[LSI0] -> GSI 22 (level, low) -> IRQ 22
    ahci 0000:00:09.0: irq 25 for MSI/MSI-X
    ahci 0000:00:09.0: AHCI 0001.0200 32 slots 2 ports 3 Gbps 0x3 impl IDE mode
    ahci 0000:00:09.0: flags: 64bit ncq sntf led clo pmp pio slum part
    ahci 0000:00:09.0: setting latency timer to 64
    scsi2 : ahci
    scsi3 : ahci
    ata3: SATA max UDMA/133 abar m8192@0xc0004000 port 0xc0004100 irq 25
    ata4: SATA max UDMA/133 abar m8192@0xc0004000 port 0xc0004180 irq 25
    ata2: port disabled. ignoring.
    Clocksource tsc unstable (delta = 4397486409693 ns)
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata4.00: ATA-8: TOSHIBA MK2555GSX, FG002C, max UDMA/100
    ata4.00: 488397168 sectors, multi 16: LBA48 NCQ (depth 31/32)
    ata4.00: configured for UDMA/100
    ata3.00: ATAPI: Optiarc DVD RW AD-7580S, FH03, max UDMA/100
    ata3.00: configured for UDMA/100
    scsi 2:0:0:0: CD-ROM Optiarc DVD RW AD-7580S FH03 PQ: 0 ANSI: 5
    scsi 3:0:0:0: Direct-Access ATA TOSHIBA MK2555GS FG00 PQ: 0 ANSI: 5
    Driver 'sr' needs updating - please use bus_type methods
    sr0: scsi3-mmc drive: 24x/24x writer dvd-ram cd/rw xa/form2 cdda tray
    Uniform CD-ROM driver Revision: 3.20
    sr 2:0:0:0: Attached scsi CD-ROM sr0
    Driver 'sd' needs updating - please use bus_type methods
    sd 3:0:0:0: [sda] 488397168 512-byte hardware sectors: (250 GB/232 GiB)
    sd 3:0:0:0: [sda] Write Protect is off
    sd 3:0:0:0: [sda] Mode Sense: 00 3a 00 00
    sd 3:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
    sda: sda1 sda2 sda3 < sda5 > sda4
    sd 3:0:0:0: [sda] Attached SCSI disk
    EXT4-fs: INFO: recovery required on readonly filesystem.
    EXT4-fs: write access will be enabled during recovery.
    EXT4-fs: barriers enabled
    kjournald2 starting: pid 569, dev sda2:8, commit interval 5 seconds
    EXT4-fs: delayed allocation enabled
    EXT4-fs: file extents enabled
    EXT4-fs: mballoc enabled
    EXT4-fs: sda2: orphan cleanup on readonly fs
    ext4_orphan_cleanup: deleting unreferenced inode 148384
    ext4_orphan_cleanup: deleting unreferenced inode 147907
    ext4_orphan_cleanup: deleting unreferenced inode 147903
    EXT4-fs: sda2: 3 orphan inodes deleted
    EXT4-fs: recovery complete.
    EXT4-fs: mounted filesystem sda2 with ordered data mode
    rtc_cmos 00:06: RTC can wake from S4
    rtc_cmos 00:06: rtc core: registered rtc_cmos as rtc0
    rtc0: alarms up to one year, y3k, 114 bytes nvram, hpet irqs
    udev: starting version 141
    pci_hotplug: PCI Hot Plug PCI Core version: 0.5
    shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
    usbcore: registered new interface driver usbfs
    usbcore: registered new interface driver hub
    ACPI: AC Adapter [ADP1] (on-line)
    forcedeth: Reverse Engineered nForce ethernet driver. Version 0.64.
    ACPI: PCI Interrupt Link [LMAC] enabled at IRQ 21
    forcedeth 0000:00:0a.0: PCI INT A -> Link[LMAC] -> GSI 21 (level, low) -> IRQ 21
    forcedeth 0000:00:0a.0: setting latency timer to 64
    sr 2:0:0:0: Attached scsi generic sg0 type 5
    sd 3:0:0:0: Attached scsi generic sg1 type 0
    usbcore: registered new device driver usb
    ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
    ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
    cfg80211: Calling CRDA to update world regulatory domain
    input: Power Button as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
    ACPI: Power Button [PWRF]
    input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input3
    ACPI: Lid Switch [LID0]
    input: Sleep Button as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input4
    ACPI: Sleep Button [SLPB]
    input: Power Button as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input5
    ACPI: Power Button [PWRB]
    processor ACPI_CPU:00: registered as cooling_device0
    processor ACPI_CPU:01: registered as cooling_device1
    forcedeth 0000:00:0a.0: ifname eth0, PHY OUI 0x732 @ 1, addr 00:1f:16:74:cb:72
    forcedeth 0000:00:0a.0: highdma csum pwrctl mgmt lnktim msi desc-v3
    ACPI: PCI Interrupt Link [LUS2] enabled at IRQ 17
    ehci_hcd 0000:00:02.1: PCI INT B -> Link[LUS2] -> GSI 17 (level, low) -> IRQ 17
    ehci_hcd 0000:00:02.1: setting latency timer to 64
    ehci_hcd 0000:00:02.1: EHCI Host Controller
    ehci_hcd 0000:00:02.1: new USB bus registered, assigned bus number 1
    ehci_hcd 0000:00:02.1: debug port 1
    ehci_hcd 0000:00:02.1: cache line size of 64 is not supported
    ehci_hcd 0000:00:02.1: irq 17, io mem 0xc0007000
    ACPI: WMI: Mapper loaded
    ehci_hcd 0000:00:02.1: USB 2.0 started, EHCI 1.00
    usb usb1: configuration #1 chosen from 1 choice
    hub 1-0:1.0: USB hub found
    hub 1-0:1.0: 3 ports detected
    i2c-adapter i2c-0: nForce2 SMBus adapter at 0x3040
    i2c-adapter i2c-1: nForce2 SMBus adapter at 0x3000
    ACPI: PCI Interrupt Link [LUS0] enabled at IRQ 17
    ohci_hcd 0000:00:02.0: PCI INT A -> Link[LUS0] -> GSI 17 (level, low) -> IRQ 17
    ohci_hcd 0000:00:02.0: setting latency timer to 64
    ohci_hcd 0000:00:02.0: OHCI Host Controller
    ohci_hcd 0000:00:02.0: new USB bus registered, assigned bus number 2
    ohci_hcd 0000:00:02.0: irq 17, io mem 0xc0006000
    usb usb2: configuration #1 chosen from 1 choice
    hub 2-0:1.0: USB hub found
    hub 2-0:1.0: 3 ports detected
    ACPI: PCI Interrupt Link [Z011] enabled at IRQ 16
    ehci_hcd 0000:00:04.1: PCI INT B -> Link[Z011] -> GSI 16 (level, low) -> IRQ 16
    ehci_hcd 0000:00:04.1: setting latency timer to 64
    ehci_hcd 0000:00:04.1: EHCI Host Controller
    ehci_hcd 0000:00:04.1: new USB bus registered, assigned bus number 3
    ehci_hcd 0000:00:04.1: debug port 1
    ehci_hcd 0000:00:04.1: cache line size of 64 is not supported
    ehci_hcd 0000:00:04.1: irq 16, io mem 0xc0007400
    ehci_hcd 0000:00:04.1: USB 2.0 started, EHCI 1.00
    usb usb3: configuration #1 chosen from 1 choice
    hub 3-0:1.0: USB hub found
    hub 3-0:1.0: 4 ports detected
    ACPI: PCI Interrupt Link [Z010] enabled at IRQ 16
    ohci_hcd 0000:00:04.0: PCI INT A -> Link[Z010] -> GSI 16 (level, low) -> IRQ 16
    ohci_hcd 0000:00:04.0: setting latency timer to 64
    ohci_hcd 0000:00:04.0: OHCI Host Controller
    ohci_hcd 0000:00:04.0: new USB bus registered, assigned bus number 4
    ohci_hcd 0000:00:04.0: irq 16, io mem 0xc0008000
    usb usb4: configuration #1 chosen from 1 choice
    hub 4-0:1.0: USB hub found
    hub 4-0:1.0: 4 ports detected
    thermal LNXTHERM:01: registered as thermal_zone0
    ACPI: Thermal Zone [TZS0] (68 C)
    ACPI: Battery Slot [BAT0] (battery present)
    thermal LNXTHERM:02: registered as thermal_zone1
    ACPI: Thermal Zone [TZS1] (68 C)
    usb 1-1: new high speed USB device using ehci_hcd and address 2
    nvidia: module license 'NVIDIA' taints kernel.
    Disabling lock debugging due to kernel taint
    usb 1-1: configuration #1 chosen from 1 choice
    Synaptics Touchpad, model: 1, fw: 7.0, id: 0x1a0b1, caps: 0xd04711/0xa00000
    acpi device:13: registered as cooling_device2
    input: Video Bus as /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:10/device:11/input/input6
    ACPI: Video Device [VGA] (multi-head: yes rom: no post: no)
    usb 3-4: new high speed USB device using ehci_hcd and address 2
    input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio2/input/input7
    ath5k 0000:07:00.0: PCI INT A -> Link[Z012] -> GSI 23 (level, low) -> IRQ 23
    ath5k 0000:07:00.0: setting latency timer to 64
    ath5k 0000:07:00.0: registered as 'phy0'
    usb 3-4: configuration #1 chosen from 1 choice
    ACPI: PCI Interrupt Link [LGPU] enabled at IRQ 20
    nvidia 0000:02:00.0: PCI INT A -> Link[LGPU] -> GSI 20 (level, low) -> IRQ 20
    nvidia 0000:02:00.0: setting latency timer to 64
    NVRM: loading NVIDIA UNIX x86_64 Kernel Module 185.18.31 Tue Jul 28 17:52:27 PDT 2009
    EXT4 FS on sda2, internal journal on sda2:8
    Adding 3148700k swap on /dev/sda5. Priority:-1 extents:1 across:3148700k
    scsi 4:0:0:0: Direct-Access Generic- Multi-Card 1.00 PQ: 0 ANSI: 0 CCS
    sd 4:0:0:0: Attached scsi generic sg2 type 0
    usb-storage: device scan complete
    sd 4:0:0:0: [sdb] Attached SCSI removable disk
    scsi 5:0:0:0: Direct-Access USB Driver 0.00 PQ: 0 ANSI: 0 CCS
    sd 5:0:0:0: Attached scsi generic sg3 type 0
    usb-storage: device scan complete
    sd 5:0:0:0: [sdc] 7827456 512-byte hardware sectors: (4.00 GB/3.73 GiB)
    sd 5:0:0:0: [sdc] Write Protect is off
    sd 5:0:0:0: [sdc] Mode Sense: 23 00 00 00
    sd 5:0:0:0: [sdc] Assuming drive cache: write through
    sd 5:0:0:0: [sdc] Assuming drive cache: write through
    sdc:
    sd 5:0:0:0: [sdc] Attached SCSI removable disk
    forcedeth 0000:00:0a.0: irq 26 for MSI/MSI-X
    eth0: no link during initialization.
    NET: Registered protocol family 10
    lo: Disabled Privacy Extensions
    ADDRCONF(NETDEV_UP): eth0: link is not ready
    PM: Syncing filesystems ... done.
    Freezing user space processes ... (elapsed 0.00 seconds) done.
    Freezing remaining freezable tasks ... (elapsed 0.00 seconds) done.
    Suspending console(s) (use no_console_suspend to debug)
    sd 3:0:0:0: [sda] Synchronizing SCSI cache
    sd 3:0:0:0: [sda] Stopping disk
    ath5k 0000:07:00.0: PCI INT A disabled
    forcedeth 0000:00:0a.0: wake-up capability disabled by ACPI
    forcedeth 0000:00:0a.0: PME# disabled
    forcedeth 0000:00:0a.0: PCI INT A disabled
    HDA Intel 0000:00:07.0: PCI INT A disabled
    ata2: port disabled. ignoring.
    ehci_hcd 0000:00:04.1: PCI INT B disabled
    ehci_hcd 0000:00:04.1: PME# disabled
    ohci_hcd 0000:00:04.0: PCI INT A disabled
    ohci_hcd 0000:00:04.0: PME# disabled
    ehci_hcd 0000:00:02.1: PCI INT B disabled
    ehci_hcd 0000:00:02.1: PME# disabled
    ohci_hcd 0000:00:02.0: PCI INT A disabled
    ohci_hcd 0000:00:02.0: PME# disabled
    ACPI: Preparing to enter system sleep state S3
    Disabling non-boot CPUs ...
    CPU 1 is now offline
    SMP alternatives: switching to UP code
    CPU0 attaching NULL sched-domain.
    CPU1 attaching NULL sched-domain.
    CPU0 attaching NULL sched-domain.
    CPU1 is down
    Extended CMOS year: 2000
    x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
    Back to C!
    Extended CMOS year: 2000
    Enabling non-boot CPUs ...
    SMP alternatives: switching to SMP code
    Booting processor 1 APIC 0x1 ip 0x6000
    Initializing CPU#1
    Calibrating delay using timer specific routine.. 4001.76 BogoMIPS (lpj=6666816)
    CPU: L1 I Cache: 64K (64 bytes/line), D cache 64K (64 bytes/line)
    CPU: L2 Cache: 512K (64 bytes/line)
    CPU: Physical Processor ID: 0
    CPU: Processor Core ID: 1
    x86 PAT enabled: cpu 1, old 0x7040600070406, new 0x7010600070106
    CPU1: AMD Athlon Dual-Core QL-62 stepping 01
    CPU0 attaching NULL sched-domain.
    Switched to high resolution mode on CPU 1
    CPU0 attaching sched-domain:
    domain 0: span 0-1 level MC
    groups: 0 1
    CPU1 attaching sched-domain:
    domain 0: span 0-1 level MC
    groups: 1 0
    CPU1 is up
    ACPI: Waking up from system sleep state S3
    ohci_hcd 0000:00:02.0: restoring config space at offset 0x1 (was 0xb00007, writing 0xb00003)
    ehci_hcd 0000:00:02.1: restoring config space at offset 0x1 (was 0xb00006, writing 0xb00002)
    ohci_hcd 0000:00:04.0: restoring config space at offset 0x1 (was 0xb00007, writing 0xb00003)
    ehci_hcd 0000:00:04.1: restoring config space at offset 0x1 (was 0xb00006, writing 0xb00002)
    pata_amd 0000:00:06.0: restoring config space at offset 0x1 (was 0xb00005, writing 0xb80005)
    HDA Intel 0000:00:07.0: restoring config space at offset 0xf (was 0x5020100, writing 0x502010a)
    HDA Intel 0000:00:07.0: restoring config space at offset 0x4 (was 0x0, writing 0xc0000000)
    HDA Intel 0000:00:07.0: restoring config space at offset 0x1 (was 0xb00000, writing 0xb00002)
    ahci 0000:00:09.0: restoring config space at offset 0x1 (was 0xb00007, writing 0xb00407)
    pcieport-driver 0000:00:14.0: restoring config space at offset 0x7 (was 0x1f1, writing 0x200001f1)
    pcieport-driver 0000:00:14.0: restoring config space at offset 0x1 (was 0x100107, writing 0x1005
    nvidia 0000:02:00.0: restoring config space at offset 0xf (was 0x100, writing 0x10a)
    nvidia 0000:02:00.0: restoring config space at offset 0x9 (was 0x1, writing 0x4001)
    nvidia 0000:02:00.0: restoring config space at offset 0x7 (was 0xc, writing 0xc400000c)
    nvidia 0000:02:00.0: restoring config space at offset 0x5 (was 0xc, writing 0xd000000c)
    ath5k 0000:07:00.0: restoring config space at offset 0x3 (was 0x0, writing 0x10)
    nForce2_smbus 0000:00:01.1: PME# disabled
    ohci_hcd 0000:00:02.0: PME# disabled
    ohci_hcd 0000:00:02.0: PCI INT A -> Link[LUS0] -> GSI 17 (level, low) -> IRQ 17
    ohci_hcd 0000:00:02.0: setting latency timer to 64
    ohci_hcd 0000:00:02.0: PME# disabled
    ehci_hcd 0000:00:02.1: PME# disabled
    ehci_hcd 0000:00:02.1: PCI INT B -> Link[LUS2] -> GSI 17 (level, low) -> IRQ 17
    ehci_hcd 0000:00:02.1: setting latency timer to 64
    ehci_hcd 0000:00:02.1: PME# disabled
    usb usb1: root hub lost power or was reset
    ehci_hcd 0000:00:02.1: debug port 1
    ehci_hcd 0000:00:02.1: cache line size of 64 is not supported
    ohci_hcd 0000:00:04.0: PME# disabled
    ohci_hcd 0000:00:04.0: PCI INT A -> Link[Z010] -> GSI 16 (level, low) -> IRQ 16
    ohci_hcd 0000:00:04.0: setting latency timer to 64
    ohci_hcd 0000:00:04.0: PME# disabled
    ehci_hcd 0000:00:04.1: PME# disabled
    ehci_hcd 0000:00:04.1: PCI INT B -> Link[Z011] -> GSI 16 (level, low) -> IRQ 16
    ehci_hcd 0000:00:04.1: setting latency timer to 64
    ehci_hcd 0000:00:04.1: PME# disabled
    usb usb3: root hub lost power or was reset
    ehci_hcd 0000:00:04.1: debug port 1
    ehci_hcd 0000:00:04.1: cache line size of 64 is not supported
    pata_amd 0000:00:06.0: restoring config space at offset 0x1 (was 0xb00005, writing 0xb80005)
    pata_amd 0000:00:06.0: setting latency timer to 64
    ata2: port disabled. ignoring.
    HDA Intel 0000:00:07.0: PCI INT A -> Link[LAZA] -> GSI 19 (level, low) -> IRQ 19
    HDA Intel 0000:00:07.0: setting latency timer to 64
    pci 0000:00:08.0: setting latency timer to 64
    ahci 0000:00:09.0: setting latency timer to 64
    forcedeth 0000:00:0a.0: wake-up capability disabled by ACPI
    forcedeth 0000:00:0a.0: PME# disabled
    ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    forcedeth 0000:00:0a.0: irq 26 for MSI/MSI-X
    eth0: no link during initialization.
    pci 0000:00:0b.0: setting latency timer to 64
    ath5k 0000:07:00.0: PCI INT A -> Link[Z012] -> GSI 23 (level, low) -> IRQ 23
    sd 3:0:0:0: [sda] Starting disk
    ata4.00: qc timeout (cmd 0xec)
    ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata4.00: revalidation failed (errno=-5)
    ata3.00: qc timeout (cmd 0xa1)
    ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata3.00: revalidation failed (errno=-5)
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
    ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
    ata3.00: qc timeout (cmd 0xa1)
    ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata3.00: revalidation failed (errno=-5)
    ata3: limiting SATA link speed to 1.5 Gbps
    ata4.00: qc timeout (cmd 0xec)
    ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata4.00: revalidation failed (errno=-5)
    ata4: limiting SATA link speed to 1.5 Gbps
    ata3: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
    ata4: SATA link up <unknown> (SStatus 103 SControl 310)
    ata4.00: qc timeout (cmd 0xec)
    ata4.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata4.00: revalidation failed (errno=-5)
    ata4.00: disabled
    ata3.00: qc timeout (cmd 0xa1)
    ata3.00: failed to IDENTIFY (I/O error, err_mask=0x4)
    ata3.00: revalidation failed (errno=-5)
    ata3.00: disabled
    sd 3:0:0:0: [sda] START_STOP FAILED
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 134590273
    Buffer I/O error on device sda2, logical block 1094141
    lost page write due to I/O error on sda2
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 135807281
    Buffer I/O error on device sda2, logical block 1246267
    lost page write due to I/O error on sda2
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 135815833
    Buffer I/O error on device sda2, logical block 1247336
    lost page write due to I/O error on sda2
    JBD2: Detected IO errors while flushing file data on sda2:8
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 155463993
    Aborting journal on device sda2:8.
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 155459417
    Buffer I/O error on device sda2, logical block 3702784
    lost page write due to I/O error on sda2
    JBD2: I/O error detected when updating journal superblock for sda2:8.
    PM: Device 3:0:0:0 failed to resume: error 262144
    usb 1-1: reset high speed USB device using ehci_hcd and address 2
    usb 3-4: reset high speed USB device using ehci_hcd and address 2
    Restarting tasks ... <2>ext4_abort called.
    EXT4-fs error (device sda2): ext4_journal_start_sb: Detected aborted journal
    Remounting filesystem read-only
    ext4_da_writepages: jbd2_start: 1024 pages, ino 131086; err -30
    Pid: 20, comm: pdflush Tainted: P 2.6.30-ARCH #1
    Call Trace:
    [<ffffffffa00d738d>] ? ext4_da_writepages+0x47d/0x4b0 [ext4]
    [<ffffffff8026c6a4>] ? bit_waitqueue+0x24/0xe0
    [<ffffffff802c8332>] ? do_writepages+0x32/0x60
    [<ffffffff80321b7a>] ? __writeback_single_inode+0xba/0x490
    [<ffffffff802406e6>] ? dequeue_task_fair+0x56/0x1d0
    [<ffffffff8020a95c>] ? __switch_to+0xdc/0x3b0
    [<ffffffff803223b3>] ? generic_sync_sb_inodes+0x193/0x530
    [<ffffffff803229c5>] ? writeback_inodes+0x65/0x120
    [<ffffffff802c85a6>] ? wb_kupdate+0xc6/0x160
    [<ffffffff802c995b>] ? pdflush+0x16b/0x2a0
    [<ffffffff802c84e0>] ? wb_kupdate+0x0/0x160
    [<ffffffff802c97f0>] ? pdflush+0x0/0x2a0
    [<ffffffff802c97f0>] ? pdflush+0x0/0x2a0
    [<ffffffff8026c204>] ? kthread+0x64/0xc0
    [<ffffffff8024af20>] ? schedule_tail+0x30/0x80
    [<ffffffff8020d4fa>] ? child_rip+0xa/0x20
    [<ffffffff8026c1a0>] ? kthread+0x0/0xc0
    [<ffffffff8020d4f0>] ? child_rip+0x0/0x20
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126637417
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126637417
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126637417
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126637417
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126637417
    done.
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 130097993
    EXT4-fs error (device sda2): ext4_find_entry: reading directory #139292 offset 0
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126637417
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126004889
    EXT4-fs error (device sda2): ext4_find_entry: reading directory #98457 offset 0
    sd 3:0:0:0: [sda] Unhandled error code
    sd 3:0:0:0: [sda] Result: hostbyte=0x04 driverbyte=0x00
    end_request: I/O error, dev sda, sector 126004889
    EXT4-fs error (device sda2): ext4_find_entry: reading directory #98457 offset 0
    ANY help would be much appreciated.
    Last edited by Cappy (2009-08-10 08:19:09)

    Nevermind .. *sigh* ... pci=msi on the kernel fixed it .. going to go cut myself now ...

  • I need a step-by-step plan: my WD external hard drive is 'read only'

    Hi,
    I hope someone can help me, because i'm in quite a pickle. I bought a WD 500 GB external hard drive a couple of months ago. I have a MacBook Pro version OS X 10.8.5. The problem I have now is that I haven't used my external hard drive for a couple of weeks now, until today (note: I bought this hard drive and used it for the first time on my macbook pro, never on windows before or any other laptop/pc), and all of a sudden I can only 'read' my hard drive, it suddenly seemed to have changed it settings by itself to 'you can read only' whilst I never did anything to the permission settings....
    So i read a couple of questions about this online, and apparently im not the only one with this problem. but all the answers i read are way too complicated for me, with too much computer jargon. Therefore i just need a simple step-by-step answer, whatever i need to install or 'configure' in order to make this thing work again!!
    Please can somebody help me??? I never used this thing for more than a month and only my macbook pro....help!! It cant be that i used this hard drive once and then all of a sudden it changes it's settings??
    Thanks,
    Daphne

    If you can see the hard drive in Finder, select it, do a Get Info (command - I) and see what permissions you have in Sharing and Permissions. It should be Read/Write. If it isn't, unlock the padlock, and change it. Then look towards the top to see how the drive is formatted. It normally should be Mac OS Extended (Journaled).
    If it is not that format, go to Applications/Utilities/Disk Utility. Open Disk Utility select the drive, select the erase partition, and after making sure the correct format is set, erase the drive. At the bottom the current format is shown. This will remove anything that was on the drive.

  • [SOLVED] Strange Hard Drive Errors - Read Only Filesystem?

    Solution: Discard old laptop, buy new laptop
    I have an Acer Aspire 5103WLMi. For about 2 months now, Arch has been running smoothly. Until 2 weeks ago.
    It all started when I tried to install and configure autofs on Arch x86_64. On the next reboot, all manner of errors were printed to the screen, to the effect that the internal hard drive was only being mounted read-only, rendering the system unusable. I tried to find a solution, but there were no references to read-only anywhere; fstab, grub etc. None that I could find.
    I tried reinstalling. However, x86_64 Arch refused to boot properly first time due to the exact same error; and I *know* that I'm configuring everything correctly. I managed (somehow) to coerce i686 Arch to install, and things "work".
    Seemingly out of the blue, during normal operation, all running applications will stop, and spit out error after error to the effect of "Cannot Write to Read Only Filesystem!". Sakura won't load (Input/Output error, apparently), and the only way to shut down the laptop is a hard reset (I can't log in as root or use sudo because it wants to write to the filesystem first, which it obviously can't.
    Now, I'm going to be giving the insides of this laptop a good cleanout this weekend, and I'm in the process of backing up all of my data, but I was wondering if anyone else has come across a similar form of misbehaviour; or (with a bit of luck) some potential solutions?
    This is very peculiar, because there seems to be no reason why the laptop suddenly loses write permissions to the hard drive. Cheers.
    Edit: I think I should point out that my /boot partition is Ext2, and / and /home are Ext3
    Last edited by aphirst (2013-03-27 14:51:38)

    Smartctl gives me the impression it's my Hard Drive:
    SMART Attributes Data Structure revision number: 16
    Vendor Specific SMART Attributes with Thresholds:
    ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE
    1 Raw_Read_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
    2 Throughput_Performance 0x0005 100 100 050 Pre-fail Offline - 0
    3 Spin_Up_Time 0x0027 100 100 001 Pre-fail Always - 1711
    4 Start_Stop_Count 0x0032 100 100 000 Old_age Always - 6194
    5 Reallocated_Sector_Ct 0x0033 100 100 050 Pre-fail Always - 0
    7 Seek_Error_Rate 0x000b 100 100 050 Pre-fail Always - 0
    8 Seek_Time_Performance 0x0005 100 100 050 Pre-fail Offline - 0
    9 Power_On_Hours 0x0032 092 092 000 Old_age Always - 3291
    10 Spin_Retry_Count 0x0033 223 100 030 Pre-fail Always - 0
    12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 1218
    192 Power-Off_Retract_Count 0x0032 100 100 000 Old_age Always - 294
    193 Load_Cycle_Count 0x0032 088 088 000 Old_age Always - 123904
    194 Temperature_Celsius 0x0022 100 100 000 Old_age Always - 34 (Lifetime Min/Max 15/62)
    196 Reallocated_Event_Count 0x0032 100 100 000 Old_age Always - 0
    197 Current_Pending_Sector 0x0032 100 100 000 Old_age Always - 0
    198 Offline_Uncorrectable 0x0030 100 100 000 Old_age Offline - 0
    199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 17
    220 Disk_Shift 0x0002 100 100 000 Old_age Always - 118
    222 Loaded_Hours 0x0032 094 094 000 Old_age Always - 2425
    223 Load_Retry_Count 0x0032 100 100 000 Old_age Always - 0
    224 Load_Friction 0x0022 100 100 000 Old_age Always - 0
    226 Load-in_Time 0x0026 100 100 000 Old_age Always - 444
    240 Head_Flying_Hours 0x0001 100 100 001 Pre-fail Offline - 0
    Everything being either Old_age or Pre-fail is not encouraging. Additionally, in the output is what I believe to be records of what caused my strange read-only behaviour:
    Error 19 occurred at disk power-on lifetime: 3287 hours (136 days + 23 hours)
    When the command that caused the error occurred, the device was active or idle.
    After command completion occurred, registers were:
    ER ST SC SN CL CH DH
    84 51 01 11 18 6a e1 Error: ICRC, ABRT 1 sectors at LBA = 0x016a1811 = 23730193
    Commands leading to the command that caused the error were:
    CR FR SC SN CL CH DH DC Powered_Up_Time Command/Feature_Name
    c8 00 48 c4 17 6a e1 00 04:43:08.023 READ DMA
    c8 00 48 14 e3 69 e1 00 04:43:08.022 READ DMA
    c8 00 a0 5c e2 69 e1 00 04:43:08.010 READ DMA
    c8 00 08 9c e5 69 e1 00 04:43:08.010 READ DMA
    c8 00 20 5c e5 69 e1 00 04:43:08.009 READ DMA
    Could this truly be referring to my problem, since the 'logs' show that the *exact same* error occurred many times.
    Not that this tells me how to fix it...
    Well, if anyone knows if there is a solution, I'd love to know. If the only solution is to ditch the Hard Drive, fair enough. Either way: I'm backing up all of my important data ASAP.
    Cheers.
    Oh, and kclive18, after I noticed that I couldn't get onto my Drive, I reinstalled arch, leaving no trace of /etc/autofs/auto.media.
    Additionally, somehow I have now been able to install Arch x86_64, but the problems still occur...

  • External Hard Drive is read only?? how do i change this?

    ive just gotten a new external hard drive which i use a giant usb pretty much,
    only problem is when i drag files into it to copy it tells me that "untitled" cant be modified.. also when i check its info im told that it is read only... how do figure out how to change this...
    i need help please

    Hi jami01
    You need to reformat your new external drive in Disk Utility. Currently it will be formatted as NTFS which is a windows format and the Mac can read that but not write to it, hence your problems.
    If you wish to use it solely with your Mac and not share it with a PC, then then choose the HFS+ format
    Open Disk Utility,
    -Select the external disk in the left panel. make sure you have selected the correct disk.
    -Click the Erase tab
    -Give the disk a name
    -Select the Volume Format type to be HFS+
    -Click Erase
    If you wish to share it with a PC then Choose MS-DOS(FAT32) format
    regards roam

  • TM drive became read-only, only to be fixed by Verify Disk ?!?!

    Could one of you experts out there please explain this to me. My small brain can't wrap my mind around what happened -
    Yesterday I had to restore my system from a TM backup. After this, I decided to erase the TM drive and start backing up fresh. I did this, and for the past 5 hours, Time Machine has been happily backing up to this newly-erased partition.
    However, just a few minutes ago, I got an error message from TM. It said that the backup couldn't be completed because the volume was "read only". I couldn't believe this, so I checked out Get Info, and indeed it said that I only had read access to the volume that Time machine's been writing to for the past 5 hours! I found the KB article HT3275 that said to do a Repair on the TM drive. But Repair Disk was grayed out; only Verify Disk was lit.
    I checked around further, and couldn't come up with what caused this change in permissions, so I decided to do the Verify Disk just to see if there were any HD errors, but the partition came up clean. But then I couldn't believe my eyes - the Repair Disk button was now active! I switched back to Finder and did a Get Info on the TM partition, and it was back to allowing me Read/Write access!
    How could a Verify Disk operation cause the permissions to change from Read Only to Read/Write? The only system operation I did during those 5 hours of good TM backups was to change my Computer Name and uncheck "Use dynamic global hostname".
    Please, one of you Time Machine/OS X/UNIX gurus explain to this feeble mind what occurred here. I really need to know so that this won't happen again.
    Thanks.

    I tried running
    sudo fsck /dev/sdb1
    and got the following error:
    fsck from util-linux-ng 2.18
    fsck: fsck.ntfs: not found
    fsck: Error 2 while executing fsck.ntfs for /dev/sdb1

  • External drive is read only under mountain lion?

    I have a firewire external drive which is used for Time Machine backups and my iPhoto + iTunes libraries.
    Since installing Mountain Lion, the disc is now reported to be Read Only, meaning none of the three uses above work.
    A quick google search shows that I am not the only one with this roblem.
    Has anyone got any suggestions? Rebooting & remounting the drive both fail to help.
    Looks like a ML bug....
    Omar

    I had the same problem.  Right click on the drive and hit "Get Info".  Under "Sharing and Permissions" make sure everone, especially "everyone" is labeled "read & write".  I did this and it works now.
    Spencer

  • Successful backup, now TM says drive is "read-only"

    Here's my story:
    On Sunday I upgraded my relatively new MacBook Pro (meaning, I haven't had it long enough to install any wonky third party applications) from 10.4 to Leopard. TM was one of my primary motivators for the upgrade. I plugged my brand new 500GB MyBook external FW drive in to my older 400GB MyBook FW drive, and plugged that into the laptop. I'd had the older drive formatted for Mac by the eBay seller and use it to store movies and such. I got the 500 off the shelf at Costco.
    My internal hard drive name has a space in it, but in file sharing the computer name does not have any non alpha characters.
    I launched TM and pointed it to the new drive as the backup location. It said the drive had to be formatted. I was not surprised. I told it to go ahead.
    It finished in a reasonable amount of time, naming the drive "Time Machine Backup" (or something similar, with spaces in the name) and started making the initial backup. I proceded to play a couple hours of World of Warcraft (but that's another forum while it worked. It was still going when I called it a night, but it was making progress backing up about 100GB.
    In the morning it was done. No error messages. I accessed the freaky stargate display and saw tons of backed up files and applications. Good so far. I shut the computer down and headed for work where I'm forced to use an HP and Windows.
    After booting up last night TM displayed a message (I'm paraphrasing here since I'm at work now): "Backup Failed -- backup disc is read only."
    Huh?
    I did "Get Info" on the disc and it says I have read/write access. Guests have read only. I was not able to change these permissions (the Get Info window is locked).
    I brought up Disc Utility thinking to fix permissions. I can only fix permissions on the internal drive, this option is greyed out for both externals. I verified permissions on the main drive, just to be safe. No issues found.
    I changed the FW daisy chain, putting the 500GB drive first so it's directly connected to the computer. No luck, didn't really expect it.
    I dragged a file from the main drive over to the backup drive. It copied. I trashed it from the backup drive. It trashed. Definitely read/write.
    Key Questions:
    Obviously I can read and write to the drive, so why can't TM?
    What do I do to fix it?
    Secondary Questions:
    The system offered to format the drive and I let it. If drive format is the problem here (which seems to be the case with others having problems), why the heck wouldn't the system format it correctly?
    If spaces in the drive name are a problem (perhaps they aren't), why would it use a name that has them?

    Okay everyone, I think I have found the solution, especially if you are seeing the "Unknown" user in your Get Info window's Sharing & Permissions setting for your external drive.
    I had written earlier about my work-around for getting my drobo to work right after getting the "read-only" error from Time Machine. But unfortunately it was a temporary and temperamental fix. There were times then I had to eject the disk and launch Disk Utility to run a repair on the disk which would take more than half an hour on my drobo. But all the while my permissions had this "Unknown" user. Well I decided to "Go UNIX" and see if I could fix this problem once and for all.
    I opened up Terminal and typed "*ls -la /Volumes*". This gives me a directory listing of my mounted drive volumes. I noticed that all of my drives, internal, external, USB and FireWire, all had "root" as the user and "admin" as the group, _EXCEPT for my drobo!_ So I forced it to conform by changing it manually by typing "*sudo chown root:admin /Volumes/Drobo\ Backup\ HD/*".
    sudo = temporarily enables root mode by asking for your password before executing.
    chown = changes ownership to...
    root:admin = "root" is the user and "admin" is the group.
    */Volumes/Drobo\ Backup\ HD/* = My drobo drive is named "*Drobo Backup HD*", but UNIX sees spaces as command separators, so you have to use the "\ " to signify spaces within a name.
    After doing this over a week ago, _I have not had any other problems_ with using my drobo as a backup drive. It has never come up with the "read-only" error in Time Machine, the Sharing & Permissions setting do not have any "Unknown" users or groups, I don't even need to wait for my drobo before logging in like I did in the past. I just boot my Mac and everything with my drobo and Time Machine just works... No problems!
    For me, this seems to be permanently fixed!
    But please let me and the rest of us know if you try this solution, and if it works for you.

Maybe you are looking for

  • Reports permission in Project server 2010

    Hi, I have reports created in SSRS, i need to bring those reports to Project Server PWA. How to do that? i need the steps. Reports like Number of active resources working in Project, Number of projects in that PWA instance. My requirement is, i have

  • Web Console install error

    Hello All, Every time i try to install the Web Console i get the error  ( Please see the attach). Any one have see this issue before ?

  • Old Issue Resurfaces: "Jaggies"

    When importing still images from iPhoto I would apply the "Ken Burns Effect" during import to eliminate the pixelizing or "Jaggies" appearance. Worked Great, but this no longer seems to be working during import of stills. ...Anyone have a suggestion,

  • Where to post feature requests?

    There are some features I'd love to see in the next Nano or software update. Is there a specific place to post feature requests? Thanks!

  • How can I disable my verticle Scroll

    HOw can I disable my verticle scroll?