virtualbox – Strange behavior of mount -t vboxsf

To mount a shared folder in VirtualBox one can run mount -t vboxsf [share name] [mountpoint]. Ever since ArchLinux integrated some VirtualBox things into the kernel I noticed that if [share name] and the directory name of [mountpoint] coincide, then the mount operation will always fail with File or directory not found.

Example:

cd ~
mkdir test
mount -t vboxsf test test # "mount failed: File or directory not found"
mv test test2
mount -t vboxsf test test2 # success

I tested this with and without virtualbox-guest-utils. Why is this happening? Is there any way to fix this?


I am using Linux Arch 5.7.7-arch1-1 x86_64 GNU/Linux in VirtualBox 6.1.8 x64 on a Windows 10 v1903 x64 host.

fstab – mount NAS shared folder subfolders info ubuntu but with a different user and group grants

On our network we have Qnap nas server with a IP 10.20.101.91 and on it we have a Midas shared folder.
10.20.101.11Midas
under midas folder I we have folderA, folderB and folderC

I need to mount nas shared midas folder to storage folder.

/storage/folderA
/storage/folderB
/storage/folderC

at the end of mount I need to set
folderA chown to www-data:www-data with owner 33 group 33 and 755
folderB chown to www-data:www-data with owner 33 group 33 and 755
folderC chown to midas:midas with owner 104 group 107 and 755

but when the folders owner can’t change and it shows just root:root

How can I solve this problem?

kubernetes – Cannot mount CIFS storage on k8s cluster

I have to mount CIFS storage, trying to use flexvolume, fstab/cifs, but I have no idea what i’m doing wrong.

Using microk8s v1.18

root@master:~/yamls# cat pod.yaml 
apiVersion: v1
kind: Secret
metadata:
  name: cifs-secret
  namespace: default
type: fstab/cifs
data:
  username: 'xxxxxxxxxxx='
  password: 'xxxxxxxxxxxxxxxxxxxxxx=='
---
apiVersion: v1
kind: Pod
metadata:
  name: busybox
  namespace: default
spec:
  containers:
  - name: busybox
    image: busybox
    command:
      - sleep
      - "3600"
    imagePullPolicy: IfNotPresent
    volumeMounts:
    - name: test
      mountPath: /data
  volumes:
  - name: test
    flexVolume:
      driver: "fstab/cifs"
      fsType: "cifs"
      secretRef:
        name: "cifs-secret"
      options:
        networkPath: "//srv/storage"
        mountOptions: "dir_mode=0755,file_mode=0644,noperm"

But

root@master:~/yamls# kubectl apply -f pod.yaml 
pod/busybox configured
The Secret "cifs-secret" is invalid: type: Invalid value: "fstab/cifs": field is immutable

On changing type of secret to Opaque I get this

Events:
  Type     Reason       Age                   From                                      Message
  ----     ------       ----                  ----                                      -------
  Normal   Scheduled    <unknown>             default-scheduler                         Successfully assigned default/busybox to spb-airsys-services.spb.rpkb.ru
  Warning  FailedMount  17m (x23 over 48m)    kubelet, master  MountVolume.SetUp failed for volume "test" : Couldn't get secret default/cifs-secret err: Cannot get secret of type fstab/cifs

What I have to use with CIFS driver on Secret? Why this is so hard? Is it changing API or else? Why API version changing from version to version, is it invented in order to give version compability?

And, in future, what can you suggest to NFS mounting? Even more, which practices do you use to provide mounts’ snapshots (or any other backup system)?

Why is my external HDD failing to mount on my MacBook?

All of my MacBook Pro 13″ 2017 backups are kept on my Toshiba External HDD. I decided to update my MacBook to macOS Big Sur developer beta (because I am a dev) and test it out. I backed my MacBook up onto my external hard drive before installing macOS 11 Big Sur beta, expecting to be able to use it just in case I need to go back to macOS Catalina.

After I installed the beta:

Just about a half a week ago, after using the drive completely fine in macOS Big Sur, I plugged in my external hard drive and found that it did not appear on my desktop or in Finder. I opened Disk Utility to find that the disk was displayed as not mounted. I tried to click Mount, which was not greyed out, and I received an error that the disk could not be mounted:

Could not mount “TOSHIBA EXT”. (com.apple.DiskManagement.disenter error 0.)

