Can't write to root lvl of boot drive in 10.6

after doing some installs and uninstalls I find that my MacBook Pro with 10.6 will not allow me to save anything to the root level of it's internal hard drive. (Can't create a new folder either) error msg "...could not be saved, you don't have permission"
When I do a Get Info on the HD my name (I'm admin) not listed in Sharing & Permissions, yet a Get Info on an indiv folder will list my name w/ read & write permission. What do you think is going on and how can I fix this. (Yes I repaired permissions with Disk First Aid to no avail)
Thanks,
Paul

Paul Dougherty wrote:
my MacBook Pro with 10.6 will not allow me to save anything to the root level of it's internal hard drive.
If you launch the Terminal utility and run this command
ls -l -d /
what do you see? (Those are lower-case letters "L".) On my Mac I see this:
drwxrwxr-t 38 root admin 1360 Oct 6 11:17 /

Similar Messages

Folders on the root level of boot drive

Hello. I'm wondering if anyone can tell me if there are long-term or detrimental consequences to keeping a folder called "C/" located on the root directory of my boot drive in Snow Leopard.
An explanation: I work at a television station, and one of our video distribution systems is switching from a satellite-based system to a web-based client and download distribution. The online Java client for this distribution method defaults to setting a download folder of "C:/Downloads" which is clearly more suitable for Windows than OS X. If the default remains unchanged when a mac user begins a download, a folder is created on the boot drive called "C/". Inside that folder is another folder called "Downloads".
If there are no ill effects to be had from keeping this folder structure on the boot drive permanently, I'll likely create a folder action that will simply move the mpeg files from "Downloads" to a server that will automatically convert the mpeg files to something more suitable for Final Cut Pro. The editors in my shop won't have to worry about changing the download folder EVERY TIME and manually moving the downloaded file to our conversion server.
Thank you to anyone who can provide some input on this. For the moment, I've gone ahead and set this up on a test machine, and I'm waiting to see if it blows up...:-)

Boy would I ever love that!
Since the distribution is being handled by a company that also has an integrated editing/playout system for video, I imagine it was designed to favor that system rather than our current Final Cut setup. I'll make it work either way, it's just whether I'll be happy about it or not.
I'll keep this thread open for a couple days, see if I can get some feedback on it. If at the end of a week, I haven't found any problems of my own, and can't get a definite yes or no from anyone else, I'll leave a follow-up and mark it solved.

How can I upgrade my Mac G5's boot drive?

Hi,
I have a PowerMac G5 running 10.5.8... and just bought a new internal 1TB SATA I would like use as my new boot drive.
What's the most simple method to do so?
I have a copy of Data Rescue 3 that has a "clone" feature -- which I tried. It worked, but the new drive's system partition map is reduced to the size of the old (smaller) drive. I used Disk Utility to try to increase the volume scheme up to the new capacity, but it gives me an error saying "MediaKit reports partition (map) to small." and won't increase the size.
Suggestions?
Thanks,
Carl

