Post Reply 
Minimserver crashes when media drive connected
28-09-2026, 15:52
Post: #1
Minimserver crashes when media drive connected
Hi,

i have minimserver freshly installed on a raspberry pi 4, 64bit Pi OS. The music is accessed from a SSD usb hard drive formatted to exFAT. However, when i connect the drive, the pi crashes. Everything runs fine with the drive disconnected.
I have reinstalled everything and formatted the drive with no joy. Can someone please provide some advice?!!!
Find all posts by this user
Quote this message in a reply
28-09-2026, 16:17
Post: #2
RE: Minimserver crashes when media drive connected
This probably isn't caused by MinimServer. What happens if you exit MinimServer and then connect the drive?
Find all posts by this user
Quote this message in a reply
28-09-2026, 20:04
Post: #3
RE: Minimserver crashes when media drive connected
(28-09-2026 16:17)simoncn Wrote:  This probably isn't caused by MinimServer. What happens if you exit MinimServer and then connect the drive?

It connects fine. The pi reads the drive. I can open and browse the files with no problem. As soon as MinimServer reads it, it crashes the pi.
Find all posts by this user
Quote this message in a reply
28-09-2026, 20:19
Post: #4
RE: Minimserver crashes when media drive connected
Are there any error messages in the minimserver.log file after the crash? The information in this file is still available after a restart unless you are automatically starting MinimServer when the system starts.

Also, some errors are written by MinimServer to a crash log file in the minimserver/data directory. This file has a name starting with "minimserver-crash." Do you see any such files?
Find all posts by this user
Quote this message in a reply
28-09-2026, 20:38 (This post was last modified: 28-09-2026 20:38 by Pdog.)
Post: #5
RE: Minimserver crashes when media drive connected
I will have a look and come back to you ?
Find all posts by this user
Quote this message in a reply
Yesterday, 18:51
Post: #6
RE: Minimserver crashes when media drive connected
(28-09-2026 20:19)simoncn Wrote:  Are there any error messages in the minimserver.log file after the crash? The information in this file is still available after a restart unless you are automatically starting MinimServer when the system starts.

Also, some errors are written by MinimServer to a crash log file in the minimserver/data directory. This file has a name starting with "minimserver-crash." Do you see any such files?

This is the crash file data,


MinimServer crash dump, produced at 20260927-175751.633

HTTPConnection: exception while processing HTTP request: java.lang.StringIndexOutOfBoundsException: Range [0, -1) out of bounds for length 19

java.lang.StringIndexOutOfBoundsException: Range [0, -1) out of bounds for length 19
at java.base/jdk.internal.util.Preconditions$1.apply(Preconditions.java:55)
at java.base/jdk.internal.util.Preconditions$1.apply(Preconditions.java:52)
at java.base/jdk.internal.util.Preconditions$4.apply(Preconditions.java:213)
at java.base/jdk.internal.util.Preconditions$4.apply(Preconditions.java:210)
at java.base/jdk.internal.util.Preconditions.outOfBounds(Preconditions.java:98)
at java.base/jdk.internal.util.Preconditions.outOfBoundsCheckFromToIndex(Preconditions.java:1​12)
at java.base/jdk.internal.util.Preconditions.checkFromToIndex(Preconditions.java:349)
at java.base/java.lang.String.checkBoundsBeginEnd(String.java:4855)
at java.base/java.lang.String.substring(String.java:2823)
at org.jminim.lib.HTTPConnection$ReaderThread.readRequest(HTTPConnection.java:243)
at org.jminim.lib.HTTPConnection$ReaderThread.runReaderThread(HTTPConnection.java:1​63)
at org.jminim.lib.HTTPConnection$ReaderThread.run(HTTPConnection.java:129)

