I getting these problems when I try to mount this filesystem DOS/MBR #file bag.vhd bag.vhd: DOS/MBR boot sector; partition 1 : ID=0x83, active, start-CHS (0x0,1,1), end-CHS (0x9,254,63), startsector 63, 160587 sectors #sudo mount -t auto -o ro,loop,offset=82252288 bag.vhd /mnt/floppy/ mount: /mnt/floppy/: overlapping loop device exists for /home/ffha/Documents/descon/bag.vhd. I have been created /mnt/floppy.

I am trying to set up my nextcloud account so that i can log in. When I try to log in with sudo mount -t davfs2 ... it keeps on asking for my next cloud credentials - it does not get them from the secrets file that i created. I have followed the tutorials online with the only difference being that the tutorials specify to update the /etc/fstab file. But i do not want to do this because i have this set up on my laptop where i only sporadically have access to the internet. I would prefer to use sudo mount.... and have the credential input automaticall from the secrects file (i understand that each time i will need to input my sudo password). I believe that what is happening is that when i use sudo mount .... it is trying to load the system /etc/davfs2 configuration instead of my local .davfs2. I believe this because when i try to configure the /etc/davfs2 (to point to my secrets file) i get config erorrs. But when i purposefully put errors in the local .davfs2 config file the system never seems to recognise it. the only other thing i can think to do is allow local users permission to run mount which i would prefer not to do. What i may be doing wrong? PS - using Xubuntu

Is there an automated way to update my mtab and fstab? Or a command I can run so that I can copy the output into these files? I'm just nervous about tampering with these files because I know they are critical. I previously had a md0 and md1 array but they "disappeared." Now my mtab and fstab is stale and it is giving me problems trying to run this automatic RAID utility, raider . ### fstab # /etc/fstab: static file system information. # # proc /proc proc defaults 0 0 /dev/md0 / ext3 errors=remount-ro 0 1 /dev/md1 none swap sw 0 0 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 ### mtab /dev/md0 / ext3 rw,errors=remount-ro 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid,mode=0755 0 0 proc /proc proc rw,noexec,nosuid,nodev 0 0 sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0 udev /dev tmpfs rw,mode=0755 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0 ### /proc/mounts rootfs / rootfs rw 0 0 none /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0 none /proc proc rw,nosuid,nodev,noexec,relatime 0 0 none /dev devtmpfs rw,relatime,size=1547340k,nr_inodes=215947,mode=755 0 0 none /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0 /dev/sda1 / ext3 rw,relatime,errors=remount-ro,data=ordered 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid,relatime,mode=755 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev,relatime 0 0 ## Here's what I think based on observation ### My proposed update to fstab (should it be sda or sda1?) # /etc/fstab: static file system information. # # proc /proc proc defaults 0 0 /dev/sda1 / ext3 errors=remount-ro 0 1 /dev/scd0 /media/cdrom0 udf,iso9660 user,noauto 0 0 ### My proposed update to mtab (should it be sda or sda1?) /dev/sda1 / ext3 rw,errors=remount-ro 0 0 tmpfs /lib/init/rw tmpfs rw,nosuid,mode=0755 0 0 proc /proc proc rw,noexec,nosuid,nodev 0 0 sysfs /sys sysfs rw,noexec,nosuid,nodev 0 0 udev /dev tmpfs rw,mode=0755 0 0 tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0 devpts /dev/pts devpts rw,noexec,nosuid,gid=5,mode=620 0 0