I have no idea what you've done with Data Rescue, but it isn't a system clone. Here's what you need to do:
A. Prep the new drive:
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. Note the SMART status of the drive in DU's status area. If it does not say "Verified" then the drive is failing or has failed and will need replacing. SMART info will not be reported on external drives. Otherwise, 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. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID (for Intel Macs) or APM (for PPC Macs) then click on the OK button. Click on the Partition button and wait until the process has completed.
B. Repair the Old Hard Drive and Permissions
Boot from your OS X Installer disc. After the installer loads select your language and click on the Continue button. When the menu bar appears select Disk Utility from the Utilities menu. After DU loads select your hard drive entry (mfgr.'s ID and drive size) from the the left side list. In the DU status area you will see an entry for the S.M.A.R.T. status of the hard drive. If it does not say "Verified" then the hard drive is failing or failed. (SMART status is not reported on external Firewire or USB drives.) If the drive is "Verified" then select your OS X volume from the list on the left (sub-entry below the drive entry,) click on the First Aid tab, then click on the Repair Disk button. If DU reports any errors that have been fixed, then re-run Repair Disk until no errors are reported. If no errors are reported click on the Repair Permissions button. Wait until the operation completes, then quit DU and return to the installer. Now restart normally.
If DU reports errors it cannot fix, then you will need Disk Warrior and/or Tech Tool Pro to repair the drive. If you don't have either of them or if neither of them can fix the drive, then you will need to reformat the drive and reinstall OS X.
C. Clone using Restore Option of Disk Utility
1. Select the destination volume from the left side list.
2. Click on the Restore tab in the DU main window.
3. Select the destination volume from the left side list and drag it to the Destination entry field.
4. Select the source volume from the left side list and drag it to the Source entry field.
5. Double-check you got it right, then click on the Restore button.
Destination means the new hard drive.
Source means the old boot drive.
Last, use Startup Disk preferences to select the new drive as the permanent startup drive, then click on the Restart button.

Can I just swap in my new boot drive?

I just carbon copy cloned my 60gb boot drive to a new 320gb drive in the 1st ATA/66 slot. I'm running off the 320gb right now. Can I just flip these 2 drives around so the 320gb is in the 1st ATA/100 slot and the 60 is in the 1st ATA/66 slot. Also, Can I put a drive in the Lower Optical Slot without and extra stuff? I see the Ribbon & Power cables just hanging there. Do I need a bracket of any type?

Thanks for all the input, Currently I have a 60gb Operating Drive, a 120gb filling up the second ATA100. I also have a 160gb waiting to go back in and a new 500gb that just arrived. So what I think I want to do is put the 320 & 500 in the 100 speed slots, with the 320 as OS drive and 500 as Itunes library. Then the 120 & 160 go in the 66 speed slots. That Leaves the 60, which is a bootable drive. I was thinking about putting it under the SuperDrive. But if it's that slow, I may shelf it as an BU OS drive. (I have a 1tb USB drive that I will back everything up to.) Once this is done, it's time to take a look at that Graphics card. Thanks again for all the speedy advice & info.

Can CS6 be installed on a non-boot drive partition?

I'm going to run CS6 and Avid MC6 on the same machine (iMac), and thought it would be a good idea to put them on separate partitions to avoid any conflicts. Avid apparently MUST be on the system (boot) partition... can CS6 be installed on a non-boot internal drive partition?

It can, but shared components will still end up in your Application Support and Library folder, so this is a moot point. you are trying to avoid something that you can't influence.
Mylenium

Can't access locked files on non-boot drive

On my six year old G4 I can't boot from the primary hard drive anymore. I have the computer booting from a secondary drive, but regardless of system reinstalls, etc., it will no longer run from the primary drive. This would be fine, except that I have a number of files that are considered to be owned by the administrator account on the primary drive, which I can no longer get into.
Is there any way I can get at those files?
Any help would be much appreciated; I have six years worth of documents and photos on this computer.

sugersh,Welcome to Apple Discussions.
Try this: Select the old Hard drive icon and choose Get Info. Then go to Ownership and Permissions. Click on the padlock' and enter your Admin password. Then in the ownership menu set your current login as the owner. Then give yourself (i.e. the name of the user account you are logged in as) 'Read and Write' access. You may then set the Owner back to whatever it was previously if you wish. Then at the bottom click the button 'Apply to Enclosed Items'. This should give you access to all the files on that hard disk.
HTH
mrtotes

How can I write to an SD card with my iPad 3?

How can I write to an SD card/thumb drive with my iPad 3?

Sorry to post this question before realizing others already did. HOWEVER! Why would Apple make such a cool device like the iPad without the abiity to write to an SD card?

Ubuntu linux machine can not write to connected usb hard drive

Hi, I bought a WRT610N router. I connected my USB drive to it, and it is working fine with my Vista Machine. However, my Ubuntu linux machine can not write to it. It can read it great, but it can not write. If I connect the drive directly to the Ubuntu device, it reads and writes fine.
I've set all the permissiosn and such in the router setup. I didn't need to do anything in Vista. Is there something I need to do in Ubuntu? I'm new to Linux so Imay have missed something.
Thank you.

Create a new admin user and give all permissions oj your router and check if you can write to it on your Ubuntu linux machine...

Boot Drive(s), Scratch Disks, eSATA chipsets

It was explained I shouldn't have posted this where a question had already been answered. Let me try again...
REPOST (thanks Hatter, but have further questions):
Setup:
Mac Pro
16GB RAM
Apple RAID card
Sonnet E4P PCIe eSATA card (dedicated channel for each of the 4 ports)
INTERNAL 2-150GB Velociraptors RAID 0 Boot array.
INTERNAL 2-750GB in RAID 0. (7200RPM Hitachi's)
EXTERNAL 5-750GB (7200RPM) RAID 0 in Sonnet Fusion D500P case
Backup drives:
Time Machine:
EXTERNAL 1TB Barracuda in OWC eSATA enclosure with Oxford chipset
Personal data/media:
EXTERNAL 2nd 1TB Barracuda in identical OWC enclosure (Mercury Elite-AL Pro)
Personal data/media (2nd backup)
Seagate 1TB FreeAgent Pro (using Firewire because Sonnet states eSATA can be untrustworthy due to chipset utilized)
Boot drive clones using SuperDuper:
250GB WD SE (1st)
400GB Simpletech (2nd)
Other drives:
500GB WD MyBook (firwire)
400GB Maxtor (USB 2.0)
Questions:
1) Am I getting the best use of my Velociraptors being used in RAID 0 (I have two clones of this array; want speed-quick boot-rapid program response)
2) I'm using the 3.75TB Fusion D500P for RAID 0 video capture via firewire from camera (SD and HD video). Is it correct the firewire MyBook and USB 2.0 Maxtor are no optimal for scratch disks? I should use a RAID array and if the drives are big, partition them? I'm having trouble finding info on this, but I suppose the place to look is the Adobe and Studio Pro forums. I have Premiere CS3, but think I'm going to rely more on Final Cut Studio 2...it's 64-bit. Still learning how to get optimal performance out of Photoshop.
3) Hatter, you mentioned "would be 'concerned' about even Oxford 934 and eSATA off 2-channel Sonnet Tempo. Same with Seagate. And MyBook, FW and USB2. I have some older FW drives, for backup and archive and rarely connected except to make a backup."
Why would you be concerned about the OWC eSATA drives with the Oxford chipset? The Barracuda drives are enterprise drives. BTW, the Sonnet E4P has a dedicated channel for each of the four ports. Are you saying there are reliability issues with the OWC drives and I suppose the concern for your (and mine) MyBook, Seagate, etc drives is that they are not enterprise grade and thus less reliable.
Also Hatter (this is a whole different story), regarding the NewerTech kit, it's my understanding the two SATA ports on the motherboard are not supported by Apple. While they do work for some applications, they do not work with Toast and Blue-Ray drives for burning Blu-Ray discs. You have to use finder for that I think. Apple should release a firmware update and support these connections!
Thanks!

