# SSD goes missing...possible connection with samba? **URL:** https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192 **Category:** Troubleshooting **Created:** [10 June 2020 21:13 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192 "2020-06-10T21:13:50Z") **Posts on this page:** 13 **Page:** 1
### Author: ![Pillendreher](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/p/a698b9/32.png) [@Pillendreher](https://dietpi.com/forum/u/Pillendreher) #### Post date: [10 June 2020 21:13 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/1 "2020-06-10T21:13:50Z")
Evening everybody, first of all I would like to thank the team for coming up with DietPi. It has been a very nice experience with my Raspberry Pi 4 so far due to DietPi 🙂 Now to the issue at hand: For whatever reason, a certain kind of load seems to make my SSD go AWOL. I’m using a external case and have had no problems whatsoever, but lately I’ve been experiencing some weird issues. Writing to the drive via the Raspberry Pi works wonderfully, yet the drive has disappeared on me a couple of times now when accessing it. Mainly via a Windows PC accessing the SSD as a Samba share, but I have seen the same thing happening during an FTP download: The transfer rate drops and I can’t access the drive anymore, not even on the Raspberry Pi. Something I’ve noticed when this happens is that the DietPi Drive Manager is not showing me the drive’s xfs filesystem, but this: ![](https://i.imgur.com/OtoqpCQ.png) ![](https://i.imgur.com/wxELAZX.png) I have never heard of a filesystem called “Net”. And it also looks like all the other options for the drive are gone. Does the Raspberry Pi think that my external drive has suddenly become a mounted network share from another computer? Trying to run “ls” in the mount point’s folder gives me an I/O error message. After restarting the Raspberry Pi, the drive manager shows me this: ![](https://i.imgur.com/QRBwzIL.png) ![](https://i.imgur.com/pOqI6DM.png) As you can see, the other options are back again and I can actually mount the drive without a single issue. I’ve tried to find a solution to this problem, but to be honest, I can’t even tell what’s going on. It has been quite some since I’ve dealt with linux and while I assume that something causes the connection to the drive to be disrupted, I wouldn’t even know where to look for the source of this whole thing. I’d appreciate if you guys could lend me a hand here. Cheers EDIT: I was just able to recreate the issue: Running a ffmpeg command turning f4v files into mp4 while copying all streams, the drive crashed on me again. After restarting, mounting the drive, stopping both nmbd and smbd and running ffmpeg again, I had no issue and all files were successfully created. To me this points straight at the sharing the drive via Samba. Any way I can log what’s going on when the crash happens? ---
### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar) #### Post date: [10 June 2020 21:21 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/2 "2020-06-10T21:21:59Z")
Hi, many thanks for your report. Once your drive disappear, you could have a look to kernel error messages. Maybe you can find some error messages regarding usb devices. ```nohighlight dmesg -l err,crit,alert,emerg ``` As well you can check status of the USB device ```nohighlight lsblk -o name,label,size,ro,type,mountpoint,partuuid,uuid ``` Does you external case has it’s own power supply? ---
### Author: ![Pillendreher](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/p/a698b9/32.png) [@Pillendreher](https://dietpi.com/forum/u/Pillendreher) #### Post date: [10 June 2020 21:25 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/3 "2020-06-10T21:25:17Z")
> [@](#): > > Hi, > > many thanks for your report. Once your drive disappear, you could have a look to kernel error messages. Maybe you can find some error messages regarding usb devices. > > ```plaintext > dmesg -l err,crit,alert,emerg > > ``` > > As well you can check status of the USB device > > ```plaintext > lsblk -o name,label,size,ro,type,mountpoint,partuuid,uuid > > ``` > > Thanks for the commands I’ll try to duplicate the conditions and post whatever I came up with 🙂 > > > [@](#): > > > > Does you external case has it’s own power supply? > > Nope, it’s one of those cases that solely rely on the USB port to provide enough power. ---
### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar) #### Post date: [10 June 2020 21:38 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/4 "2020-06-10T21:38:57Z")
we highly recommend to use an external power supply for your SSD. We have seen a couple of messages where external HDD/SDD had quite some issues running just connected to USB port. In most of cases, issues are gone once connected to own power. ---
### Author: ![Pillendreher](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/p/a698b9/32.png) [@Pillendreher](https://dietpi.com/forum/u/Pillendreher) #### Post date: [10 June 2020 22:44 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/5 "2020-06-10T22:44:00Z")
> [@](#): > > we highly recommend to use an external power supply for your SSD. We have seen a couple of messages where external HDD/SDD had quite some issues running just connected to USB port. In most of cases, issues are gone once connected to own power. Thanks, I’ll look into that. * * * I just managed to force another crash. ```plaintext root@DietPi:~# dmesg -l err,crit,alert,emerg [5335.445477] xhci_hcd 0000:01:00.0: xHCI host controller not responding, assume dead [5335.447503] xhci_hcd 0000:01:00.0: HC died; cleaning up [5335.525443] print_req_error: I/O error, dev sda, sector 367394728 [5335.525497] print_req_error: I/O error, dev sda, sector 367390632 [5335.525537] print_req_error: I/O error, dev sda, sector 367387560 [5335.525576] print_req_error: I/O error, dev sda, sector 367388584 [5335.525615] print_req_error: I/O error, dev sda, sector 367392680 [5335.525651] print_req_error: I/O error, dev sda, sector 361440792 [5335.525660] print_req_error: I/O error, dev sda, sector 361439768 [5335.525673] print_req_error: I/O error, dev sda, sector 367396776 [5335.525686] print_req_error: I/O error, dev sda, sector 361455128 [5335.525701] print_req_error: I/O error, dev sda, sector 361456152 [5335.533666] XFS (sda1): writeback error on sector 361437720 [5335.537049] XFS (sda1): writeback error on sector 361486872 [5335.539202] XFS (sda1): writeback error on sector 361462296 [5335.539232] XFS (sda1): metadata I/O error in "xlog_iodone" at daddr 0xee7b080 len 64 error 5 [5335.539302] XFS (sda1): Log I/O Error Detected. Shutting down filesystem [5335.539313] XFS (sda1): Please umount the filesystem and rectify the problem(s) [5335.583470] XFS (sda1): writeback error on sector 330838608 ``` ```plaintext root@DietPi:~# lsblk -o name,label,size,ro,type,mountpoint,partuuid,uuid NAME LABEL SIZE RO TYPE MOUNTPOINT PARTUUID UUID mmcblk0 119,1G 0 disk ├─mmcblk0p1 boot 256M 0 part /boot 2fed7fee-01 592B-C92C └─mmcblk0p2 rootfs 118,9G 0 part / 2fed7fee-02 706944a6-7d0f-4a45-9f8c-7fb07375e9f7 ``` EDIT: Googling the error messages leads me to believe that I’m not the only one with this sort of problem: > > > \*\*Describe the bug\*\* > After boot-up, an when activating a service that uses USB …interface (Network UPS tools, as an example) xHCI interface crashs and the USB devices get disconnected. Recovery only possible after system reboot. > > List of USB devices when the system boots up: > \`\`\` > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 003: ID 0463:ffff MGE UPS Systems UPS > Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > \`\`\` > > After enabling a: > \`\`\` > Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > \`\`\` > > > \*\*To reproduce\*\* > After system boot, start Network UPS tools (UPS connected through USB, having a poll frequency of 30 seconds), and the xHCI interface will crash shortly after, leading to all USB devices being disconnected. > > \*\*System\*\* > > Details: > \`Raspberry Pi 4 Model B Rev 1.1\` > > \`\`\` > \# cat /etc/os-release | head -4 > NAME=HassOS > VERSION="3.8 (RaspberryPi 4 64bit)" > ID=hassos > VERSION\_ID=3.8 > \`\`\` > > \`\`\` > \# uname -a > Linux hassio 4.19.93-v8 #1 SMP PREEMPT Sun Jan 12 18:33:10 UTC 2020 aarch64 Hassio/OS > \`\`\` > > \`\`\` > \# cat /proc/cpuinfo | tail -3 > Revision : c03111 > Serial : 1000000013df512e > Model : Raspberry Pi 4 Model B Rev 1.1 > \# > \`\`\` > > \`\`\` > \# df > Filesystem 1K-blocks Used Available Use% Mounted on > /dev/root 92032 92032 0 100% / > devtmpfs 1915496 0 1915496 0% /dev > tmpfs 1948808 0 1948808 0% /dev/shm > tmpfs 1948808 708 1948100 0% /run > tmpfs 1948808 0 1948808 0% /sys/fs/cgroup > tmpfs 1948808 708 1948100 0% /etc/machine-id > /dev/mmcblk0p7 91099 18656 65562 22% /mnt/overlay > /dev/mmcblk0p7 91099 18656 65562 22% /root/.docker > /dev/mmcblk0p7 91099 18656 65562 22% /etc/modprobe.d > /dev/mmcblk0p7 91099 18656 65562 22% /etc/modules-load.d > /dev/mmcblk0p7 91099 18656 65562 22% /etc/docker > /dev/mmcblk0p7 91099 18656 65562 22% /etc/dropbear > /dev/mmcblk0p7 91099 18656 65562 22% /etc/udev/rules.d > /dev/mmcblk0p7 91099 18656 65562 22% /root/.ssh > /dev/mmcblk0p1 32686 3650 29036 11% /mnt/boot > /dev/mmcblk0p7 91099 18656 65562 22% /etc/hostname > /dev/mmcblk0p7 91099 18656 65562 22% /etc/systemd/timesyncd.conf > /dev/mmcblk0p7 91099 18656 65562 22% /etc/NetworkManager/system-connections > /dev/mmcblk0p7 91099 18656 65562 22% /etc/hosts > /dev/mmcblk0p8 122172044 6834280 109113732 6% /mnt/data > /dev/zram2 15856 40 14676 0% /tmp > /dev/zram1 31728 128 29312 0% /var > /dev/mmcblk0p7 91099 18656 65562 22% /var/lib/bluetooth > /dev/mmcblk0p8 122172044 6834280 109113732 6% /var/lib/docker > /dev/mmcblk0p7 91099 18656 65562 22% /var/log/journal > /dev/mmcblk0p7 91099 18656 65562 22% /var/lib/systemd > /dev/mmcblk0p7 91099 18656 65562 22% /var/lib/NetworkManager > overlay 122172044 6834280 109113732 6% /mnt/data/docker/overlay2/c79789ef74f2520ce9bf8308f4f0a0a0c2e2d1453a2836027ab47f3c629d6263/merged > overlay 122172044 6834280 109113732 6% /var/lib/docker/overlay2/c79789ef74f2520ce9bf8308f4f0a0a0c2e2d1453a2836027ab47f3c629d6263/merged > shm 65536 0 65536 0% /mnt/data/docker/containers/4383e4a9b4bfd33f30377b389a5dd8e96f92522bfb5f5e75b5268393aca9af5f/mounts/shm > shm 65536 0 65536 0% /var/lib/docker/containers/4383e4a9b4bfd33f30377b389a5dd8e96f92522bfb5f5e75b5268393aca9af5f/mounts/shm > overlay 122172044 6834280 109113732 6% /mnt/data/docker/overlay2/22cdad6842ade8567501c09ce194d03f072af3910c18cb54da5175d19b0e3aa6/merged > overlay 122172044 6834280 109113732 6% /var/lib/docker/overlay2/22cdad6842ade8567501c09ce194d03f072af3910c18cb54da5175d19b0e3aa6/merged > shm 65536 0 65536 0% /mnt/data/docker/containers/d383f5286c098e038869aa411fbc087895e9852c34db2276b293d5493076e82f/mounts/shm > shm 65536 0 65536 0% /var/lib/docker/containers/d383f5286c098e038869aa411fbc087895e9852c34db2276b293d5493076e82f/mounts/shm > overlay 122172044 6834280 109113732 6% /mnt/data/docker/overlay2/8a1741030a19b420c34768b69144ab241b11b00ec67083b86228cee3844dd40a/merged > overlay 122172044 6834280 109113732 6% /var/lib/docker/overlay2/8a1741030a19b420c34768b69144ab241b11b00ec67083b86228cee3844dd40a/merged > overlay 122172044 6834280 109113732 6% /mnt/data/docker/overlay2/69458a8f8866e9605cd4a15109eb3d1b2a81e7b2b76c81b8f7a1d1f3f7241ec1/merged > overlay 122172044 6834280 109113732 6% /var/lib/docker/overlay2/69458a8f8866e9605cd4a15109eb3d1b2a81e7b2b76c81b8f7a1d1f3f7241ec1/merged > shm 65536 64 65472 0% /mnt/data/docker/containers/b9ddddacc42db28bed967a218c67d490d3b89e3bf3ac4bf980d0f027af739f41/mounts/shm > shm 65536 64 65472 0% /var/lib/docker/containers/b9ddddacc42db28bed967a218c67d490d3b89e3bf3ac4bf980d0f027af739f41/mounts/shm > overlay 122172044 6834280 109113732 6% /mnt/data/docker/overlay2/563028cbdc5e65467e4299d65e42050ca216a6252d1e144e8491723a1434ad1e/merged > overlay 122172044 6834280 109113732 6% /var/lib/docker/overlay2/563028cbdc5e65467e4299d65e42050ca216a6252d1e144e8491723a1434ad1e/merged > overlay 122172044 6834280 109113732 6% /mnt/data/docker/overlay2/a00df7501c5d7ef5be8316129829c2b57b7fef415914170006b3172bb43ebaaa/merged > overlay 122172044 6834280 109113732 6% /var/lib/docker/overlay2/a00df7501c5d7ef5be8316129829c2b57b7fef415914170006b3172bb43ebaaa/merged > overlay 122172044 6834280 109113732 6% /mnt/data/docker/overlay2/a72a5bc9321264232980140c9bc6686e89db9c4a83a1da17c8755811f160de6a/merged > overlay 122172044 6834280 109113732 6% /var/lib/docker/overlay2/a72a5bc9321264232980140c9bc6686e89db9c4a83a1da17c8755811f160de6a/merged > overlay 122172044 6834280 109113732 6% /mnt/data/docker/overlay2/7624b7f0f58cc8d32d9d8702d26ae71c27fcd0026f27a6623b15c0ec13fd499a/merged > overlay 122172044 6834280 109113732 6% /var/lib/docker/overlay2/7624b7f0f58cc8d32d9d8702d26ae71c27fcd0026f27a6623b15c0ec13fd499a/merged > shm 65536 48 65488 0% /mnt/data/docker/containers/376a3e6a98ad20b772ae7f38b2051750d0d38d2f876be82d1cc17a81ae801a05/mounts/shm > shm 65536 48 65488 0% /var/lib/docker/containers/376a3e6a98ad20b772ae7f38b2051750d0d38d2f876be82d1cc17a81ae801a05/mounts/shm > shm 65536 60 65476 0% /mnt/data/docker/containers/8043d49fda6b8c96b4cfd0fd77a8499b6f70e5a4ad7a66fc37eb417c1ac6a936/mounts/shm > shm 65536 60 65476 0% /var/lib/docker/containers/8043d49fda6b8c96b4cfd0fd77a8499b6f70e5a4ad7a66fc37eb417c1ac6a936/mounts/shm > shm 65536 68 65468 0% /mnt/data/docker/containers/ef4df3ae0e79c33285baec87cd55c0b9d28d150ffda2a19e799979073cd1297a/mounts/shm > shm 65536 68 65468 0% /var/lib/docker/containers/ef4df3ae0e79c33285baec87cd55c0b9d28d150ffda2a19e799979073cd1297a/mounts/shm > shm 65536 68 65468 0% /mnt/data/docker/containers/f73b6c980b13d97d27fb314c6224f8ed0ef66be8e8039b69436273dc328925f5/mounts/shm > shm 65536 68 65468 0% /var/lib/docker/containers/f73b6c980b13d97d27fb314c6224f8ed0ef66be8e8039b69436273dc328925f5/mounts/shm > shm 65536 56 65480 0% /mnt/data/docker/containers/6cbb56501e93036eebc86c0c4bfc38a133d2a62ab458290f5005c592a572e7e3/mounts/shm > shm 65536 56 65480 0% /var/lib/docker/containers/6cbb56501e93036eebc86c0c4bfc38a133d2a62ab458290f5005c592a572e7e3/mounts/shm > overlay 122172044 6834280 109113732 6% /mnt/data/docker/overlay2/9737f2fb6b35435b15a046da2583412dd66e3559ab0fde67c9fd7c2e67336aa4/merged > overlay 122172044 6834280 109113732 6% /var/lib/docker/overlay2/9737f2fb6b35435b15a046da2583412dd66e3559ab0fde67c9fd7c2e67336aa4/merged > shm 65536 0 65536 0% /mnt/data/docker/containers/05216e59fa3a97c660472ae072c417cab1743086a3bb61f40ff167f2caaa03ba/mounts/shm > shm 65536 0 65536 0% /var/lib/docker/containers/05216e59fa3a97c660472ae072c417cab1743086a3bb61f40ff167f2caaa03ba/mounts/shm > overlay 122172044 6834280 109113732 6% /mnt/data/docker/overlay2/ce9f300e071672f49be4e085525ee1e19e381ff4e6bb869e12f5cad245018136/merged > overlay 122172044 6834280 109113732 6% /var/lib/docker/overlay2/ce9f300e071672f49be4e085525ee1e19e381ff4e6bb869e12f5cad245018136/merged > shm 65536 68 65468 0% /mnt/data/docker/containers/f3c374354b066023eef0662df5fee6b5112d69eba4e2c18daff4223e387d00fa/mounts/shm > shm 65536 68 65468 0% /var/lib/docker/containers/f3c374354b066023eef0662df5fee6b5112d69eba4e2c18daff4223e387d00fa/mounts/shm > \# cat /proc/swaps > Filename Type Size Used Priority > /dev/zram0 partition 974400 0 -2 > \# > \`\`\` > > \* Which model of Raspberry Pi? Raspberry Pi 4B 4GB > \* Which OS and version (\`cat /etc/rpi-issue\`)? HassOS 3.8 > \* Which firmware version (\`vcgencmd version\`)? > \* Which kernel version (\`uname -a\`)? Linux hassio 4.19.93-v8 #1 SMP PREEMPT Sun Jan 12 18:33:10 UTC 2020 aarch64 Hassio/OS > > \*\*Logs\*\* > dmesg output: > \`\`\` > \[0.197545\] usbcore: registered new interface driver usbfs > \[0.197606\] usbcore: registered new interface driver hub > \[0.197718\] usbcore: registered new device driver usb > \[0.487955\] usbcore: registered new interface driver r8152 > \[0.488025\] usbcore: registered new interface driver lan78xx > \[0.488474\] xhci\_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1 > \[0.495448\] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 4.19 > \[0.495481\] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 > \[0.495507\] usb usb1: Product: xHCI Host Controller > \[0.495528\] usb usb1: Manufacturer: Linux 4.19.88-v8 xhci-hcd > \[0.495549\] usb usb1: SerialNumber: 0000:01:00.0 > \[0.496073\] hub 1-0:1.0: USB hub found > \[0.496671\] xhci\_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2 > \[0.496706\] xhci\_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed > \[0.497145\] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 4.19 > \[0.497175\] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 > \[0.497200\] usb usb2: Product: xHCI Host Controller > \[0.497220\] usb usb2: Manufacturer: Linux 4.19.88-v8 xhci-hcd > \[0.497242\] usb usb2: SerialNumber: 0000:01:00.0 > \[0.497711\] hub 2-0:1.0: USB hub found > \[0.499380\] usbcore: registered new interface driver uas > \[0.499478\] usbcore: registered new interface driver usb-storage > \[0.499601\] usbcore: registered new interface driver usbserial\_generic > \[0.499647\] usbserial: USB Serial support registered for generic > \[0.507353\] usbcore: registered new interface driver usbhid > \[0.507361\] usbhid: USB HID core driver > \[0.830300\] usb 1-1: new high-speed USB device number 2 using xhci\_hcd > \[0.980982\] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.20 > \[0.981020\] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 > \[0.981041\] usb 1-1: Product: USB2.0 Hub > \[0.982796\] hub 1-1:1.0: USB hub found > \[1.278306\] usb 1-1.3: new full-speed USB device number 3 using xhci\_hcd > \[1.615672\] usbcore: registered new interface driver brcmfmac > \[1.999992\] usb 1-1.3: New USB device found, idVendor=0463, idProduct=ffff, bcdDevice= 0.01 > \[2.000016\] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=0 > \[2.000027\] usb 1-1.3: Product: 5E > \[2.000036\] usb 1-1.3: Manufacturer: EATON > \[3.967565\] hid-generic 0003:0463:FFFF.0001: hiddev96,hidraw0: USB HID v1.10 Device \[EATON 5E\] on usb-0000:01:00.0-1.3/input0 > \[172.256228\] xhci\_hcd 0000:01:00.0: xHCI host not responding to stop endpoint command. > \[172.272306\] xhci\_hcd 0000:01:00.0: Host halt failed, -110 > \[172.272321\] xhci\_hcd 0000:01:00.0: xHCI host controller not responding, assume dead > \[172.272369\] xhci\_hcd 0000:01:00.0: HC died; cleaning up \[172.272442\] usb 1-1: USB disconnect, device number 2 > \[172.272467\] usb 1-1.3: USB disconnect, device number 3 > \`\`\` > > \*\*Additional context\*\* > This bug report was opened here because HassOS3.8 rus default raspbian Kernel. > This issue was initially reported here: > https://github.com/home-assistant/hassos/issues/526 > > USB cable was replaced to ensure that it was not faulty. > > If more logs are needed, please let me know [https://www.reddit.com/r/raspberry\_pi/comments/f0xkyw/usb\_complete\_failure\_xhci\_host\_controller\_not/](https://www.reddit.com/r/raspberry_pi/comments/f0xkyw/usb_complete_failure_xhci_host_controller_not/) [https://www.raspberrypi.org/forums/viewtopic.php?t=262649](https://www.raspberrypi.org/forums/viewtopic.php?t=262649) [https://www.raspberrypi.org/forums/viewtopic.php?t=263332](https://www.raspberrypi.org/forums/viewtopic.php?t=263332) [https://archlinuxarm.org/forum/viewtopic.php?f=65&t=14172](https://archlinuxarm.org/forum/viewtopic.php?f=65&t=14172) ---
### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar) #### Post date: [10 June 2020 23:22 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/6 "2020-06-10T23:22:03Z")
well you have I/O errors on this drive. Usually this is pointing to issues with the drive itself or some bad cable or some issues on thy RPi. If possible try to run some self test on the SSD, use another USB slot, change cable and check if you can use own power in the SSD. ---
### Author: ![Pillendreher](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/p/a698b9/32.png) [@Pillendreher](https://dietpi.com/forum/u/Pillendreher) #### Post date: [11 June 2020 08:31 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/7 "2020-06-11T08:31:36Z")
> [@](#): > > well you have I/O errors on this drive. Usually this is pointing to issues with the drive itself or some bad cable or some issues on thy RPi. If possible try to run some self test on the SSD, use another USB slot, change cable and check if you can use own power in the SSD. Well I’m no expert by any means, but I reckon the input/output errors are due to the connection to the drive being lost, no? Regarding the drive: SMART tells me there are no issues (no critical warnings, no media and data integrity errors) ```plaintext root@DietPi:~# smartctl -a /dev/sda -d sntjmicron smartctl 7.1 2019-12-30 r5022 [armv7l-linux-4.19.118-v7l+] (local build) Copyright (C) 2002-19, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Number: SAMSUNG MZVLW256HEHP-000L7 Serial Number: S35ENA1K272709 Firmware Version: 5L7QCXB7 PCI Vendor/Subsystem ID: 0x144d IEEE OUI Identifier: 0x002538 Total NVM Capacity: 256.060.514.304 [256 GB] Unallocated NVM Capacity: 0 Controller ID: 2 Number of Namespaces: 1 Namespace 1 Size/Capacity: 256.060.514.304 [256 GB] Namespace 1 Utilization: 244.637.016.064 [244 GB] Namespace 1 Formatted LBA Size: 512 Namespace 1 IEEE EUI-64: 002538 b28102e969 Local Time is: Thu Jun 11 10:22:42 2020 CEST Firmware Updates (0x16): 3 Slots, no Reset required Optional Admin Commands (0x0017): Security Format Frmw_DL Self_Test Optional NVM Commands (0x001f): Comp Wr_Unc DS_Mngmt Wr_Zero Sav/Sel_Feat Warning Comp. Temp. Threshold: 69 Celsius Critical Comp. Temp. Threshold: 72 Celsius Supported Power States St Op Max Active Idle RL RT WL WT Ent_Lat Ex_Lat 0 + 7.60W - - 0 0 0 0 0 0 1 + 6.00W - - 1 1 1 1 0 0 2 + 5.10W - - 2 2 2 2 0 0 3 - 0.0400W - - 3 3 3 3 210 1500 4 - 0.0050W - - 4 4 4 4 2200 6000 Supported LBA Sizes (NSID 0x1) Id Fmt Data Metadt Rel_Perf 0 + 512 0 0 === START OF SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED SMART/Health Information (NVMe Log 0x02) Critical Warning: 0x00 Temperature: 32 Celsius Available Spare: 100% Available Spare Threshold: 10% Percentage Used: 5% Data Units Read: 38.939.450 [19,9 TB] Data Units Written: 29.900.926 [15,3 TB] Host Read Commands: 307.986.706 Host Write Commands: 229.812.741 Controller Busy Time: 1.028 Power Cycles: 3.049 Power On Hours: 886 Unsafe Shutdowns: 141 Media and Data Integrity Errors: 0 Error Information Log Entries: 1.611 Warning Comp. Temperature Time: 0 Critical Comp. Temperature Time: 0 Temperature Sensor 1: 32 Celsius Temperature Sensor 2: 36 Celsius Error Information (NVMe Log 0x01, max 64 entries) Num ErrCount SQId CmdId Status PELoc LBA NSID VS 0 1611 0 0x010e 0x4202 0x028 0 0 - 1 1610 0 0x000d 0x4202 0x028 0 0 - 2 1609 0 0x0f0c 0x4202 0x028 0 0 - 3 1608 0 0x0e0b 0x4202 0x028 0 0 - 4 1607 0 0x0d0a 0x4202 0x028 0 0 - 5 1606 0 0x0c09 0x4202 0x028 0 0 - 6 1605 0 0x0b08 0x4202 0x028 0 0 - 7 1604 0 0x0a07 0x4202 0x028 0 0 - 8 1603 0 0x0906 0x4202 0x028 0 0 - 9 1602 0 0x0805 0x4202 0x028 0 0 - 10 1601 0 0x0704 0x4202 0x028 0 0 - 11 1600 0 0x0603 0x4202 0x028 0 0 - 12 1599 0 0x0502 0x4202 0x028 0 0 - 13 1598 0 0x0401 0x4202 0x028 0 0 - 14 1597 0 0x030f 0x4202 0x028 0 0 - 15 1596 0 0x020e 0x4202 0x028 0 0 - ... (48 entries not shown) ``` and I somewhat doubt that the cable is faulty simply because everything is running smoothly except when I remote access the drive and put some stress on it. Of course I can’t be sure, but I think it’s reasonable to assume that a faulty drive/cable would impact everything and not just during certain scenarios. I’ll try to get a more in-depth log for a crash, maybe that will tell us sómething. EDIT: By “everything else is running smoothly” I mean that I have not encountered a single issue running downloads with JDownloader or SABNZBD for example. ---
### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar) #### Post date: [11 June 2020 10:04 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/8 "2020-06-11T10:04:47Z")
I just can share the experience on our board. Most of the issues with external drives are connected to insufficient power. It might be that there as issues on the kernel but this is something out of our scope as DietPi is using Raspberry OS for PRi devices. This include the kernel as well. BTW there is quite a long post on HDD issues already. Might not fit 100% but probably good to read [https://dietpi.com/forum/t/external-hdd-issues/3829/1](https://dietpi.com/forum/t/external-hdd-issues/3829/1) ---
### Author: ![baz123](https://dietpi.com/forum/user_avatar/dietpi.com/baz123/32/2653_2.png) [@baz123](https://dietpi.com/forum/u/baz123) #### Post date: [12 June 2020 19:35 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/9 "2020-06-12T19:35:41Z")
I had loads of issues with an SSD and DietPi. I moved back to Raspbian and have had no real issues. Personally I think it must be kernel related. A small SSD draws an insignificant amount of power so power, especially with an official supply is not the issue. If it was an HDD I’d agree with you. There is quite a long thread on it. Also note this is a Pi4; I ran a Pi2B+ with a PiDrive and DietPi Stretch for many years with no issues. ---
### 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 June 2020 19:37 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/10 "2020-06-12T19:37:51Z")
DietPi has no own kernel. It’s using the default kernel provided by the base image. In case of Raspberry Pi it’s using the kernel provided with Raspbian OS. ---
### Author: ![baz123](https://dietpi.com/forum/user_avatar/dietpi.com/baz123/32/2653_2.png) [@baz123](https://dietpi.com/forum/u/baz123) #### Post date: [13 June 2020 20:38 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/11 "2020-06-13T20:38:01Z")
All I can say is that with the same HW, DietPi install regularly disconnects from the SSD, Raspbian doesn’t. ---
### Author: ![Pillendreher](https://dietpi.com/forum/letter_avatar_proxy/v4/letter/p/a698b9/32.png) [@Pillendreher](https://dietpi.com/forum/u/Pillendreher) #### Post date: [23 June 2020 12:14 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/12 "2020-06-23T12:14:10Z")
Just to provide an update on the whole situation: Per [this comment](https://github.com/raspberrypi/linux/issues/3404#issuecomment-642512000) and based on [this thread at the Raspberry Pi Forums](https://www.raspberrypi.org/forums/viewtopic.php?p=1501426), I switched from UAS to usb-storage and have not encountered a single issue since! ---
### Author: ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar) #### Post date: [23 June 2020 13:18 UTC](https://dietpi.com/forum/t/ssd-goes-missing-possible-connection-with-samba/4192/13 "2020-06-23T13:18:18Z")
thx for sharing your solution, much appreciated