I am trying to access SD cards on Fedora 28, but do not have any success. System info is as follows: $ lsb_release -a LSB Version: :core-4.1-amd64:core-4.1-noarch:cxx-4.1-amd64:cxx-4.1-noarch:desktop-4.1-amd64:desktop-4.1-noarch:languages-4.1-amd64:languages-4.1-noarch:printing-4.1-amd64:printing-4.1-noarch Distributor ID: Fedora Description: Fedora release 28 (Twenty Eight) Release: 28 Codename: TwentyEight I was not able to access different SD cards using two different card readers. Despite of being accessible on both macOS and Windows, none of them is shown in the Nautilus file browser, the desktop or elsewhere obvious. The card readers are recognized by the system as per lsusb output: $ lsusb -v # some other USB devices Bus 001 Device 005: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x058f Alcor Micro Corp. idProduct 0x6362 Flash Card Reader/Writer bcdDevice 1.29 iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 0 bmAttributes 0x80 (Bus Powered) MaxPower 250mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 # some other USB devices Bus 001 Device 006: ID 0dda:2027 Integrated Circuit Solution, Inc. USB 2.0 Card Reader Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 0 bDeviceSubClass 0 bDeviceProtocol 0 bMaxPacketSize0 64 idVendor 0x0dda Integrated Circuit Solution, Inc. idProduct 0x2027 USB 2.0 Card Reader bcdDevice 1.6e iManufacturer 1 iProduct 2 iSerial 3 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 32 bNumInterfaces 1 bConfigurationValue 1 iConfiguration 4 bmAttributes 0x80 (Bus Powered) MaxPower 500mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 8 Mass Storage bInterfaceSubClass 6 SCSI bInterfaceProtocol 80 Bulk-Only iInterface 5 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x01 EP 1 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0200 1x 512 bytes bInterval 0 # some other USB devices I then had a look at the udev events while plugging a card in and out: $ udevadm monitor monitor will print the received events for: UDEV - the event which udev sends out after rule processing KERNEL - the kernel uevent KERNEL[701.434565] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block) UDEV [714.263816] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block) KERNEL[748.477184] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block) UDEV [761.338940] change /devices/pci0000:00/0000:00:1d.7/usb1/1-3/1-3:1.0/host4/target4:0:0/4:0:0:2/block/sde (block) In addition, I had a look at the kernel messages: $ dmesg [ 603.846840] usb-storage 1-3:1.0: USB Mass Storage device detected [ 603.847749] scsi host4: usb-storage 1-3:1.0 [ 605.703531] scsi 4:0:0:0: Direct-Access Generic CF 1.6E PQ: 0 ANSI: 0 CCS [ 605.704982] scsi 4:0:0:1: Direct-Access Generic MS 1.6E PQ: 0 ANSI: 0 CCS [ 606.509034] scsi 4:0:0:2: Direct-Access Generic MMC/SD 1.6E PQ: 0 ANSI: 0 CCS [ 606.510387] scsi 4:0:0:3: Direct-Access Generic SM 1.6E PQ: 0 ANSI: 0 CCS [ 606.511519] sd 4:0:0:0: Attached scsi generic sg4 type 0 [ 606.511943] sd 4:0:0:1: Attached scsi generic sg5 type 0 [ 606.512177] sd 4:0:0:2: Attached scsi generic sg6 type 0 [ 606.512408] sd 4:0:0:3: Attached scsi generic sg7 type 0 [ 608.924586] sd 4:0:0:1: [sdd] Attached SCSI removable disk [ 629.830776] sd 4:0:0:2: [sde] Attached SCSI removable disk [ 633.048754] sd 4:0:0:3: [sdf] Attached SCSI removable disk [ 639.490479] sd 4:0:0:0: [sdc] Attached SCSI removable disk Both the output of dmesg and udevadm monitor are telling that the card should be shown as sde. However, fdisk -l does not list sde. Besides that, trying to mount the device manually, raises an error: $ mount -t auto /dev/sde /mnt/ mount: /mnt: no medium found on /dev/sde. I am not sure, whether the needed driver module is loaded properly, since there is no mmc0-like entry in the dmesg output (as I am used to know from Debian-based systems). lsmod does not list the mmc0 kernel module either: $ lsmod | grep mm rtl8192c_common 61440 1 rtl8192cu rtlwifi 98304 3 rtl8192c_common,rtl_usb,rtl8192cu The only mmc-like modules which seems to be available but are not loaded are mmc_block and mmc_core: $ modprobe mm # listing suggestions using tab auto-completion mma7660 mmc_block mmc_core mms114 How could I solve this problem or at least narrow it down?

I would like to mount a disk on /var/log, the thing is, there are some process/services writing into it, such as openvpn, or system logs. Is there a way to mount a filesystem without having to restart the machine, or stopping the service? Many thanks

I have a hard drive with a lot of back up files, that were created by PhotoRec. When mounting it with a windows computer I can read all the files perfectly fine. Under linux I get an error when trying to look at the folder that contains all my backups. The rest of the hard drive is perfectly readable but when I try to ls the backup folder I get

ls: reading directory .: Input/output error

