+- Moode Forum (https://moodeaudio.org/forum)
+-- Forum: moOde audio player (https://moodeaudio.org/forum/forumdisplay.php?fid=3)
+--- Forum: Support (https://moodeaudio.org/forum/forumdisplay.php?fid=7)
+--- Thread: Large(r) SSDs not supported (/showthread.php?tid=3780)
Large(r) SSDs not supported - Gekel - 05-06-2021
Hi,
tried one whole day to move the Moode installation from SD card to an 870 QVO SSD with 2TB, but no matter what I tried, the system locked up. I could not even use the drive as pure data drive on my Raspberry Pi 4 (B, 2GB). Copying files would fail and I had to format the drive to ext4 while having it attached to a different computer.
I monitored the syslog and could find multiple instances of the driver being reset and the ssd drive becoming unavailable. Exchanging the PSU of the pi didn't help (I am using a 5V 3A PSU), switching from USB 3 to USB 2 also didn't help and after some research with Google I even plugged the drive into an external hdd case with separate power supply (24W, should be enough...) with no changes. the drive simply was unusable.
End of story: I replaced the 2TB SSD with an 512GB drive which was laying around, and since then the system runs flawless. the 2TB drive will end in a NanoPi and I'll mount it over the network to add some more storage space to moode.
Anyone else experienced this?
RE: Large(r) SSDs not supported - Tim Curtis - 05-06-2021
You might try posting about the 2TB drive on the Raspberry Pi Forums to see if anyone there has info on the issue
https://www.raspberrypi.org/forums/
RE: Large(r) SSDs not supported - Gekel - 05-06-2021
(05-06-2021, 10:58 AM)Tim Curtis Wrote: You might try posting about the 2TB drive on the Raspberry Pi Forums to see if anyone there has info on the issue
https://www.raspberrypi.org/forums/
I'll have a closer look at this when I have time. It's ok now and the network streamer is already running with a 450GB partition reserved for audio files, and before I run out of space the Nano pi Neo3 should be here and I can build a dedicated file server for audio files.
Until then I am busy for sure. My old amp needs to be checked and handed over to my sister, the loud speaker need to be reassembled and the ne new amp/cd player/ network streamer combo moved to the final place.
One unrelated side note: I might just have ignored some kind of documentation, but it would be an idea to place some kind of pop up window on the webserver when you run Moode the first time as reminder to change the password on the SSH login.
RE: Large(r) SSDs not supported - yannig - 05-06-2021
(05-06-2021, 09:07 AM)Gekel Wrote: Hi,
tried one whole day to move the Moode installation from SD card to an 870 QVO SSD with 2TB, but no matter what I tried, the system locked up. I could not even use the drive as pure data drive on my Raspberry Pi 4 (B, 2GB). Copying files would fail and I had to format the drive to ext4 while having it attached to a different computer.
I monitored the syslog and could find multiple instances of the driver being reset and the ssd drive becoming unavailable. Exchanging the PSU of the pi didn't help (I am using a 5V 3A PSU), switching from USB 3 to USB 2 also didn't help and after some research with Google I even plugged the drive into an external hdd case with separate power supply (24W, should be enough...) with no changes. the drive simply was unusable.
End of story: I replaced the 2TB SSD with an 512GB drive which was laying around, and since then the system runs flawless. the 2TB drive will end in a NanoPi and I'll mount it over the network to add some more storage space to moode.
Anyone else experienced this?
I tried 3TB (non SSD) on a 3B+, and it worked...
RE: Large(r) SSDs not supported - Gekel - 05-07-2021
Interesting.
What I did yesterday:
- started the pi with Moode (on the 512GB SSD), attached the 2TB to the second port - immediate system freez, no connection via SSH possible, had to hard reset it
- attached the 2TB drive in the original case using the original cable to my PC (running Ubuntu): drive detected and mounted. No error messages in syslog, even while/after running a quick test where I copied 50GB data to the 2TB drive.
So I can rule out a defect in the drive, case or USB cable and the required power needed to "spin up" the drive. Last straw: the kernel is not compatible with this specific drive.
Today a fresh sd card should arrive. I'll install Moode on it, check if the error with the drive goes away and if not try a kernel update. Hopefully this doesn't break too much....
RE: Large(r) SSDs not supported - Gekel - 05-07-2021
It is the kernel. I launched a pi OS with kernel 5.10.17 and the ssd is working without issues.
So now it's time to see if I break Moode when I change the kernel
RE: Large(r) SSDs not supported - Gekel - 05-07-2021
So here we go again.
Fresh SD, just created, booted, hooked up the SSD to it...
May 7 08:44:37 moode kernel: [ 499.057465] sd 0:0:0:0: [sda] tag#2 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD
May 7 08:44:37 moode kernel: [ 499.057481] sd 0:0:0:0: [sda] tag#2 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
May 7 08:44:37 moode kernel: [ 499.057507] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
May 7 08:44:37 moode kernel: [ 499.057519] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 00 00 02 10 00 01 10 00
May 7 08:44:37 moode kernel: [ 499.057744] sd 0:0:0:0: [sda] tag#0 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN
May 7 08:44:37 moode kernel: [ 499.057757] sd 0:0:0:0: [sda] tag#0 CDB: opcode=0x28 28 00 00 00 02 08 00 00 08 00
May 7 08:44:37 moode kernel: [ 499.097492] scsi host0: uas_eh_device_reset_handler start
May 7 08:44:37 moode kernel: [ 499.258378] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
May 7 08:44:37 moode kernel: [ 499.293015] scsi host0: uas_eh_device_reset_handler success
May 7 08:46:38 moode systemd[1]: Started Samba NMB Daemon.
May 7 08:47:12 moode kernel: [ 654.579980] sd 0:0:0:0: [sda] tag#27 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD
May 7 08:47:12 moode kernel: [ 654.579996] sd 0:0:0:0: [sda] tag#27 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
May 7 08:47:12 moode kernel: [ 654.580022] sd 0:0:0:0: [sda] tag#26 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
May 7 08:47:12 moode kernel: [ 654.580034] sd 0:0:0:0: [sda] tag#26 CDB: opcode=0x28 28 00 00 00 0a 08 00 01 f8 00
May 7 08:47:12 moode kernel: [ 654.580329] sd 0:0:0:0: [sda] tag#25 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
May 7 08:47:12 moode kernel: [ 654.580341] sd 0:0:0:0: [sda] tag#25 CDB: opcode=0x28 28 00 e8 e0 88 00 00 00 08 00
May 7 08:47:12 moode kernel: [ 654.580612] sd 0:0:0:0: [sda] tag#24 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD IN
May 7 08:47:12 moode kernel: [ 654.580624] sd 0:0:0:0: [sda] tag#24 CDB: opcode=0x28 28 00 00 08 08 88 00 00 78 00
May 7 08:47:12 moode kernel: [ 654.580752] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN
May 7 08:47:12 moode kernel: [ 654.580764] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 00 08 09 08 00 00 f8 00
May 7 08:47:12 moode kernel: [ 654.620006] scsi host0: uas_eh_device_reset_handler start
May 7 08:47:13 moode kernel: [ 654.771001] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
May 7 08:47:13 moode kernel: [ 654.806116] scsi host0: uas_eh_device_reset_handler success
May 7 08:47:43 moode kernel: [ 685.300388] sd 0:0:0:0: [sda] tag#28 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN
May 7 08:47:43 moode kernel: [ 685.300404] sd 0:0:0:0: [sda] tag#28 CDB: opcode=0x28 28 00 e8 e0 85 28 00 00 a8 00
May 7 08:47:43 moode kernel: [ 685.300579] sd 0:0:0:0: [sda] tag#27 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN
May 7 08:47:43 moode kernel: [ 685.300592] sd 0:0:0:0: [sda] tag#27 CDB: opcode=0x28 28 00 e8 e0 84 e8 00 00 10 00
May 7 08:47:43 moode kernel: [ 685.300893] sd 0:0:0:0: [sda] tag#26 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
May 7 08:47:43 moode kernel: [ 685.300904] sd 0:0:0:0: [sda] tag#26 CDB: opcode=0x28 28 00 e8 e0 84 d8 00 00 08 00
May 7 08:47:43 moode kernel: [ 685.301010] sd 0:0:0:0: [sda] tag#1 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN
May 7 08:47:43 moode kernel: [ 685.301022] sd 0:0:0:0: [sda] tag#1 CDB: opcode=0x28 28 00 e8 e0 85 d8 00 00 28 00
May 7 08:47:43 moode kernel: [ 685.330376] sd 0:0:0:0: [sda] tag#24 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD
May 7 08:47:43 moode kernel: [ 685.330392] sd 0:0:0:0: [sda] tag#24 CDB: opcode=0x35 35 00 00 00 00 00 00 00 00 00
May 7 08:47:43 moode kernel: [ 685.380381] scsi host0: uas_eh_device_reset_handler start
May 7 08:47:43 moode kernel: [ 685.531382] usb 2-2: reset SuperSpeed Gen 1 USB device number 2 using xhci_hcd
May 7 08:47:43 moode kernel: [ 685.566390] scsi host0: uas_eh_device_reset_handler success
Then I ran a system update/upgrade, rebooted, and with kernel 5.10.17
May 7 09:01:26 moode kernel: [ 50.949212] sd 0:0:0:0: [sda] Attached SCSI disk
May 7 09:01:57 moode kernel: [ 81.773823] sd 0:0:0:0: [sda] tag#27 uas_eh_abort_handler 0 uas-tag 7 inflight: CMD IN
May 7 09:01:57 moode kernel: [ 81.773840] sd 0:0:0:0: [sda] tag#27 CDB: opcode=0x28 28 00 00 08 07 88 00 00 68 00
May 7 09:01:57 moode kernel: [ 81.774046] sd 0:0:0:0: [sda] tag#26 uas_eh_abort_handler 0 uas-tag 6 inflight: CMD IN
May 7 09:01:57 moode kernel: [ 81.774060] sd 0:0:0:0: [sda] tag#26 CDB: opcode=0x28 28 00 00 08 07 00 00 00 80 00
May 7 09:01:57 moode kernel: [ 81.774356] sd 0:0:0:0: [sda] tag#25 uas_eh_abort_handler 0 uas-tag 5 inflight: CMD IN
May 7 09:01:57 moode kernel: [ 81.774370] sd 0:0:0:0: [sda] tag#25 CDB: opcode=0x28 28 00 00 08 06 00 00 00 f8 00
May 7 09:01:57 moode kernel: [ 81.774698] sd 0:0:0:0: [sda] tag#24 uas_eh_abort_handler 0 uas-tag 4 inflight: CMD IN
May 7 09:01:57 moode kernel: [ 81.774711] sd 0:0:0:0: [sda] tag#24 CDB: opcode=0x28 28 00 04 08 0a 08 00 01 f8 00
May 7 09:01:57 moode kernel: [ 81.775080] sd 0:0:0:0: [sda] tag#19 uas_eh_abort_handler 0 uas-tag 1 inflight: CMD IN
May 7 09:01:57 moode kernel: [ 81.775092] sd 0:0:0:0: [sda] tag#19 CDB: opcode=0x28 28 00 04 08 06 00 00 00 f8 00
May 7 09:01:57 moode kernel: [ 81.775384] sd 0:0:0:0: [sda] tag#17 uas_eh_abort_handler 0 uas-tag 3 inflight: CMD IN
May 7 09:01:57 moode kernel: [ 81.775396] sd 0:0:0:0: [sda] tag#17 CDB: opcode=0x28 28 00 04 08 07 88 00 00 68 00
May 7 09:01:57 moode kernel: [ 81.775684] sd 0:0:0:0: [sda] tag#16 uas_eh_abort_handler 0 uas-tag 2 inflight: CMD IN
May 7 09:01:57 moode kernel: [ 81.775697] sd 0:0:0:0: [sda] tag#16 CDB: opcode=0x28 28 00 04 08 07 00 00 00 80 00
Here might be the reason and solution: https://www.raspberrypi.org/forums/viewtopic.php?t=245931 At least after identifying the vendor and drive id and adding the quirks-command to cmdline.txt like described on the linked page, the system is now working.