I meant to reiterate the 3.75TB Fusion D500P is connected via eSATA, the video camera is connected via firewire.
Thanks.

Can't write to samba shares as any user but root.

I can mount shares, and I've specified every parameter I think could make a difference, but can't write to shares as any user but root.
archangel $ sudo mount -t cifs -o guest,uid=barrucadu,gid=users,file_mode=0777,dir_mode=0777,rw //masonlap/share /share/mason/
archangel $ touch /share/mason/file
touch: cannot touch `/share/mason/file': Permission denied
This doesn't help either:
archangel $ sudo chmod 777 -R /share
archangel $ touch /share/mason/file
touch: cannot touch `/share/mason/file': Permission denied

By hand, here's my smb.conf
[global]
workgroup = HOME
server string = Linux SAMBA Server
security = user
hosts allow = 192.168.1. 192.168.0. 127.0.0.1
load printers = no
log file = /var/log/samba/%m.log
max log size = 50
dns proxy = no
[share]
comment = SAMBA File Sharing
path = /srv/share
read only = no
public = yes
writable = yes
create mask = 0777
guest ok = yes
browseable = yes
Last edited by Barrucadu (2009-01-17 14:41:47)

[SOLVED] Booting Arch off USB HDD fails - can't mount real root device

I've installed Arch on the internal HDD (sda) of my laptop, and I attempted to install a second copy of Arch on partition sdb3 of an external USB HDD. sdb3 is a primary partition that I had prepared beforehand with gparted and outfitted with the reiserfs filesystem. I skipped section 3.2 (manually prepare hard drives) of the Arch installer. There was no problem with section 3.3 (manually configure filesystems and mountpoints); I put all of / in sdb3. Installing packages and configuring the system also went without a hitch.
I wanted to boot this new install of Arch via the boot menu of GRUB that was installed in the MBR of sda with my primary install of Arch. On the new install, I first did go through section 7 (install bootloader), thinking I would want to install GRUB in the root sector of partition sdb3 (not in the MBR of sdb where the GRUB of MintKDE resides, a boot menu that I want to keep) but that failed, so I then picked "no bootloader to be installed". With that I exited the new install, since it appeared to have gone to completion.
I then copied the appropriate stanza in the /boot/grub/menu.lst of this new Arch install to the /boot/grub/menu.lst of my primary Arch install on the internal HDD of my laptop.
This stanza reads as follows:
# (3) Arch Linux on WDPP60 blue (sdb3)
title Arch Linux on WDPP60 blue (sdb3)
root (hd1,2)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/191cc027-43ce-443b-8846-f265d60555ec ro
initrd /boot/kernel26.img
However, I'm not able to boot the new Arch install when I pick this entry from the GRUB menu list. The new install starts booting, finds sda but not sdb and stops with the following errors, dropping me to a recovery shell:
Root device /dev/disk/by-uuid... doesn't exist. Attempting to create it.
ERROR: Unable to determine major/minor number of root device '/dev/disk/by-uuid...'
mounting /dev/disk/by-uuid... on /new_root failed: No such file ...
ERROR: Failed to mount the real root device.
Running "mount -t reiserfs /dev/sdb3 /new_root" at the ramfs prompt also fails.
I've tried a number of edits of the menu.lst stanza from the grub> command prompt, such as adding rootfstype=reiserfs, replacing root=/dev/disk/by-uuid..etc. with root=/dev/sdb3 (booting then fails with "/dev/sdb3 No such file"), using "initrd /boot/kernel26-fallback.img" etc., but booting always fails at the same stage with equivalent error messages.
I have no trouble booting half a dozen other Linux/BSD distros that reside on two different external USB HDD's by the same method, i.e. choosing an entry from the GRUB boot menu of my primary Arch install, after I placed the appropriate stanza in its /boot/grub/menu.lst.
How can I get this new Arch install to boot?
Last edited by RobF (2010-05-17 23:03:27)