In Dolphin I just see a blank directory. I have tried letting arch auto mount and I have tried manually mounting it with -t ntfs-3g option (only flag used). A strange thing I notice is that if I manually mount it with the 3g option then all permissions are -rwxrwxrwx but if I let it be automatically mounted I have permissions -rw------- 1 steven steven (some have 2, but not many. The directories show d as they should). These are the same for every file and directory on the system. I don't understand why I can't see these files under Linux, but can under Windows. I even booted up SystemRescueCD again to see if it recognized it, but it couldn't even see the files (even though it was what had originally written the files in the first place). What is so weird to me is that I can read everything on the hard drive except that one folder. It has the exact same permissions as everything else in the hard drive. Additional info: This is a fresh install of Arch. As of today.

[steven@serenity ~]$ uname -a
Linux serenity 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux

(auto mounted) [steven@serenity ~]$ sudo fdisk -l Disk /dev/sdb: 596.2 GiB, 640135028736 bytes, 1250263728 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: 0x1549f232 Device Boot Start End Sectors Size Id Type /dev/sdb1 * 63 1250258159 1250258097 596.2G 7 HPFS/NTFS/exFAT

My ACER PC would not start, so I removed the disk and tried to access it on another PC in Ubuntu 24.04.2, but got this error msg: >Error mounting /dev/sdc4 at /media/ubuntu/ACER:wrong fs type,bad option,bad superblock on dev/sdc4, missing codepage or helper program, or other error. Is there a way to access this disk ?

Is it possible to mount an Overlayfs filesystem as an unprivileged user in a user namespace in Linux kernels >4.3.3; it seems that the fix to this vulnerability has blocked this functionality entirely. When I create a new user namespace with clone() , passing the CLONE_NEWNS flag and attempt to invoke mount with an overlayfs filesystem, I'm given permission denied. I can mount any other filesystem though. Is there a way to work around this/am I missing something?

I have a Debian 12 server that I just restored to a different hardware from backups. The new hardware is missing some disks and of course they failed to mount. After the machine booted, the root filesystem was still mounted read-only. I checked everything, but didn't find any issue. Then I removed all the *.mount services for the missing disks and the server booted with the root filesystem mounted writeable. That makes no sense to me. Why should the root filesystem, which is completely fine and without any errors, not be mounted rw if any other mount point fails? Is that a behaviour that I can configure somehow?

I have an NFS server installed on my PC running KDE Neon (24.04). I installed it so that I could share a folder to a Windows 11 tablet. It worked well, and I was able to create a persistent mount on the tablet. I have removed Windows from the tablet in favor of KDE Neon. Now I can mount the share from the cmd line without a problem, but I am not able to get it to mount from fstab. Can anyone suggest why one works and the other doesn't? CMD mount... sudo mount -t nfs 10.0.0.239:/srv/nfs/share /media/media0 In my fstab I have this... /media/media0 /srv/nfs4/media/media0 none bind 0 0 In my exports file I have... /srv/nfs4 10.0.0.0/255.255.255.0(rw,sync,fsid=0,crossmnt,no_subtree_check) Can anyone help me figure out why I the mount works from the command line, but not from fstab? Thanks, Rick Thanks for the suggestions everyone. Unfortunately I have yet to find a complete solution. I've made the suggested changes to my /etc/exports file and the the /etc/fstab file recommended in the last reply. I am still not able to mount the shares at boot. I can mount them manually, and I can mount them with $ sudo mount -a. I thought the issue was timing and my impatience but after a reboot and waiting several minutes the share didn't mount unless I issued sudo mount -a. What am I missing here? Rick Ok, the instructions say to reply to a post I need to edit my post so, here goes... Adding _netdev to the NFS mount commands in my fstab did not work. In fact adding that caused the network to not start, but had no effect on nfs-server.service, at least not that I could see. Thanks, Rick

I have some embedded devices running Linux (4.14.126), and i want them to write some of their logfiles to a network share on another (Windows 10) computer. Mounting the network share works mostly fine, apart from the fact that i have to provide login credentials (which i wanted to avoid), but i need some reliable way to detect a broken mount (for example when i reboot the PC). - Is it possible to get some kind of status information for a cifs mount? - What error conditions (if any) can be detected without actually trying to read from (or write to) the share? - Is it possible for my application to get automatic notifications in case of an error (maybe through inotify)? - Do i have to handle remounting myself, or does that happen automatically once the share becomes available again? PS (in case it matters): I won't use fstab, because the location of the network share is not known at boot time.

