# Nextcloud problems / questions **URL:** \ **Category:** Troubleshooting\ **Created:** [29 December 2022 13:30 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415 "2022-12-29T13:30:27Z")\ **Posts on this page:** 20\ **Page:** 6
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [12 January 2023 20:17 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/101 "2023-01-12T20:17:55Z")
Hello Jounilar, first of all, many thanks for your patience and all your help! During the holidaytime I started back from scratch with NC All I wanted is just [nextcloud.YourDomain.com](http://nextcloud.YourDomain.com) It seems this is not possible with the standard NC installation and the DietPi ‘[nextcloud.YourDomain.com](http://nextcloud.YourDomain.com) LetsEncrypt script’ ? So manual editing is needed, wright? My only goal is to find out which editing is neccesary to get this working… The standard NC installation with the DietPi ‘[www.YourDomain.com](http://www.YourDomain.com)\nextcloud LetsEncrypt script’ is working out of the box without manual editing? ---
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [12 January 2023 20:20 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/102 "2023-01-12T20:20:49Z")
> [@hemertje](#): > > The standard NC installation with the DietPi ‘[www.YourDomain.com](http://www.YourDomain.com)\nextcloud LetsEncrypt script’ is working out of the box without manual editing? This standard installation should also lead to no Security & setup NC warnings if you ask me ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [12 January 2023 21:00 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/103 "2023-01-12T21:00:18Z")
> [@hemertje](#): > > All I wanted is just [nextcloud.YourDomain.com](http://nextcloud.YourDomain.com) This is possible and takes 5 minutes > [@hemertje](#): > > It seems this is not possible with the standard NC installation and the DietPi ‘[nextcloud.YourDomain.com](http://nextcloud.YourDomain.com) LetsEncrypt script’ ? yes you need to adjust the Nginx config manually. > [@hemertje](#): > > The standard NC installation with the DietPi ‘[www.YourDomain.com](http://www.YourDomain.com)\nextcloud LetsEncrypt script’ is working out of the box without manual editing? Yes this is working ootb > [@hemertje](#): > > My only goal is to find out which editing is neccesary to get this working… already shared [Nextcloud problems / questions - #78 by Joulinar](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/78) ---
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [14 January 2023 20:01 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/104 "2023-01-14T20:01:09Z")
> [@Jappe](#): > > Maybe you run certbot before you set up the subdomain and changed the webroot? So certbot added the line to the default config? Just a guess. Hello @Jappe @Joulinar I think this can be the problem If I remember correct I installed NC via DietPi After this I run the LetsEncrypt with the subdomain + maindomain After that I opened the WebIf from NC and set my personal profile and Administration settings. This is the incorrect way? ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [14 January 2023 20:38 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/105 "2023-01-14T20:38:10Z")
no this should be correct order. ---
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [18 January 2023 20:31 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/106 "2023-01-18T20:31:31Z")
Oke… also regarding the NC subdomain? ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [18 January 2023 22:09 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/107 "2023-01-18T22:09:48Z")
> [@hemertje](#): > > NC subdomain This should not matter. If I understood, you would use just one domain. For the config it’s no difference if it is sub domain or not. ---
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [19 January 2023 20:54 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/108 "2023-01-19T20:54:44Z")
Oke, I’m thinking about starting all over again with NC after setting back a backup with the default DietPi. So we again can follow the files > /etc/nginx/sites-available/default > /etc/nginx/sites-dietpi/dietpi-nextcloud.conf if the default setup goes correct… ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [19 January 2023 20:57 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/109 "2023-01-19T20:57:10Z")
first get your system up to latest DietPi, have NC installed, and SSL configured. Once done we can check. ---
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [20 January 2023 12:18 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/110 "2023-01-20T12:18:40Z")
yes, saw that you guys have an update, nice job! ---
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [28 January 2023 12:28 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/111 "2023-01-28T12:28:14Z")
Oke, starting again 😉 ![image](https://dietpi.com/forum/uploads/default/original/2X/6/6382c688319ab07bb9039315045adb81ce6e60c7.jpeg) ---
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [28 January 2023 13:27 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/112 "2023-01-28T13:27:30Z")
![image](https://dietpi.com/forum/uploads/default/original/2X/0/0704e72b43e408d55dd58825fb1a5eac764f05cf.png) ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [28 January 2023 13:33 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/113 "2023-01-28T13:33:54Z")
Are you willing to share some more words instead of posting a screenshot only? ---
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [29 January 2023 18:39 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/114 "2023-01-29T18:39:59Z")
Sorry! Ofcourse Joulinar… Was on my way out to the Awakenings festival and I forgot to enter the Send button ☺ I started from scratch and formatted my newly bought drive I got this HDD error also last december MichaIng tipped me to run a HDD check. Gonna find it in the history Is such an error normal with a new HDD? Or should I return it under warranty? ---
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [29 January 2023 19:10 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/115 "2023-01-29T19:10:28Z")
Got stuck with ```auto root@DietPi:~# dietpi-launcher [INFO] DietPi-Drive_Manager | Detecting drives, please wait... [INFO] DietPi-Drive_Manager | - Detected mounted physical drive: /dev/mmcblk2p1 > / [INFO] DietPi-Drive_Manager | - Detected unmounted drive: /dev/sda1 [OK] DietPi-Drive_Manager | mv .fstab /etc/fstab [OK] DietPi-Drive_Manager | systemctl daemon-reload [INFO] DietPi-Drive_Manager | Checking for required APT packages: e2fsprogs e2fsprogs [OK] DietPi-Drive_Manager | sync [INFO] DietPi-Drive_Manager | Erasing partition: /dev/sda1 [OK] DietPi-Drive_Manager | dd if=/dev/zero of=/dev/sda1 bs=4K count=1337 [FAILED] DietPi-Drive_Manager | mkfs.ext4 -F -m 0 /dev/sda1 [INFO] DietPi-Drive_Manager | Detecting drives, please wait... [INFO] DietPi-Drive_Manager | - Detected mounted physical drive: /dev/mmcblk2p1 > / [INFO] DietPi-Drive_Manager | - Detected unformatted drive: /dev/sda [OK] DietPi-Drive_Manager | mv .fstab /etc/fstab [OK] DietPi-Drive_Manager | systemctl daemon-reload [INFO] DietPi-Drive_Manager | Checking for required APT packages: e2fsprogs [OK] DietPi-Drive_Manager | sync [INFO] DietPi-Drive_Manager | Detecting drives, please wait... [INFO] DietPi-Drive_Manager | - Detected mounted physical drive: /dev/mmcblk2p1 > / [INFO] DietPi-Drive_Manager | - Detected unformatted drive: /dev/sda [OK] DietPi-Drive_Manager | mv .fstab /etc/fstab [OK] DietPi-Drive_Manager | systemctl daemon-reload [OK] DietPi-Drive_Manager | sync [INFO] DietPi-Drive_Manager | Writing zeros to partition: /dev/sda1 [OK] DietPi-Drive_Manager | dd if=/dev/zero of=/dev/sda1 bs=4K count=10 [INFO] DietPi-Drive_Manager | Erasing partition table: /dev/sda [OK] DietPi-Drive_Manager | dd if=/dev/zero of=/dev/sda bs=4K count=1337 [INFO] DietPi-Drive_Manager | Creating new gpt partition table [FAILED] DietPi-Drive_Manager | parted -s /dev/sda mklabel gpt ``` ---
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [29 January 2023 19:17 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/116 "2023-01-29T19:17:01Z")
```auto --------------------------------------------------------------------- - DietPi has encountered an error - - Please create a ticket: https://github.com/MichaIng/DietPi/issues - - Copy and paste only the BLUE lines below into the ticket - --------------------------------------------------------------------- #### Details: - Date | Sun Jan 29 20:08:40 CET 2023 - DietPi version | v8.13.2 (MichaIng/master) - Image creator | DietPi Core Team - Pre-image | from scratch - Hardware | ROCKPro64 (aarch64) (ID=42) - Kernel version | `Linux DietPi 5.15.89-rockchip64 #22.11.4 SMP PREEMPT Mon Jan 23 22:01:54 UTC 2023 aarch64 GNU/Linux` - Distro | bullseye (ID=6) - Command | `parted -s /dev/sda mklabel gpt` - Exit code | 1 - Software title | DietPi-Drive_Manager #### Steps to reproduce: 1. ... 2. ... #### Expected behaviour: - ... #### Actual behaviour: - ... #### Extra details: - ... #### Additional logs: ``` ```auto --------------------------------------------------------------------- [FAILED] DietPi-Drive_Manager | Unable to continue, DietPi-Drive_Manager will now terminate. - Press any key to return to DietPi-Launcher...^[[B^[[B^[[B^[[B root@DietPi:~# ``` ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [29 January 2023 19:23 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/117 "2023-01-29T19:23:53Z")
anything on kernel error messages? ```auto dmesg -l err,crit,alert,emerg ``` ---
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [30 January 2023 20:06 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/118 "2023-01-30T20:06:23Z")
```auto root@DietPi:~# dmesg -l err,crit,alert,emerg [1.458186] rockchip-usb2phy ff770000.syscon:usb2phy@e450: failed to create phy [1.459230] rockchip-usb2phy ff770000.syscon:usb2phy@e460: failed to create phy [5.755179] rk_gmac-dwmac fe300000.ethernet: cannot get clock clk_mac_speed [8.559667] typec_fusb302 4-0022: Failed to allocate extcon device: -22 [573.800688] ata1.00: exception Emask 0x10 SAct 0x1ff80 SErr 0x400000 action 0x6 frozen [573.801463] ata1.00: irq_stat 0x08000000, interface fatal error [573.802017] ata1: SError: { Handshk } [573.802382] ata1.00: failed command: WRITE FPDMA QUEUED [573.802872] ata1.00: cmd 61/40:38:00:a0:10/05:00:23:01:00/40 tag 7 ncq dma 688128 out res 40/00:80:40:c5:10/00:00:23:01:00/40 Emask 0x10 (ATA bus error) [573.804348] ata1.00: status: { DRDY } [573.804774] ata1.00: failed command: WRITE FPDMA QUEUED [573.805271] ata1.00: cmd 61/c0:40:40:a5:10/02:00:23:01:00/40 tag 8 ncq dma 360448 out res 40/00:80:40:c5:10/00:00:23:01:00/40 Emask 0x10 (ATA bus error) [573.806758] ata1.00: status: { DRDY } [573.807116] ata1.00: failed command: WRITE FPDMA QUEUED [573.807607] ata1.00: cmd 61/40:48:00:a8:10/05:00:23:01:00/40 tag 9 ncq dma 688128 out res 40/00:80:40:c5:10/00:00:23:01:00/40 Emask 0x10 (ATA bus error) [573.809143] ata1.00: status: { DRDY } [573.809510] ata1.00: failed command: WRITE FPDMA QUEUED [573.810002] ata1.00: cmd 61/c0:50:40:ad:10/02:00:23:01:00/40 tag 10 ncq dma 360448 out res 40/00:80:40:c5:10/00:00:23:01:00/40 Emask 0x10 (ATA bus error) [573.811495] ata1.00: status: { DRDY } [573.811853] ata1.00: failed command: WRITE FPDMA QUEUED [573.812344] ata1.00: cmd 61/40:58:00:b0:10/05:00:23:01:00/40 tag 11 ncq dma 688128 out res 40/00:80:40:c5:10/00:00:23:01:00/40 Emask 0x10 (ATA bus error) [573.813879] ata1.00: status: { DRDY } [573.814243] ata1.00: failed command: WRITE FPDMA QUEUED [573.814734] ata1.00: cmd 61/c0:60:40:b5:10/02:00:23:01:00/40 tag 12 ncq dma 360448 out res 40/00:80:40:c5:10/00:00:23:01:00/40 Emask 0x10 (ATA bus error) [573.816228] ata1.00: status: { DRDY } [573.816622] ata1.00: failed command: WRITE FPDMA QUEUED [573.817116] ata1.00: cmd 61/40:68:00:b8:10/05:00:23:01:00/40 tag 13 ncq dma 688128 out res 40/00:80:40:c5:10/00:00:23:01:00/40 Emask 0x10 (ATA bus error) [573.818609] ata1.00: status: { DRDY } [573.818967] ata1.00: failed command: WRITE FPDMA QUEUED [573.819456] ata1.00: cmd 61/c0:70:40:bd:10/02:00:23:01:00/40 tag 14 ncq dma 360448 out res 40/00:80:40:c5:10/00:00:23:01:00/40 Emask 0x10 (ATA bus error) [573.820992] ata1.00: status: { DRDY } [573.821355] ata1.00: failed command: WRITE FPDMA QUEUED [573.821847] ata1.00: cmd 61/40:78:00:c0:10/05:00:23:01:00/40 tag 15 ncq dma 688128 out res 40/00:80:40:c5:10/00:00:23:01:00/40 Emask 0x10 (ATA bus error) [573.823339] ata1.00: status: { DRDY } [573.823698] ata1.00: failed command: WRITE FPDMA QUEUED [573.824188] ata1.00: cmd 61/c0:80:40:c5:10/02:00:23:01:00/40 tag 16 ncq dma 360448 out res 40/00:80:40:c5:10/00:00:23:01:00/40 Emask 0x10 (ATA bus error) [573.825712] ata1.00: status: { DRDY } [583.826089] ata1: softreset failed (1st FIS failed) [593.826633] ata1: softreset failed (1st FIS failed) [628.829767] ata1: softreset failed (1st FIS failed) [633.829929] ata1: softreset failed (1st FIS failed) [633.830440] ata1: reset failed, giving up [633.831943] blk_update_request: I/O error, dev sda, sector 4883259392 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 0 [633.833068] blk_update_request: I/O error, dev sda, sector 4883260736 op 0x1:(WRITE) flags 0x0 phys_seg 88 prio class 0 [633.834182] blk_update_request: I/O error, dev sda, sector 4883261440 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 0 [633.835262] blk_update_request: I/O error, dev sda, sector 4883262784 op 0x1:(WRITE) flags 0x0 phys_seg 88 prio class 0 [633.836307] blk_update_request: I/O error, dev sda, sector 4883263488 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 0 [633.837373] blk_update_request: I/O error, dev sda, sector 4883264832 op 0x1:(WRITE) flags 0x0 phys_seg 88 prio class 0 [633.838454] blk_update_request: I/O error, dev sda, sector 4883265536 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 0 [633.839523] blk_update_request: I/O error, dev sda, sector 4883266880 op 0x1:(WRITE) flags 0x0 phys_seg 88 prio class 0 [633.840564] blk_update_request: I/O error, dev sda, sector 4883267584 op 0x1:(WRITE) flags 0x4000 phys_seg 168 prio class 0 [633.841632] blk_update_request: I/O error, dev sda, sector 4883268928 op 0x1:(WRITE) flags 0x0 phys_seg 88 prio class 0 [633.846135] Buffer I/O error on dev sda1, logical block 0, lost async page write [633.846977] Buffer I/O error on dev sda1, logical block 584, lost async page write [633.847707] Buffer I/O error on dev sda1, logical block 585, lost async page write [633.848427] Buffer I/O error on dev sda1, logical block 586, lost async page write [633.849148] Buffer I/O error on dev sda1, logical block 587, lost async page write [633.849915] Buffer I/O error on dev sda1, logical block 588, lost async page write [633.850640] Buffer I/O error on dev sda1, logical block 589, lost async page write [633.851358] Buffer I/O error on dev sda1, logical block 590, lost async page write [633.852077] Buffer I/O error on dev sda1, logical block 591, lost async page write [633.852795] Buffer I/O error on dev sda1, logical block 592, lost async page write [108280.999514] blk_update_request: I/O error, dev sda, sector 67584 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0[108281.000695] blk_update_request: I/O error, dev sda, sector 67584 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [108281.001625] Buffer I/O error on dev sda1, logical block 8192, async page read [108281.002456] blk_update_request: I/O error, dev sda, sector 67584 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [108281.003372] Buffer I/O error on dev sda1, logical block 8192, async page read [108281.004491] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 [108281.005837] blk_update_request: I/O error, dev sda, sector 133120 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [108281.007075] blk_update_request: I/O error, dev sda, sector 133120 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [108281.008055] Buffer I/O error on dev sda1, logical block 16384, async page read [108281.008931] blk_update_request: I/O error, dev sda, sector 133120 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [108281.009858] Buffer I/O error on dev sda1, logical block 16384, async page read [108281.010786] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x800 phys_seg 0 prio class 0 [108281.011884] blk_update_request: I/O error, dev sda, sector 264192 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [108281.013153] blk_update_request: I/O error, dev sda, sector 264192 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [108281.014021] Buffer I/O error on dev sda1, logical block 1220942320, async page read [108281.014128] Buffer I/O error on dev sda1, logical block 32768, async page read [108281.015781] Buffer I/O error on dev sda1, logical block 32768, async page read [108281.017586] Buffer I/O error on dev sda1, logical block 65536, async page read [108281.018592] Buffer I/O error on dev sda1, logical block 65536, async page read [108281.020562] Buffer I/O error on dev sda1, logical block 131072, async page read [108325.007506] blk_update_request: I/O error, dev sda, sector 9767540608 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [108325.008949] blk_update_request: I/O error, dev sda, sector 9767540608 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [108325.009966] Buffer I/O error on dev sda1, logical block 1220942320, async page read [108341.384556] blk_update_request: I/O error, dev sda, sector 9767540608 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [108341.386039] blk_update_request: I/O error, dev sda, sector 9767540608 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [108341.387047] Buffer I/O error on dev sda1, logical block 1220942320, async page read [108373.820502] blk_update_request: I/O error, dev sda, sector 2048 op 0x1:(WRITE) flags 0x800 phys_seg 10 prio class 0 [108373.821478] Buffer I/O error on dev sda1, logical block 0, lost async page write [108373.822188] Buffer I/O error on dev sda1, logical block 1, lost async page write [108373.822871] Buffer I/O error on dev sda1, logical block 2, lost async page write [108373.823559] Buffer I/O error on dev sda1, logical block 3, lost async page write [108373.824280] Buffer I/O error on dev sda1, logical block 4, lost async page write [108373.824988] Buffer I/O error on dev sda1, logical block 5, lost async page write [108373.825698] Buffer I/O error on dev sda1, logical block 6, lost async page write [108373.826413] Buffer I/O error on dev sda1, logical block 7, lost async page write [108373.827117] Buffer I/O error on dev sda1, logical block 8, lost async page write [108373.827855] Buffer I/O error on dev sda1, logical block 9, lost async page write [108373.833553] blk_update_request: I/O error, dev sda, sector 9767540608 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 [108373.834842] blk_update_request: I/O error, dev sda, sector 9767540608 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 [108373.897774] blk_update_request: I/O error, dev sda, sector 0 op 0x1:(WRITE) flags 0x4800 phys_seg 168 prio class 0 [108373.899650] sd 0:0:0:0: [sda] tag#18 access beyond end of device [108373.900201] blk_update_request: I/O error, dev sda, sector 1344 op 0x1:(WRITE) flags 0x800 phys_seg 9 prio class 0 root@DietPi:~# ``` ---
**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\ **Post date:** [30 January 2023 20:17 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/119 "2023-01-30T20:17:53Z")
quite a lot of I/O errors on your disc. Check cable and PSU on your HDD. ---
**Author:** ![hemertje](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/h/cdc98d/32.png) [@hemertje](https://dietpi.com/forum/u/hemertje)\ **Post date:** [1 February 2023 19:04 UTC](https://dietpi.com/forum/t/nextcloud-problems-questions/15415/120 "2023-02-01T19:04:42Z")
Hi Joulinar, used the other port on the PCIe adapter … ![Afbeelding van WhatsApp op 2023-02-01 om 20.03.10](https://dietpi.com/forum/uploads/default/original/2X/c/c5944bc19f6fd3dd1b478e05e2be6827b50e8ac6.jpeg) No problems anymore [Previous page](https://dietpi.com/forum/t/nextcloud-problems-questions/15415.md?page=5) [Next page](https://dietpi.com/forum/t/nextcloud-problems-questions/15415.md?page=7)