Yes, this was in fact the solution. I stumbled upon it in this thread:
http://bbs.archlinux.org/viewtopic.php?id=65844
When one wants to boot from a USB mass storage device, the initrd needs to include the modules for accessing USB devices, and in Arch this is accomplished by adding "usb" to the HOOKS array. I simply reinstalled Arch to the USB HDD and in the system configuration step now edited /etc/mkinitcpio.conf by adding the "usb" item. Adding "rootdelay=10" and/or "rootfstype=reiserfs" to the kernel line in the appropriate stanza in Arch's /boot/grub/menu.lst wasn't necessary in this case. I left the stanza exactly as I posted it above.
Thanks for your input.

Root login is blocked from telnet ssh pam_unix_session: Can't write lastlog: uid 0: I/O error

Root login is blocked from telnet ,ssh error : pam_unix_session: Can't write lastlog: uid 0: I/O error
sshd[1969]: pam_unix_session: Can't write lastlog: uid 0: I/O error
sshd[1970]: pam_unix_session: Can't write lastlog: uid 0: I/O error
sshd[1983]: pam_unix_session: Can't write lastlog: uid 0: I/O error
sshd[1984]: pam_unix_session: Can't write lastlog: uid 0: I/O error
sshd[2023]: pam_unix_session: Can't write lastlog: uid 0: I/O error
sshd[2021]: pam_unix_session: Can't write lastlog: uid 0: I/O error
genunix: vn_rdwr failed with error 0x6
genunix: kobj_load_module: smp read header failed
genunix: vn_rdwr failed with error 0x6
genunix: kobj_load_module: ses read header failed
sshd[2037]: pam_unix_session: Can't write lastlog: uid 0: I/O error
sshd[2035]: pam_unix_session: Can't write lastlog: uid 0: I/O error
please suggest for the issue , occurs frequently in solaris 10

please verify your underlying hardware

I can't write to my Drobo