I'm writing a program to allow unprivileged users to mount overlay filesystems using a setuid binary. I've implemented a few safeguards to improve the program's security, but I'd like a more definitive checklist of potential security risks such a program might expose. Here are the safeguards I've implemented so far: - The program dissociates its mount namespace before performing any mounts, ensuring that other processes remain unaffected by the new mount. The program then runs a user-provided command inside that namespace. - It verifies that every lowerdir is readable by the user. For sub-items within each lowerdir, I assume that POSIX ACLs will prevent unauthorized access. - It ensures that the upperdir is both readable and writable by the user. Again, I rely on ACLs to enforce access restrictions on sub-items. - It verifies that the workdir is writable. Since the workdir must be empty for OverlayFS to function, I consider the risk there to be minimal. - It ensures that the mountpoint is writable by the user. - The program resets the effective UID and GID to the real user’s IDs immediately after completing the mount operations. These measures cover all the attacks I could foresee, but I suspect there may be additional risks I haven't accounted for. I would appreciate it if someone could point out any security issues before this goes into production.

I have a linux (ubuntu) server with a zfs pool containing nested fileystem. E.g.: zfs_pool/root_fs/fs1 zfs_pool/root_fs/fs2 zfs_pool/root_fs/fs3 I have enabled NFS sharing on the root filesystem (via zfs, not by editing /etc/exports). Nested filesystems inherit this property. NAME PROPERTY VALUE SOURCE zfs_pool/root_fs sharenfs rw=192.168.1.0/24,root_squash,async local NAME PROPERTY VALUE SOURCE zfs_pool/root_fs/fs1 sharenfs rw=192.168.1.0/24,root_squash,async inherited from zfs_pool/root_fs On the client machines (linux, mostly ubuntu), the only filesystem I explicitly mount is the root filesystem. mount -t nfs zfsserver:/zfs_pool/root_fs /root_fs_mountpoint Nested filesystems are mounted automatically when they are accessed. I didn't need to configure anything to make this work. This is great, but I'd like to know who is providing this feature. Is it ZFS? Is it NFS? Is it something else on the client side (something like autofs, which isn't even installed). I'd like to change the timeout after which nested filesystems are unmounted, but I don't even know which configuration to edit and which documentation to read.

I'm encountering an issue when trying to mount a partition in Ubuntu. When I attempt to access the partition, I receive the following error message: Error mounting /dev/sda1 at /media/moe404/[partition_id]: wrong fs type, bad option, bad superblock on /dev/sda1, missing codepage or helper program, or other error. Screenshot: Additional Information: OS: Ubuntu 24.04 Disk Information: /dev/sda1 is a partition on my internal/external hard drive. Actions Taken: I haven't made any recent changes to the disk or system configuration. This error occurred unexpectedly when I tried to access the partition. Attempted Solutions: I tried rebooting the system, checking the disk with fsck, and searching for similar issues, but I haven't found a solution that works. What could be causing this issue, and how can I resolve it?

I'm trying to mount a DFS share via cifs. The share is built up like this: \\mydomain.local\Files is the DFS share. I can successfully mount this share as follows:

# mount -t cifs //mydomain.local/Files ~/fileserver -o username=myuser,domain=mydomain.local,password=hunter2

After this I can traverse the directories in ~/fileserver as I'd expect.

# ls ~/fileserver
folder1 folder2

When I try to cd into folder1 however, I get an error:

# cd folder1
cd: folder1: No such file or directory

It takes a second or two before the error appears. I think this is because folder1 is a DFS-Link to another fileserver, it links to: \\fileserver2.mydomain.local\Fileshare$\somedirectory\folder1 Now I've looked at dmesg right after this:

# dmesg
CIFS: Attempting to mount //fileserver2.mydomain.local/Fileshare/somedirectory/folder1
No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
FS-Cache: Duplicate cookie detected
FS-Cache: O-cookie c=0000000088cf85cb [p=00000000a52bce0c fl=222 nc=0 na=1]
FS-Cache: O-cookie d=00000000ff7a58d3 n=000000005109413d
FS-Cache: O-key= '46696c6573'
FS-Cache: N-cookie c=00000000c39f9d7a [p=00000000a52bce0c fl=2 nc=0 na=1]
FS-Cache: N-cookie d=00000000ff7a58d3 n=00000000930f66cf
FS-Cache: N-key= '46696c6573'
No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
FS-Cache: Duplicate cookie detected
FS-Cache: O-cookie c=0000000088cf85cb [p=00000000a52bce0c fl=222 nc=0 na=1]
FS-Cache: O-cookie d=00000000ff7a58d3 n=000000005109413d
FS-Cache: O-key= '46696c6573'
FS-Cache: N-cookie c=000000007c6a3385 [p=00000000a52bce0c fl=2 nc=0 na=1]
FS-Cache: N-cookie d=00000000ff7a58d3 n=00000000f006535b
FS-Cache: N-key= '46696c6573'
No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount.
CIFS VFS: \\fileserver2.mydomain.local cannot query dirs between root and final path, enabling CIFS_MOUNT_USE_PREFIX_PATH
CIFS VFS: Autodisabling the use of server inode numbers on new server.
CIFS VFS: The server doesn't seem to support them properly or the files might be on different servers (DFS).
CIFS VFS: Hardlinks will not be recognized on this mount. Consider mounting with the "noserverino" option to silence this message.
CIFS VFS: cifs_read_super: get root inode failed

I believe the "cannot query dirs between root and final path" seems to be the actual problem, as I don't have permission to directly mount either the Share Fileshare$ or somedirectory, but only folder1. I could also directly mount this share on fileserver2, but since on the DFS there are many links to another server, I'd have to mount a whole lot of stuff. I'm in the lucky position to be able to try the mount with an elevated account that *can* access both Fileshare$and somedirectory and when I mount it with that user instead of "myuser", I can access folder1:

# mount -t cifs //mydomain.local/Files ~/fileserver -o username=adminuser,domain=mydomain.local,password=hunter2
# ls ~/fileserver/folder1
file1 file2 file3

But I can't use this elevated account for day to day work - also, I'm not in a position to change the permissions on the DFS share or the fileserver. The interesting part is that smbclient can do the traversal with myuser:

# smbclient '\\mydomain.local\Files' -U 'myuser@mydomain.local'
# smb: \> ls folder1
.
..
file1
file2
file3

I tried a lot of different options to the mount (mostly in desperation):

vers=1.0
vers=3.0
noserverino
sec=ntlmv2
sec=ntlmssp

Has anybody got any idea what else I could try? The DFS share is on a windows server by the way.

I can successfully mount a windows network drive/share using this command: mount -t cfis //servername/sharename /mnt -o 'username=user,sec=ntlmssp' as running this commands prompts a password to be input and then if correct mounts. According to man mount.cifs I should be able to to this. mount -t cfis //servername/sharename /mnt -o 'username=user,password=pwd,sec=ntlmssp' or this PASSWD='pwd' mount -t cfis //servername/sharename /mnt -o 'username=user,sec=ntlmssp' However strangely both those commands fail with this message. mount error(13): Permission denied Now because our company does this "supersmart" thing to require passwords with **special characters** mine does contain a exclamation mark "!". I know that this would have a special meaning to the command line shell, so I have escaped it properly such that if my password was pwd! I would issue those two commands: PASSWD='pwd\!' mount -t cfis //servername/sharename /mnt -o 'username=user,sec=ntlmssp' mount -t cfis //servername/sharename /mnt -o 'username=user,password=pwd\!,sec=ntlmssp' but still it does not work. Connecting to Windows I do not have any particular feeling of urgency to hide my password (of appearing in the bash history) so I would be happy to find a way to skip the password prompt. Mostly I would like to know what the problem is? Lastly I have even tried a credentials file which also did not work.

I have bought an external DVD driver but, after plugging (or booting with the unit already plugged) I see the unit listed in the resources of the computer but I cannot access it: If I try to access the driver via VLC, I get the error VLC is unable to open the MRL 'cdda:///dev/sr0'. The content of fstab is: $ cat /etc/fstab # /etc/fstab: static file system information. # # Use 'blkid' to print the universally unique identifier for a # device; this may be used with UUID= as a more robust way to name devices # that works even if disks are added and removed. See fstab(5). # # # / was on /dev/nvme0n1p2 during installation UUID=341faa1b-4e49-49d7-85a4-e33acecb2212 / ext4 errors=remount-ro 0 1 # /boot/efi was on /dev/nvme0n1p1 during installation UUID=24D6-7429 /boot/efi vfat umask=0077 0 1 /swapfile none swap sw 0 0 What is the right way to plug a DVD in Ubuntu 20.04? Is it a problem with the driver (I need to buy another brand more Linux-prone)? Or do I need to change the permission of the driver with some sudo commands? After I plug the DVD driver I get: $ ls -lt | less | grep sr0 lrwxrwxrwx 1 root root 3 May 27 21:15 cdrom -> sr0 lrwxrwxrwx 1 root root 3 May 27 21:15 cdrw -> sr0 lrwxrwxrwx 1 root root 3 May 27 21:15 dvd -> sr0 lrwxrwxrwx 1 root root 3 May 27 21:15 dvdrw -> sr0 brw-rw----+ 1 root cdrom 11, 0 May 27 21:15 sr0 Thank you

I am mounting a drive via SSH, and then editing the fstab to reflect the changes, however after I reboot, the drive doesnt mount? I dont understand what I'm doing wrong? This is my fstab and its /md0 that isnt mounting after reboot, am I missing something? # /dev/md4 / ext3 errors=remount-ro,usrjquota=quota.user,jqfmt=vfsv0 0 1 /dev/md0 /BACKUP ext3 defaults 0 1 /dev/md1 /boot ext3 errors=remount-ro 0 1 /dev/md2 /var/tmp ext3 usrjquota=quota.user,jqfmt=vfsv0 1 2 /dev/sda3 swap swap defaults 0 0 /dev/sdb3 swap swap defaults 0 0 proc /proc proc defaults 0 0 sysfs /sys sysfs defaults 0 0 tmpfs /dev/shm tmpfs defaults 0 0 devpts /dev/pts devpts defaults 0 0

I am trying to mount hdfs on my local machine running Ubuntu using the following command :--- sudo mount -t nfs -o vers=3,proto=tcp,nolock 192.168.170.52:/ /mnt/hdfs_mount/ But I am getting this error:- mount.nfs: mount system call failed Output for rpcinfo -p 192.168.170.52 is program vers proto port service 100000 4 tcp 111 portmapper 100000 3 tcp 111 portmapper 100000 2 tcp 111 portmapper 100000 4 udp 111 portmapper 100000 3 udp 111 portmapper 100000 2 udp 111 portmapper 100024 1 udp 48435 status 100024 1 tcp 54261 status 100005 1 udp 4242 mountd 100005 2 udp 4242 mountd 100005 3 udp 4242 mountd 100005 1 tcp 4242 mountd 100005 2 tcp 4242 mountd 100005 3 tcp 4242 mountd 100003 3 tcp 2049 nfs Output for showmount -e 192.168.170.52 is Export list for 192.168.170.52: / * I also tried by adding hadoop.proxyuser.root.groups * hadoop.proxyuser.root.hosts * in my core-site.xml file located in /etc/hadoop/conf.pseudo. But it did not work. Please help me with this.

I have searched all over the Internet, and perhaps I missed the answer to this question, but I still cannot solve it yet. So far, I have successfully mounted my QNAP drive: 1. Make a folder for the mount point: /home/t420/QNAP 2. Edit (after getting root privileges) the /etc/fstab file to include the following: - //192.168.x.xxx/homes /home/t420/QNAP nfs defaults - sudo mount -a - For those who are new at this and trying to learn or those trying to understand what the heck I am doing, this is what I understand of the first line I added: - 1st field is the "block device", the address and folder of the device you are trying to mount. - 2nd field is the mount point folder. - 3rd field is the file system type (nfs in my case). - 4th field are mount point options (using defaults). - 5th field is for the ability of a backup utility to dump the file system, or something like that. I've left that field blank for now. 3. The second line in the fstab file is my attempt to automatically mount the NAS drive. The drive fails to mount automatically, although QNAP appears in the list of drives. If I try to click on the QNAP under the list of drives, I get the message - Unable to mount QNAP mount:/home/t420/QNAP: operation permitted for root only. I am able to manually mount the drive: - If I enter root mode by typing su root, then the password, and then type the following: - ***mount -t nfs 192.168.x.xxx/homes:/home/t420/QNAP*** **See error and correction in my comment below** |===============================================================| To make matters more frustrating, I am now unable to mount the drive manually either. I get the message "can't find in /etc/fstab". I typed the mount command exactly as you see it above (with x's replaced by the appropriate address numbers), and the line in the fstab file also exactly as you see it. It seems that it won't recognize my QNAP folder. I really want to love Linux, but this learning curve is very icy right now. What am I doing wrong here?!? Larry