"main" id=1 WAITING
at java.base@21.0.12.1/java.lang.Object.wait0(Native Method)
- waiting on java.lang.Object@7a788f6c
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:366)
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:339)
at org.jminim.core.RuntimeImpl.waitForRequest(RuntimeImpl.java:4479)
at org.jminim.core.RuntimeImpl.run(RuntimeImpl.java:2918)
at org.jminim.core.LauncherImpl.run(LauncherImpl.java:1327)
at org.jminim.core.LauncherImpl.launch(LauncherImpl.java:126)
at java.base@21.0.12.1/java.lang.invoke.LambdaForm$DMH/0x00000060010c2800.invokeStatic(LambdaForm$DMH)
at java.base@21.0.12.1/java.lang.invoke.LambdaForm$MH/0x00000060010c5000.invoke(LambdaForm$MH)
at java.base@21.0.12.1/java.lang.invoke.LambdaForm$MH/0x00000060010c5800.invoke(LambdaForm$MH)
at java.base@21.0.12.1/java.lang.invoke.Invokers$Holder.invokeExact_MT(Invokers$Holder)
at java.base@21.0.12.1/jdk.internal.reflect.DirectMethodHandleAccessor.invokeImpl(DirectMethodHandleAcc​essor.java:157)
at java.base@21.0.12.1/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccesso​r.java:103)
at java.base@21.0.12.1/java.lang.reflect.Method.invoke(Method.java:580)
at org.jminim.mlaunch.MinimLaunch.doLaunch(MinimLaunch.java:525)
at org.jminim.mlaunch.MinimLaunch.launch(MinimLaunch.java:150)
at org.jminim.mlaunch.MinimLaunch.launch(MinimLaunch.java:90)
at java.base@21.0.12.1/java.lang.invoke.LambdaForm$DMH/0x0000006001004000.invokeStatic(LambdaForm$DMH)
at java.base@21.0.12.1/java.lang.invoke.LambdaForm$MH/0x0000006001008000.invoke(LambdaForm$MH)
at java.base@21.0.12.1/java.lang.invoke.Invokers$Holder.invokeExact_MT(Invokers$Holder)
at java.base@21.0.12.1/jdk.internal.reflect.DirectMethodHandleAccessor.invokeImpl(DirectMethodHandleAcc​essor.java:157)
at java.base@21.0.12.1/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccesso​r.java:103)
at java.base@21.0.12.1/java.lang.reflect.Method.invoke(Method.java:580)
at app//org.jminim.launch.Launcher.launch(Launcher.java:88)
at app//com.minimserver.launch.LaunchServer.main(LaunchServer.java:38)

"Reference Handler" id=9 RUNNABLE
at java.base@21.0.12.1/java.lang.ref.Reference.waitForReferencePendingList(Native Method)
at java.base@21.0.12.1/java.lang.ref.Reference.processPendingReferences(Reference.java:246)
at java.base@21.0.12.1/java.lang.ref.Reference$ReferenceHandler.run(Reference.java:208)

"Finalizer" id=10 WAITING
at java.base@21.0.12.1/java.lang.Object.wait0(Native Method)
- waiting on java.lang.ref.NativeReferenceQueue$Lock@27d53b48
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:366)
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:339)
at java.base@21.0.12.1/java.lang.ref.NativeReferenceQueue.await(NativeReferenceQueue.java:48)
at java.base@21.0.12.1/java.lang.ref.ReferenceQueue.remove0(ReferenceQueue.java:158)
at java.base@21.0.12.1/java.lang.ref.NativeReferenceQueue.remove(NativeReferenceQueue.java:89)
at java.base@21.0.12.1/java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:173)

"Signal Dispatcher" id=11 RUNNABLE

"Notification Thread" id=17 RUNNABLE

"Common-Cleaner" id=18 TIMED_WAITING
at java.base@21.0.12.1/jdk.internal.misc.Unsafe.park(Native Method)
- waiting on java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject@49d8b379
at java.base@21.0.12.1/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:269)
at java.base@21.0.12.1/java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(Abst​ractQueuedSynchronizer.java:1886)
at java.base@21.0.12.1/java.lang.ref.ReferenceQueue.await(ReferenceQueue.java:71)
at java.base@21.0.12.1/java.lang.ref.ReferenceQueue.remove0(ReferenceQueue.java:143)
at java.base@21.0.12.1/java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:218)
at java.base@21.0.12.1/jdk.internal.ref.CleanerImpl.run(CleanerImpl.java:140)
at java.base@21.0.12.1/java.lang.Thread.runWith(Thread.java:1596)
at java.base@21.0.12.1/java.lang.Thread.run(Thread.java:1583)
at java.base@21.0.12.1/jdk.internal.misc.InnocuousThread.run(InnocuousThread.java:186)