I have a new iMac (like this):
I am trying to connect the Drobo that I used to use with my Windows Computer. It has 4 drives @ 3TB each, and the whole drive is over half full, so I am not terribly interested in the cost that it would take to "back up" that whole disk pack. It took some shenanigans (reboots of both the drive and the computer; disconnections, and reconnections; fiddling around with MAC Disk Utility) to get it to show up in Finder at all. I still have issues with it unmounting and needing to remount it, but that's not my main issue.
THE REAL PROBLEM:
Though I can get the Drobo to show up in finder, and I can read from it, I can't write to it. Based on some earlier searching I tried this terminal command, which helped it to show up in finder, but didn't seem to affect it's being read-only:
new-host-3:~ davidholcomb$ getfileinfo /Volumes/Drobo
directory: "/Volumes/Drobo"
attributes: avbstclinmedz
created: 12/10/2012 19:06:46
modified: 09/11/2014 03:37:07
Looking at another thread (partition map check failed because no slices were found), which I wandered into because I was getting this error in Disk Utility upon running Verify Disk because I got a failure when I tried to "mount" the drive in Disk Utility:
This thread suggested I try a couple additional Terminal Commands, which I will post the results of here:
#1: diskutil list
new-host-3:~ davidholcomb$ diskutil list
/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *121.3 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:          Apple_CoreStorage                         121.0 GB   disk0s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk0s3
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk1
   1:                        EFI EFI                     209.7 MB   disk1s1
   2:          Apple_CoreStorage                         999.3 GB   disk1s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk1s3
/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Macintosh HD           *1.1 TB     disk2
/dev/disk4
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *17.6 TB    disk4
   1:       Microsoft Basic Data Drobo                   17.6 TB    disk4s1
#2 diskutil cs list
new-host-3:~ davidholcomb$ diskutil cs list
CoreStorage logical volume groups (1 found)
|
+-- Logical Volume Group 7DACBFD5-E22C-404B-98B1-99D97AD08B2F
    =========================================================
    Name:         Macintosh HD
    Status:       Online
    Size:         1120333979648 B (1.1 TB)
    Free Space:   114688 B (114.7 KB)
    |
    +-< Physical Volume F26F7717-B081-4312-8252-65C9E3040AD4
    |   ----------------------------------------------------
    |   Index:    0
    |   Disk:     disk0s2
    |   Status:   Online
    |   Size:     120988852224 B (121.0 GB)
    |
    +-< Physical Volume 414053B5-EFD8-4FC0-87CE-F3913D6E876B
    |   ----------------------------------------------------
    |   Index:    1
    |   Disk:     disk1s2
    |   Status:   Online
    |   Size:     999345127424 B (999.3 GB)
    |
    +-> Logical Volume Family BE5280EF-B093-4137-88A2-5AF3F1ACEFCC
        Encryption Status:       Unlocked
        Encryption Type:         None
        Conversion Status:       NoConversion
        Conversion Direction:    -none-
        Has Encrypted Extents:   No
        Fully Secure:            No
        Passphrase Required:     No
        |
        +-> Logical Volume D35043A0-F886-4223-81DD-4880F04ECEA3
            Disk:                  disk2
            Status:                Online
            Size (Total):          1114146996224 B (1.1 TB)
            Conversion Progress:   -none-
            Revertible:            No
            LV Name:               Macintosh HD
            Volume Name:           Macintosh HD
            Content Hint:          Apple_HFS
and #3: Mount:
new-host-3:~ davidholcomb$ mount
/dev/disk2 on / (hfs, local, journaled)
devfs on /dev (devfs, local, nobrowse)
map -hosts on /net (autofs, nosuid, automounted, nobrowse)
map auto_home on /home (autofs, automounted, nobrowse)
/dev/disk4s1 on /Volumes/Drobo (ntfs, local, nodev, nosuid, read-only, noowners)
Another user who had run these commands and posted the results, seemed to have been missing an EFI partition on their external drive and was asked to run this command and post results. But the thread with that user dies there. Here are my results of this command:
new-host-3:~ davidholcomb$ diskutil info disk4
   Device Identifier:        disk4
   Device Node:              /dev/disk4
   Part of Whole:            disk4
   Device / Media Name:      TRUSTED Mass Storage Media
   Volume Name:              Not applicable (no file system)
   Mounted:                  Not applicable (no file system)
   File System:              None
   Content (IOContent):      GUID_partition_scheme
   OS Can Be Installed:      No
   Media Type:               Generic
   Protocol:                 USB
   SMART Status:             Not Supported
   Total Size:               17.6 TB (17592186044416 Bytes) (exactly 34359738368 512-Byte-Units)
   Volume Free Space:        Not applicable (no file system)
   Device Block Size:        512 Bytes
   Read-Only Media:          No
   Read-Only Volume:         Not applicable (no file system)
   Ejectable:                Yes
   Whole:                    Yes
   Internal:                 No
   OS 9 Drivers:             No
   Low Level Format:         Not supported
