I even tried sudo mkdir /mnt/A83B-1B10/music to make a new folder, as I thought that if I had actually just made the folder then perhaps it'd be created with appropriate permissions that I could then either write to it immediately or sudo chown it and then write to it. So I really can't see why the operation is not permitted. And I believe that the sudo part means effectively 'I'm the boss, do as you're told', right? And to cap it all, remember that the same drive can be written to when it's plugged into the other Pi on the same network. The fact that it runs through all the files means that the path must be correct. Still quite poky at >8% though, and actually rather nice.Īnyway, unfortunately, I tried the suggested command, and it didn't work.Įven with sudo thrown in, the chown -R command just scrolls through a huge list of 'chown: changing ownership of x' for all the files and folders on the disk, each followed by 'Operation not permitted'. Magic Rock's 'What are the odds?' from Tesco. In the absence of a magic bullet, I think I'm done fettling with it.Īh, mine weren't quite that strong. I tried chmod -R 777 and the Pi thought about it for a while, but it didn't solve anything. So if solving the issue would require doing so, I'll just bin the whole Pi-as-NAS idea and plug it back into the Digione Pi. So it's not the disk itself.Īnd since the external disk works fine otherwise, I don't want to touch what's on it or add any Pi OSs. And when it's plugged directly into the other Pi with the Digi attached, it is writeable. The USB SSD is vfat/fat32 formatted, not NTFS. The music files are on an external USB SSD, while the Dietpi OS is on the SD card in the Pi. I changed it from the default, of course, but the dietpi OS defaults to changing the passwords for both root and the dietpi user it creates at the same time, so I kept them the same to make things easier to navigate. Yeah the password is the same for the Pi admin user (root) and for the specified SMB user (dietpi). But I wouldn’t want to impose too much, given that it just plugging the SSD directly into the other Pi with the Digione attached works (minus having Minimserver) - albeit that it’s less satisfying! So any guidance you can offer would indeed be appreciated. And I even got a windows-like GUI working with the Pi, which was kind of fun.īut this bloody write permission issue just will not go away! It’s resulted in something between just laughing at it and forgetting about it, and throwing the whole thing in the bin in rage So it’s been a learning experience, certainly, to try this stuff. I tried to chown -R the path to the SSD but it failed.įor the avoidance of doubt, I’d never actually typed anything to do with a Pi into a terminal before this, I’d only ever used things like Volumio or Ropieee via their GUIs before! I’m just going by suggestions I’ve found on forums and so on. I tried editing the mount commands in fstab (at least think that’s what I did!) to include noperm and a couple of other tips I read on the net, but that just made the SSD share appear empty when I accessed it from my iMac. I tried editing the smb.conf with all sorts - writeable = yes and read only = no among them. Minimserver was running fine too (I prefer to have Minimserver as an option alongside Volumio’s own browser because it makes it easier to access classical music by composer and that sort of thing).īut I couldn’t get write permission for the the SSD to work. Volumio on the other Pi/Digione could see the drive as a NAS and scan it as a library. I installed Samba via Dietpi, and could mount the SSD and access the files across the network just fine.
0 Comments
Leave a Reply. |