"Thread-0" id=19 WAITING
at java.base@21.0.12.1/java.lang.Object.wait0(Native Method)
- waiting on org.jminim.core.RuntimeImpl$ActionThread@65f724b0
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:366)
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:339)
at org.jminim.core.RuntimeImpl$ActionThread.run(RuntimeImpl.java:4587)

"Thread-1" id=20 WAITING
at java.base@21.0.12.1/java.lang.Object.wait0(Native Method)
- waiting on org.jminim.core.RuntimeImpl$TimerThread@5b4ad48d
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:366)
at org.jminim.core.RuntimeImpl$TimerThread.run(RuntimeImpl.java:4633)

"Thread-3" id=27 WAITING
at java.base@21.0.12.1/java.lang.Object.wait0(Native Method)
- waiting on org.jminim.lib.OhNetService$ActionThread@55cbabd7
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:366)
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:339)
at org.jminim.lib.OhNetService$ActionThread.run(OhNetService.java:1202)

"Thread-4" id=28 WAITING
at java.base@21.0.12.1/java.lang.Object.wait0(Native Method)
- waiting on org.jminim.lib.OhNetService$TimerThread@5984896c
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:366)
at org.jminim.lib.OhNetService$TimerThread.run(OhNetService.java:1247)

"Thread-5" id=29 WAITING
at java.base@21.0.12.1/java.lang.Object.wait0(Native Method)
- waiting on org.jminim.lib.HTTPService$SocketThread@50ae448
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:366)
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:339)
at org.jminim.lib.HTTPService$SocketThread.run(HTTPService.java:432)

"Thread-6" id=30 RUNNABLE (in native)
at java.base@21.0.12.1/sun.nio.ch.Net.accept(Native Method)
at java.base@21.0.12.1/sun.nio.ch.NioSocketImpl.accept(NioSocketImpl.java:748)
at java.base@21.0.12.1/java.net.ServerSocket.implAccept(ServerSocket.java:698)
at java.base@21.0.12.1/java.net.ServerSocket.platformImplAccept(ServerSocket.java:663)
at java.base@21.0.12.1/java.net.ServerSocket.implAccept(ServerSocket.java:639)
at java.base@21.0.12.1/java.net.ServerSocket.implAccept(ServerSocket.java:585)
at java.base@21.0.12.1/java.net.ServerSocket.accept(ServerSocket.java:543)
at org.jminim.lib.HTTPService.runServerThread(HTTPService.java:376)
at org.jminim.lib.HTTPService.access$200(HTTPService.java:32)
at org.jminim.lib.HTTPService$1.run(HTTPService.java:361)
Locked synchronizers:
- java.util.concurrent.locks.ReentrantLock$NonfairSync@8e9a6d8

"Thread-15" id=40 RUNNABLE (in native)

"Thread-24" id=49 WAITING
at java.base@21.0.12.1/java.lang.Object.wait0(Native Method)
- waiting on org.jminim.lib.HTTPConnection@6587f32e
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:366)
at java.base@21.0.12.1/java.lang.Object.wait(Object.java:339)
at org.jminim.lib.HTTPConnection.getRequest(HTTPConnection.java:110)
at org.jminim.lib.HTTPConnection.access$1700(HTTPConnection.java:18)
at org.jminim.lib.HTTPConnection$WriterThread.runWriterThread(HTTPConnection.java:4​45)
at org.jminim.lib.HTTPConnection$WriterThread.run(HTTPConnection.java:430)

