Closed BETEP-ok closed 6 years ago
nachoparker
commented
6 years ago good enough the trick with /usr/local/etc/nc-automount-links worked and symlink popped up, but it doesn't seem like a bulletproof solution.
can you explain this "trick"? does it survive a reboot? if it doesn't, what's the output of
systemctl status nc-automount-linksAlso, please include the output of sudo ncp-report
BETEP-ok
commented
6 years ago Hi )) sure thing.
steps 2 reproduce:
1 fresh instal the ncp, set it up, change default passwords 2 nc-database until first reboot everything works. but after reboot- the USBdrive symlink is lost:
ls -l /media/
total 16
drwxr-xr-x 1 root root 20 Dec 15 19:44 myCloudDrivesystemctl status nc-automount-links
● nc-automount-links.service - Monitor /media for mountpoints and create USBdrive* symlinks
Loaded: loaded (/usr/lib/systemd/system/nc-automount-links.service; enabled; vendor preset: enabled)
Active: active (running) since Tue 2017-12-26 09:56:31 UTC; 39s ago
Main PID: 353 (nc-automount-li)
CGroup: /system.slice/nc-automount-links.service
├─353 /bin/bash /usr/local/etc/nc-automount-links-mon
├─372 inotifywait --monitor --event create --event delete --format %f %e /media/
├─373 grep --line-buffered ISDIR
└─374 /bin/bash /usr/local/etc/nc-automount-links-mon
Dec 26 09:56:31 nextcloudpi systemd[1]: Started Monitor /media for mountpoints and create USBdrive* symlinks.
Dec 26 09:56:31 nextcloudpi nc-automount-links-mon[353]: Setting up watches.
Dec 26 09:56:31 nextcloudpi nc-automount-links-mon[353]: Watches established.
Dec 26 09:56:38 nextcloudpi nc-automount-links-mon[353]: myCloudDrive DELETE,ISDIR
Dec 26 09:56:43 nextcloudpi nc-automount-links-mon[353]: myCloudDrive CREATE,ISDIR3 then I do the trick described in #181 : "Try this command and let's see if the links appear
/usr/local/etc/nc-automount-links
ls -l /media"
pi@nextcloudpi:~ $ sudo /usr/local/etc/nc-automount-links
pi@nextcloudpi:~ $ ls -l /media
total 16
drwxr-xr-x 1 root root 20 Dec 15 19:44 myCloudDrive
lrwxrwxrwx 1 root root 19 Dec 26 10:02 USBdrive -> /media/myCloudDrivethe USBdrive is back. but this symlink only stays until the next reboot. After the reboot- have to trigger the "sudo /usr/local/etc/nc-automount-links" again.
nachoparker
commented
6 years ago that is weird... nc-automount-links is enabled and it detects the drive mount
Dec 26 09:56:43 nextcloudpi nc-automount-links-mon[353]: myCloudDrive CREATE,ISDIRplease, include the output of sudo ncp-report to see if I get some ideas.
Anyhow, it is recommended that you use myCloudDrive where possible, because also if you plug in another USB drive, you have no guarantees as of which one will be USBdrive and which one USBdrive1. It is better to use labels always if you know them.
I would change to myCloudDrive in the mysqld configuration file, and really everywhere (config.php if you used nc-datadir, and so on)
BETEP-ok
commented
6 years ago hi again. well... on one side - "you are god damn right" on the other - I specifically purchased this raps in order to have it as a dedicated file server. So 99 percent of the time it is supposed to stay ON and that usb drive connected to it. The setup wizard don't offer an alternative - so as a stupid user I rely on the default setting as a correct one. and now I am simply scared t change anything in the existing set up because I don't want to upload 200 gigs of family photos again ) so IF changing the USBdrive symlink => to /media/myCloudDrive goes beyond just using the nc-database script - I don`t dare to play with the settings deeper. )))
I think I will rarely connect additional USB drives to that machine. so most probably this will not be an issue for me, but I can easily imagine other users building more complicated set ups, utilising all the USB ports of the PI. so I guess the wizard routing needs to be adjusted.
as requested - sudo ncp-report:
<--! Paste this in GitHub report -->
nachoparker
commented
6 years ago Well, I see no reason why the link dissappears, because as shown in the output of systemctl status nc-automount-links, the drive dir creation is detected...
In any case, if you are scared to play around and want a quick solution, you can copy and paste these commands and you should be good to go, as long as you don't touch the setting again
sudo /usr/local/etc/nc-automount-links
sudo systemctl disable nc-automount-links
sudo ln -s /media/myCloudDrive /media/USBdriveIf someone else is seeing the same, please reopen and see if we can detect what's going on. It is strange that noone else has reported this.
BETEP-ok
commented
6 years ago hi again, @nachoparker
I generated the report AFTER the symlink was re-generated (manually)
stupid me.
will make another one tonight right after the reboot - maybe you can find a hint why its not being generated.
nachoparker
commented
6 years ago sure, we'll do that
BETEP-ok
commented
6 years ago hi, @nachoparker
as promised- sudo ncp-report right after reboot
nachoparker
commented
6 years ago thanks, what I am interested in is the output right after reboot of
systemctl status nc-automount-linksAlso, you can try if the above solution works for you
BETEP-ok
commented
6 years ago hi, again, @nachoparker
soo... I did a reboot, and the output of systemctl status nc-automount-links:
systemctl status nc-automount-links
● nc-automount-links.service - Monitor /media for mountpoints and create USBdriv
Loaded: loaded (/usr/lib/systemd/system/nc-automount-links.service; enabled;
Active: active (running) since Thu 2018-01-04 19:40:25 UTC; 47s ago
Main PID: 352 (nc-automount-li)
CGroup: /system.slice/nc-automount-links.service
├─352 /bin/bash /usr/local/etc/nc-automount-links-mon
├─388 inotifywait --monitor --event create --event delete --format %f
├─389 grep --line-buffered ISDIR
└─390 /bin/bash /usr/local/etc/nc-automount-links-mon
Jan 04 19:40:25 nextcloudpi systemd[1]: Started Monitor /media for mountpoints a
Jan 04 19:40:26 nextcloudpi nc-automount-links-mon[352]: Setting up watches.
Jan 04 19:40:26 nextcloudpi nc-automount-links-mon[352]: Watches established.
Jan 04 19:40:29 nextcloudpi nc-automount-links-mon[352]: myCloudDrive DELETE,ISD
Jan 04 19:40:38 nextcloudpi nc-automount-links-mon[352]: myCloudDrive CREATE,ISD
lines 1-15/15 (END)now I do the proposed magic:
sudo /usr/local/etc/nc-automount-links sudo systemctl disable nc-automount-links sudo ln -s /media/myCloudDrive /media/USBdrive
and trigger again the systemctl status nc-automount-links
● nc-automount-links.service - Monitor /media for mountpoints and create USBdrive* symlinks
Loaded: loaded (/usr/lib/systemd/system/nc-automount-links.service; disabled; vendor preset: enabled)
Active: active (running) since Thu 2018-01-04 19:40:25 UTC; 2min 27s ago
Main PID: 352 (nc-automount-li)
CGroup: /system.slice/nc-automount-links.service
├─352 /bin/bash /usr/local/etc/nc-automount-links-mon
├─388 inotifywait --monitor --event create --event delete --format %f %e /media/
├─389 grep --line-buffered ISDIR
└─390 /bin/bash /usr/local/etc/nc-automount-links-mon
Jan 04 19:40:25 nextcloudpi systemd[1]: Started Monitor /media for mountpoints and create USBdrive* symlinks.
Jan 04 19:40:26 nextcloudpi nc-automount-links-mon[352]: Setting up watches.
Jan 04 19:40:26 nextcloudpi nc-automount-links-mon[352]: Watches established.
Jan 04 19:40:29 nextcloudpi nc-automount-links-mon[352]: myCloudDrive DELETE,ISDIR
Jan 04 19:40:38 nextcloudpi nc-automount-links-mon[352]: myCloudDrive CREATE,ISDIRnow the symlink in /media is back again.
media $ ls
myCloudDrive USBdrivenow again - reboot.....
aaand... symlink stays in /media:
/media $ ls
myCloudDrive USBdriveSweet! your kung-fu is better then mine ) but still don`t get it why this problem happens at all with a fresh installation. )
nachoparker
commented
6 years ago but still don`t get it why this problem happens at all with a fresh installation
Me neither, because we can se the detection working
Jan 04 19:40:38 nextcloudpi nc-automount-links-mon[352]: myCloudDrive CREATE,ISDIR
At least the workaround works for you...
cp2732
commented
4 years ago @nachoparker, I am getting a similar issue when trying to use an already formatted USB drive using the btrfs filesystem. I originally formatted this USB drive using a different NextCloud instance on a separate 4GB SD card. After I upgraded to a new 64GB SD card using NextCloud, I decided to compare my old NextCloud configuration with the new one and keep the configurations I desired to keep. I did this by plugging in a SD to USB thumb drive, since the Raspberry Pi does not have another SD slot. For this, I manually mounted this thumb drive using
sudo mkdir -p /media/old
sudo mount -t ext4 -o defaults /dev/sda1 /media/oldand unmounted with
sudo umount /media/old
Since I also had a bunch of data on a separate 5TB external USB hard drive, I tried to plug that into the Raspberry Pi with the new SD card, but cannot get the drive to automount, even if automount was enabled though the web-ui.
Here's what I got using sudo lsblk --fs:
NAME FSTYPE LABEL UUID FSAVAIL FSUSE% MOUNTPOINT
sda
└─sda1 btrfs myCloudDrive 4b5da605-a5b6-4d06-a62f-e2cf9e543662
mmcblk0
├─mmcblk0p1 vfat boot 4BBD-D3E7 199M 21% /boot
└─mmcblk0p2 ext4 rootfs 45e99191-771b-4e12-a526-0779148892cb 53.8G 4% /Before I ran the three commands suggested above
sudo /usr/local/etc/nc-automount-links
sudo systemctl disable nc-automount-links
sudo ln -s /media/myCloudDrive /media/USBdriveI got:
● nc-automount-links.service - Monitor /media for mountpoints and create USBdrive* symlinks
Loaded: loaded (/usr/lib/systemd/system/nc-automount-links.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2020-06-21 11:03:29 EDT; 1min 35s ago
Main PID: 340 (nc-automount-li)
Tasks: 4 (limit: 4915)
Memory: 2.1M
CGroup: /system.slice/nc-automount-links.service
├─340 /bin/bash /usr/local/etc/nc-automount-links-mon
├─353 inotifywait --monitor --event create --event delete --format %f %e /media/
├─354 grep --line-buffered ISDIR
└─355 /bin/bash /usr/local/etc/nc-automount-links-mon
Jun 21 11:03:29 top-notch-ncp systemd[1]: Started Monitor /media for mountpoints and create USBdrive* symlinks.
Jun 21 11:03:29 top-notch-ncp nc-automount-links-mon[340]: Setting up watches.
Jun 21 11:03:29 top-notch-ncp nc-automount-links-mon[340]: Watches established.
Jun 21 11:03:42 top-notch-ncp nc-automount-links-mon[340]: myCloudDrive CREATE,ISDIR
Jun 21 11:03:42 top-notch-ncp nc-automount-links-mon[340]: myCloudDrive DELETE,ISDIRAfter running those three commands and rebooting, I now get
systemctl status nc-automount-links
● nc-automount-links.service - Monitor /media for mountpoints and create USBdrive* symlinks
Loaded: loaded (/usr/lib/systemd/system/nc-automount-links.service; disabled; vendor preset: enabled)
Active: inactive (dead)I am using NextCloud version 18.0.6 and NextCloudPi version 1.26.2. I have not changed the data directory yet from the default, but when I try to run nc-datadir in the UI wizard, I get
/media/USBdrive does not exist
I would be grateful if there is a way that exists, where I do not need to reformat the USB drive.
weiw11
commented
4 years ago This looks similar to https://github.com/nextcloud/nextcloudpi/issues/1084
Try following this post and see if that helps.
The most common symptoms of a misbehaving UAS device are
- Extremely slow performance - in the kilobytes per second range
- Frequent disconnects-reconnects of the device with the desktop repeatedly displaying the "removable medium inserted" dialogue box
- The kernel message log (dmesg) reports errors relating to a UAS device that look like this:
[ 501.594683] usbcore: registered new interface driver usb-storage [ 501.599729] scsi host6: uas [ 501.599800] usbcore: registered new interface driver uas ... [ 573.203294] sd 6:0:0:0: [sda] tag#29 uas_eh_abort_handler 0 uas-tag 9 inflight: CMD OUT [ 573.203302] sd 6:0:0:0: [sda] tag#29 CDB: Write(10) 2a 00 00 4f a0 00 00 04 00 00 [ 573.205063] sd 6:0:0:0: [sda] tag#28 uas_eh_abort_handler 0 uas-tag 10 inflight: CMD OUT [ 573.205070] sd 6:0:0:0: [sda] tag#28 CDB: Write(10) 2a 00 00 4f a4 00 00 04 00 00 [ 573.208537] sd 6:0:0:0: [sda] tag#27 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD OUT ... [ 573.269992] scsi host6: uas_eh_device_reset_handler start [ 573.393710] usb 2-4: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd [ 573.414256] scsi host6: uas_eh_device_reset_handler success
as a followup to #181
sorry to say, but I also have issues with the fresh install of NextcloudPi
after fresh install nd configuration- every time I reboot- the symlink is lost. I still can see my usb drive as /media/myCloudDrive but /media/USBDrive is just not there.
good enough the trick with /usr/local/etc/nc-automount-links worked and symlink popped up, but it doesn't seem like a bulletproof solution.
I don't want to type in ssh commands after every powerloss )))
nextcloudpi ver 0.43.1 (the latest as of now)