Can anyone help me with a next step to make this drive read/writeable?

Turns out that the Drobo needs to be plugged straight into computer. I had it via hub. Though it has worked for the past couple weeks in this configuration, the new update pushed it over the edge, I guess. Plugged in directly and working fine.

After upgrading to Solaris 10 "Can't load the root filesystem" on V245

I have a Sunfire V245 that was running on Solaris 9 (very stable). I upgraded to Solaris 10 (6/06) this morning and everything seemed to go smoothly. After the upgrade the system rebooted, but will not boot. I get the following uptput;
Rebooting with command: boot
Boot device: disk File and args:
SunOS Release 5.10 Version Generic_118833-17 64-bit
Copyright 1983-2005 Sun Microsystems, Inc. All rights reserved.
Use is subject to license terms.
pxb_bcm: cannot load driver
Cannot load drivers for /pci@1e,600000/pci@0/pci@a/pci@0/pci@8/scsi@1/disk@0,0:a
Can't load the root filesystem
Type 'go' to resume
"go" attempts to reboot, but I end up back in the same place.
Please help.
Thanks in advanced,
Craig

It seems like the driver for that device does not exist. Since the system installed successfully it means that it S10 did find a disk. I wonder if that was a different disk than the default disk. Please boot to the miniroot and check the disk info.

I can't write to usb stick [solved]

I've installed arch on my notebook yesterday. It took a few hours, but I got almost everything working correctly.
My issue is that when I plug in a usb stick, it gets automatically mounted, but I can't write to it.
I had the same issue with my ntfs data partition, but I solved it by adding an entry to /etc/fstab.
Unfortunately that won't be an efficient solution for usb sticks, since their partition type might vary.
/dev/sda1: LABEL="arch" UUID="6c7ecf62-2ffb-4bfe-9af0-39d7cdb89751" TYPE="ext4" PARTUUID="000e19e1-01"
/dev/sda2: LABEL="swap" UUID="ff87fb8b-773b-45ca-9198-c2abf9a1a017" TYPE="swap" PARTUUID="000e19e1-02"
/dev/sda3: UUID="AAACDC9DACDC657B" TYPE="ntfs" PARTUUID="000e19e1-03"
/dev/sda4: LABEL="Dados" UUID="EC60740C6073DC30" TYPE="ntfs" PARTUUID="000e19e1-04"
/dev/sdb1: UUID="2013-11-01-08-10-26-00" LABEL="ARCH_201311" TYPE="iso9660" PTUUID="0d738582" PTTYPE="dos" PARTUUID="0d738582-01"
[hfluz@hfluz-arch ~]$ sudo fdisk -l
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x000e19e1
Device Boot Start End Blocks Id System
/dev/sda1 2048 398753791 199375872 83 Linux
/dev/sda2 398753792 402948095 2097152 82 Linux swap / Solaris
/dev/sda3 402948096 1399447551 498249728 7 HPFS/NTFS/exFAT
/dev/sda4 1399447552 1953519615 277036032 7 HPFS/NTFS/exFAT
Disk /dev/sdb: 14.8 GiB, 15879634944 bytes, 31014912 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x0d738582
Device Boot Start End Blocks Id System
/dev/sdb1 * 0 1056767 528384 0 Empty
/dev/sdb2 84432 147919 31744 ef EFI (FAT-12/16/32)
My usb stick is /dev/sdb.
Anyone already had the same problem?
Last edited by hfluz (2013-11-11 16:40:38)

MW wrote:Check your groups, you should be in the storage group.
https://wiki.archlinux.org/index.php/Users_and_Groups
I don't think that the storage group covers this. All USB storage devices that I have seem to come up as being part of the disk group. You should really not make your user part of the disk group.
If you read the post, and saw the info provided by the OP, you would see that he/she is trying to write to an iso, which is read-only.

Can't write to root lvl of boot drive in 10.6

Similar Messages

Maybe you are looking for