"Thread-25" id=50 RUNNABLE
at java.management@21.0.12.1/sun.management.ThreadImpl.dumpThreads0(Native Method)
at java.management@21.0.12.1/sun.management.ThreadImpl.getThreadInfo(ThreadImpl.java:482)
at org.jminim.core.LogImpl.writeCrashDump(LogImpl.java:1249)
at org.jminim.core.LogImpl.printStackTraceSync(LogImpl.java:1174)
- locked org.jminim.core.LogImpl@f43101
at org.jminim.core.LogImpl.reportErrorEx(LogImpl.java:258)
at org.jminim.lib.HTTPConnection$ReaderThread.run(HTTPConnection.java:137)

- - - - - - - - - - - - - - - -
Find all posts by this user
Quote this message in a reply
Yesterday, 19:15
Post: #7
RE: Minimserver crashes when media drive connected
Thanks for this. MnimServer has crashed because it received an HTTP request that it isn't expecting. To see what this unexpected request is, I need to see a debug log. Please do the following:

1) Start MinimServer with the drive disconnected
2) From the minim icon, select 'Show log'
3) In the MinimServer log window, set the logging level to Debug
4) Connect the drive
5) After the Pi crashes, restart the Pi
6) Don't start MinimServer. Instead, copy the minimserver/data/minimserver.log file to some other location.
7) Zip or compress the minimserver.log file that you have copied (this step is important)
8) Attach the compressed log file to a post here

I wil look at the log file and advise you on next steps.
Find all posts by this user
Quote this message in a reply
Yesterday, 19:57
Post: #8
RE: Minimserver crashes when media drive connected
(Yesterday 19:15)simoncn Wrote:  Thanks for this. MnimServer has crashed because it received an HTTP request that it isn't expecting. To see what this unexpected request is, I need to see a debug log. Please do the following:

1) Start MinimServer with the drive disconnected
2) From the minim icon, select 'Show log'
3) In the MinimServer log window, set the logging level to Debug
4) Connect the drive
5) After the Pi crashes, restart the Pi
6) Don't start MinimServer. Instead, copy the minimserver/data/minimserver.log file to some other location.
7) Zip or compress the minimserver.log file that you have copied (this step is important)
8) Attach the compressed log file to a post here

I wil look at the log file and advise you on next steps.

See attached. Thank you so much for helping me out!

.zip  Minimserver log.zip (Size: 30.27 KB / Downloads: 2)
Find all posts by this user
Quote this message in a reply
Yesterday, 21:29
Post: #9
RE: Minimserver crashes when media drive connected
Thanks for this. This log shows two things:

1) The error in the crash file isn't related to the problem with reading the disk. The debug log file that you sent has no evidence of the crash. The crash file is from 27 September and it might be too late now to identify what caused this HTTP problem. I will improve the way MinimServer handles this situation if it should occur again.

2) The crash is caused by a disk I/O error. Something on the disk is corrupted. The file scan is proceeding normally until it gets to this file:

Barrington Levy/Barrington Levy - Hunter Man/02 shaolin temple.mp3

After this, all other files that are scanned produce I/O errors but MinimServer handles these errors correctly and doesn't crash. I think the crash is probably caused by something else trying to access these bad files or write to the disk. Running fsck should give you more information about the disk errors.
Find all posts by this user
Quote this message in a reply
Yesterday, 22:10 (This post was last modified: Yesterday 22:38 by Pdog.)
Post: #10
RE: Minimserver crashes when media drive connected
(Yesterday 21:29)simoncn Wrote:  Thanks for this. This log shows two things:

1) The error in the crash file isn't related to the problem with reading the disk. The debug log file that you sent has no evidence of the crash. The crash file is from 27 September and it might be too late now to identify what caused this HTTP problem. I will improve the way MinimServer handles this situation if it should occur again.

2) The crash is caused by a disk I/O error. Something on the disk is corrupted. The file scan is proceeding normally until it gets to this file:

Barrington Levy/Barrington Levy - Hunter Man/02 shaolin temple.mp3

After this, all other files that are scanned produce I/O errors but MinimServer handles these errors correctly and doesn't crash. I think the crash is probably caused by something else trying to access these bad files or write to the disk. Running fsck should give you more information about the disk errors.

Thanks for this.

I checked the drive, no issues. Replaced the cable...all working fine!!!

I wouldnt have got there without your advice! Thank you
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 3 Guest(s)