I automatically assumed that this was just a bug in the new beta update and I reported it to Apple. However, I soon came to find out it was also happening on another MacBook Air that has macOS Catalina 10.14.2 installed. So it was obviously not the beta, it was the disk.

Why exactly did this happen on a disk that was working perfectly fine the day before? Was the disk affected by something in the macOS Big Sur beta or is it a completely unrelated issue? I was searching for solutions for this issue and found that it was somewhat common, and that people recommend using DiskWarrior to repair the disk, however, I cannot justify spending $100 to repair a disk when I might as well just buy a newer and faster SSD. Are there any other cheaper and even free solutions to this?

And in terms of data, I do not have data on the disk that is vital except for my MacBook Pro backups, which I was hoping to have on hand if something went wrong. If I bought a new drive, could I back up that from macOS Big Sur, erase Big Sur and install Catalina with the data from Big Sur?

Mount Samsung S10 file system to Windows 10

Is it not possible to mount and browse the file system with Samsung Galaxy S10 if I connect it to Windows 10? With Galaxy S8 it was possible and I could easily traverse the file system of the phone to make sure that I did and did not have files in the phone before I erased and reset it. Now I want to erase and reset my S10 but I find no good way of checking its file system the way that I did with the S8.

Mount Samsung S10 file system to Windwos 10

Is it not possible to mount and browse the file system with Samsung Galaxy S10 if I connect it to Windows 10? With Galaxy S8 it was possible and I could easily traverse the file system of the phone to make sure that I did and did not have files in the phone before I erased and reset it. Now I want to erase and reset my S10 but I find no good way of checking its file system the way that I did with the S8.

server – 20.04 – chmod not working on exfat mount

I have 2 internal HDDs formatted in exFAT – fstab as below

#INT-1TB-4K Internal HDD mount to /mnt/INT-1TB-4K
UUID=0E7E-6579 /mnt/INT-1TB-4K exfat defaults, permissions 0 0

#INT-1TB-BAK Internal HDD mount to /mnt/INT-1TB-BAK
UUID=3037-96B0 /mnt/INT-1TB-BAK exfat defaults, permissions 0 0

Running Ubuntu Server 20.04, for which kernel supports exFAT without the exfat-utils / fuse packages being present.

/mnt ls-all gives

exharris@plexserv:/mnt$ ls -all
total 520
drwxr-xr-x  4 root root   4096 Jul  2 09:32 .
drwxr-xr-x 20 root root   4096 Jul  2 05:15 ..
drwxr-xr-x  9 root root 262144 Jul  3 03:49 INT-1TB-4K
drwxr-xr-x  7 root root 262144 Jul  3 03:49 INT-1TB-BAK

I get permission denied errors in the terminal when trying to create files in these folders (unless I use ‘sudo’, of course). This is because the ‘others’ write bit is set to -.

When running sudo chmod -R 777 INT-1TB-4K from /mnt, I get no errors, but when doing ls -all again, nothing has changed.

This is causing me problems also as I have set these up as Samba shares and also cannot write to them from other machines.

I also tried sudo chmod -R o+w INT-1TB-4K – same thing happened.

link2sd – Fix for error : “mount: ‘/system’ not in /proc/mounts”

First things first, I just got into rooting and custom roms. I haven’t written a single command, and I am just at the start of a beautiful journey. I am going to try to include everything, since I don’t know which part is important.

I have a redmi note 5 pro, was android 9, at that point I unlocked the bootloader and rooted it with magisk. Didn’t download any module.

After that I donwloaded a custom rom (pixel experience) (I use pitch black recovery). The device got unrooted and I had to root it again via magisk. I wanted to root because there were certain apps that I wanted to convert to system apps. I tried downloading a module called App Systemizer through magisk and tried to run it, but to no avail, maybe because I am running android 10. After that I searched for alernative ways, and found an app Link2SD . I tried to convert an app to system app, and got shown this error :
Error in shown by Link2SD

So what do I do now? I am looking for permanent solutions. I have tried looking up other answers and most of them were like “… write this code…” But where am I supposed to write and implement these codes? Also, I somewhere read that maybe my /system is read only, so then how do I convert to read-write mode? Is there way to solve it without compromising my data (I know I can take backup, but still).

All help is appreciated .