I mount with nfs my HDD usb connected to Rpi. I mount it on my laptops.
NOIP I use for my Nextcloud and Emby server but they work OK.
regards.
I guess you can ignore both error messages if NFS as well as NoIP are running fine
Maybe you should activate FULL Log mode to be able to see what happen if your system crash
Can You tell me how to do this?
Do You think my ISP doing something to block my internet because I use this shadowproxy in deluge? There was no problems when I use openVPN (the same VPS IP) on my laptop and download torrents to my Emby server through NFS share.
Do You think uninstall Webmin will make any difference (I don’t use it hardly at all)?
Regards.
why should a blocking of your ISP result into crashing of your system?
To set your system to full log mode
- dietpi-software
- Log System
- Full
Now, all logs should be written to /var/log. Probably you are able to find anything after your system crashed next time.
Hi, I’m not good at reading logs but I see there’s something in kern.log https://paste.gnome.org/pvqy7oyf1 after connection lost.
There was connection lost at 16:35.
root@Przemas82:/var/log# cat user.log
Dec 1 16:14:40 Przemas82 blkmapd[144]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
Dec 1 16:15:47 Przemas82 redis-server: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Dec 1 16:15:47 Przemas82 redis-server: Redis version=5.0.3, bits=32, commit=00000000, modified=0, pid=855, just started
Dec 1 16:15:47 Przemas82 redis-server: Configuration loaded
Dec 1 16:17:03 Przemas82 blkmapd[144]: open pipe file /run/rpc_pipefs/nfs/blocklayout failed: No such file or directory
Dec 1 16:35:52 Przemas82 redis-server: oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Dec 1 16:35:52 Przemas82 redis-server: Redis version=5.0.3, bits=32, commit=00000000, modified=0, pid=823, just started
Dec 1 16:35:52 Przemas82 redis-server: Configuration loaded
I find that errors in daemon.log. That ss-local is from that proxy installation.
Dec 1 16:33:54 Przemas82 ss-local[580]: 2020-12-01 16:33:35 ERROR: remote_recv_cb_recv: Connection reset by peer
Dec 1 16:34:08 Przemas82 ss-local[580]: 2020-12-01 16:33:45 ERROR: remote_recv_cb_recv: Connection reset by peer
Dec 1 16:34:09 Przemas82 ss-local[580]: 2020-12-01 16:33:53 ERROR: remote_recv_cb_recv: Connection reset by peer
Dec 1 16:34:09 Przemas82 ss-local[580]: 2020-12-01 16:33:53 ERROR: remote_recv_cb_recv: Connection reset by peer
Full log: https://paste.gnome.org/przquqiz2
What Do You think about that?
Regards,
Przemko
for me both links are not working
I made it again.
Daemon.log
https://paste.gnome.org/prrj70vfd
kern.log
https://paste.gnome.org/ppnvtjcot
Not sure why but even on the new files I’m getting the error
The page you are looking for does not exist.
Another try:
Edit. I remove proxy from Deluge and disable <shadowsocks-libev-local@location-of-your-server.service> but that doesn’t help. I still have connection losts. Now Kodi start very long an stuck at Network Time Sync. then was many red entries with errors.
Maybe that my SD-Card is corrupted?
gru 01 22:17:05 Przemas82 systemd[1]: Started Check for Raspberry Pi EEPROM updates.
gru 01 22:17:06 Przemas82 kernel: EXT4-fs (sda): recovery complete
gru 01 22:17:06 Przemas82 kernel: EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: (null)
gru 01 22:17:06 Przemas82 systemd[1]: Mounted /mnt/Toshiba.
gru 01 22:17:14 Przemas82 kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
gru 01 22:17:22 Przemas82 kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
gru 01 22:17:31 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 25212136 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:17:32 Przemas82 systemd[1]: systemd-fsckd.service: Succeeded.
gru 01 22:17:39 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 25212137 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:17:47 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 25212138 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:17:55 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 25212139 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:17:56 Przemas82 systemd[1]: Started DietPi-Arr_to_RAM.
gru 01 22:17:56 Przemas82 systemd[1]: Starting DietPi-PreBoot...
gru 01 22:17:56 Przemas82 DietPi-PreBoot[406]: [ SUB1 ] DietPi-CPU_set > Applying CPU governor settings: ondemand
gru 01 22:17:56 Przemas82 DietPi-PreBoot[406]: [ INFO ] DietPi-CPU_set | Setting up_threshold: 50 %
gru 01 22:17:56 Przemas82 DietPi-PreBoot[406]: [ INFO ] DietPi-CPU_set | Setting sampling_rate: 25000 microseconds
gru 01 22:17:56 Przemas82 DietPi-PreBoot[406]: [ INFO ] DietPi-CPU_set | Setting sampling_down_factor: 40
gru 01 22:17:56 Przemas82 DietPi-PreBoot[406]: [ OK ] DietPi-CPU_set | Applied CPU governor settings: ondemand
gru 01 22:17:56 Przemas82 systemd[1]: Started DietPi-PreBoot.
gru 01 22:17:56 Przemas82 systemd[1]: Reached target Network (Pre).
gru 01 22:17:56 Przemas82 systemd[1]: Started ifup for eth0.
gru 01 22:17:56 Przemas82 systemd[1]: Starting Raise network interfaces...
gru 01 22:17:56 Przemas82 kernel: bcmgenet: Skipping UMAC reset
gru 01 22:17:56 Przemas82 kernel: bcmgenet fd580000.ethernet: configuring instance for external RGMII
gru 01 22:17:56 Przemas82 kernel: bcmgenet fd580000.ethernet eth0: Link is Down
gru 01 22:17:56 Przemas82 systemd[1]: Started Raise network interfaces.
gru 01 22:17:56 Przemas82 systemd[1]: Reached target Network.
gru 01 22:17:56 Przemas82 systemd[1]: Reached target Network is Online.
gru 01 22:17:56 Przemas82 systemd[1]: Starting LSB: disk temperature monitoring daemon...
gru 01 22:17:56 Przemas82 systemd[1]: Starting DietPi-Boot...
gru 01 22:17:56 Przemas82 systemd[1]: Starting Fail2Ban Service...
gru 01 22:17:56 Przemas82 systemd[1]: Condition check resulted in fast remote file copy program daemon being skipped.
gru 01 22:17:56 Przemas82 systemd[1]: Starting Permit User Sessions...
gru 01 22:17:56 Przemas82 systemd[1]: Starting OpenVPN service...
gru 01 22:17:56 Przemas82 systemd[1]: Started Fail2Ban Service.
gru 01 22:17:56 Przemas82 systemd[1]: Started OpenVPN service.
gru 01 22:17:56 Przemas82 systemd[1]: Started Permit User Sessions.
gru 01 22:17:56 Przemas82 DietPi-Boot[525]: [ INFO ] DietPi-Boot | Waiting for valid network connection before continuing boot | Mode=1
gru 01 22:17:56 Przemas82 systemd[1]: Started LSB: disk temperature monitoring daemon.
gru 01 22:17:56 Przemas82 DietPi-Boot[525]: [ OK ] DietPi-Boot | Valid network connection found
gru 01 22:17:57 Przemas82 DietPi-Boot[525]: [ .... ] DietPi-Run_NTPD | systemctl restart systemd-timesyncd
gru 01 22:17:57 Przemas82 systemd[1]: Starting Network Time Synchronization...
gru 01 22:18:02 Przemas82 kernel: bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
gru 01 22:18:02 Przemas82 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
gru 01 22:18:05 Przemas82 kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
gru 01 22:18:13 Przemas82 kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
gru 01 22:18:21 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020144 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:18:30 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020145 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:18:38 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020146 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:18:46 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020147 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:18:54 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020148 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:19:02 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020150 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:19:11 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020151 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:19:19 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020152 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:19:27 Przemas82 systemd[1]: systemd-timesyncd.service: Start operation timed out. Terminating.
gru 01 22:19:27 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020153 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:19:35 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020154 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:19:43 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020155 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:19:52 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020200 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:20:00 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020201 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:20:08 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020202 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:20:16 Przemas82 kernel: blk_update_request: I/O error, dev mmcblk0, sector 24020203 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
gru 01 22:20:16 Przemas82 systemd[1]: systemd-timesyncd.service: Main process exited, code=killed, status=15/TERM
gru 01 22:20:16 Przemas82 systemd[1]: systemd-timesyncd.service: Failed with result 'timeout'.
gru 01 22:20:16 Przemas82 systemd[1]: Failed to start Network Time Synchronization.
gru 01 22:20:16 Przemas82 systemd[1]: systemd-timesyncd.service: Service has no hold-off time (RestartSec=0), scheduling restart.
gru 01 22:20:16 Przemas82 systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 1.
gru 01 22:20:16 Przemas82 systemd[1]: Stopped Network Time Synchronization.
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: [FAILED] DietPi-Run_NTPD | systemctl restart systemd-timesyncd
gru 01 22:20:16 Przemas82 systemd[1]: Starting Network Time Synchronization...
gru 01 22:20:16 Przemas82 DietPi-Boot[525]:
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: ---------------------------------------------------------------------
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - DietPi has encountered an error -
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - Please create a ticket: https://github.com/MichaIng/DietPi/issues -
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - Copy and paste only the BLUE lines below into the ticket -
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: ---------------------------------------------------------------------
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: #### Details:
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - Date | Tue Dec 1 22:20:16 CET 2020
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - DietPi version | v6.33.3 (MichaIng/master)
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - Image creator | DietPi Core Team
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - Pre-image | Raspbian Lite
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - Hardware | RPi 4 Model B (armv7l) (ID=4)
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - Kernel version | Linux Przemas82 5.4.72-v7l+ #1356 SMP Thu Oct 22 13:57:51 BST 2020 armv7l GNU/Linux
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - Distro | buster (ID=5,RASPBIAN=1)
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - Command | systemctl restart systemd-timesyncd
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - Exit code | 1
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - Software title | DietPi-Run_NTPD
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: #### Steps to reproduce:
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: <!-- Explain how to reproduce the issue -->
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: 1. ...
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: 2. ...
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: #### Expected behaviour:
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: <!-- What SHOULD happen? -->
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - ...
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: #### Actual behaviour:
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: <!-- What IS happening? -->
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - ...
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: #### Extra details:
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: <!-- Please post any extra details that might help solve the issue -->
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: - ...
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: #### Additional logs:
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: ```
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: Job for systemd-timesyncd.service failed because a timeout was exceeded.
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: See "systemctl status systemd-timesyncd.service" and "journalctl -xe" for details.
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: ```
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: ---------------------------------------------------------------------
gru 01 22:20:16 Przemas82 DietPi-Boot[525]: [FAILED] DietPi-Run_NTPD | Unable to continue, DietPi-Run_NTPD will now terminate.
gru 01 22:20:16 Przemas82 systemd[1]: Started Network Time Synchronization.
gru 01 22:20:16 Przemas82 systemd[1]: Reached target System Time Synchronized.
gru 01 22:20:16 Przemas82 systemd[1]: Started DietPi-Boot.
gru 01 22:20:16 Przemas82 systemd[1]: Starting OpenBSD Secure Shell server...
gru 01 22:20:16 Przemas82 systemd[1]: Started DietPi-PostBoot.
gru 01 22:20:16 Przemas82 systemd[1]: Started Getty on tty1.
gru 01 22:20:16 Przemas82 systemd[1]: Reached target Login Prompts.
gru 01 22:20:25 Przemas82 kernel: mmc0: Got data interrupt 0x00000002 even though no data operation was in progress.
gru 01 22:31:38 Przemas82 systemd-timesyncd[557]: Synchronized to time server for the first time 194.177.4.2:123 (0.debian.pool.ntp.org).
gru 01 22:31:38 Przemas82 sshd[595]: Server listening on 0.0.0.0 port 22.
gru 01 22:31:38 Przemas82 sshd[595]: Server listening on :: port 22.
Regards.
yes looks like your SD card is dying. You can do following to check both partition.
dosfsck /dev/mmcblk0p1
fsck -a /dev/mmcblk0p2
Hi, today after connection lost I try to restart my Raspberry and it wont run 
Is it possible to rescue my Dietpi installation?
Regards.
best would be to use a USB connector and plug your SD card into another Linux box to be able to run some file system checks
I put my sc-card and start badblocks -n -v.
Boot partition went fast:
sudo badblocks -n -v /dev/mmcblk0p1
Poszukiwanie wadliwych bloków w trybie z niedestruktywnym zapisem
Od bloku 0 do 262143
Testowanie wzorcem losowym: 0
Przebieg zakończony, znaleziono 0 wadliwych bloków (błędów: 0/0/0)
0 Errors.
Rootfs going very slow:
sudo badblocks -n -v /dev/mmcblk0p2
Poszukiwanie wadliwych bloków w trybie z niedestruktywnym zapisem
Od bloku 0 do 30900735
Testowanie wzorcem losowym: 0
12339828
12339829
12339830
12339831
...
It is OK, or stop that test and start another? Do You recommend something different?
Regards.
hi,
I guess you placed the SD card into another system via USB port? If yes, you would need to check /dev/sda1 and /dev/sda2.
/dev/mmcblk0 is the SD card you are booting from
To show all devices connected
lsblk -o name,fstype,label,size,ro,type,mountpoint,partuuid,uuid
I connect sd-card to card reader in my laptop.
When test ends I have 4 corrupted blocks.
sudo badblocks -n -v /dev/mmcblk0p2
Poszukiwanie wadliwych bloków w trybie z niedestruktywnym zapisem
Od bloku 0 do 30900735
Testowanie wzorcem losowym: 0
12339828
12339829
12339830
12339831
Przebieg zakończony, znaleziono 4 wadliwych bloków (błędów: 4/0/0).
I also burn Dietpi image on new sd-card and put it to my Rpi4. I will try to restore my config from HDD. Can I rub Dietpi-Backup and restore?
Regards.
well you could give it a try. Where is the backup stored? On SD Card or HDD?
I store backup on HDD, also move dietpi_userdata to HDD.
ok that might work. But I need to say I never tested this procedure. You would need to verify that user data is linked correctly afterwards.
Can You tell me what to do first: link userddata to HDD and then restore backup, and when to install apps? Or dietpi_backup will restore my apps?
Edit. So I just select location /mint/Toshiba/dietpi_backup search for backup and restore. Then after all I reboot. System stop at:
usually it should be enough to mount the HDD and perform a restore. Everything should be restored as it was saved before. This should include the link of DietPi User data directory. If possible try to do a backup of your HDD to avoid issues if thinks will go wrong. Better to be on safe side.