New answers tagged

0

Based on this answer for another question, the issue might be the lack of a dbus session. See: laptop $ ssh pi pi $ gio mount smb://192.168.86.18/Video gio: smb://192.168.86.18/Video: volume doesn’t implement mount After connecting to my headless Raspberry Pi over ssh, I can't mount things using gio/gvfs. Then, I can start a dbus session and run a new shell ...


0

After many hours of attempts, I was able to get it working with the following command: sudo mount -t cifs -o vers=3.1.1,rw,noperm,username=<microsoft-account>,password='<microsoft-account-password>',iocharset=utf8,file_mode=0777,dir_mode=0777,soft,user //<windows-device>/<windows-share-folder>/ /<linux-folder-path>/


0

It could possibly caused by some trickery of a drive controller possibly in an enclosure - and the problem will likely disappear if reinserted back the way it was - or configured back to the settings as it was when the filesystem was originally created - or it could just be a firmware or utility off-by-one bug (used to be fairly common) - but sudo resize2fs /...


0

If your physical volume is gone then there is no chance to recover your VG and LV and it's time to start from fresh.


0

would you mind trying to create the CSIDriver object and the Daemonset related as well? apiVersion: storage.k8s.io/v1beta1 kind: CSIDriver metadata: name: efs.csi.aws.com spec: attachRequired: false --- # Node Service kind: DaemonSet apiVersion: apps/v1 metadata: name: efs-csi-node namespace: kube-system spec: selector: matchLabels: app: ...


Top 50 recent answers are included