Everything posted by LunarstarFurry
-
Was replacing the Parity Drive untill one drive completely go empty
So I recently got 2 10TB HDD to replace my original 2TB HDD, was following the tutorial to replace the Parity first (https://docs.unraid.net/legacy/FAQ/parity-swap-procedure/) which everything seems to go well, and when I try to replace one of the HDD to a newer one, after data rebuild is finish newer drive suddenly goes empty? For me it looks like the Parity Swap went well, but it attempting to rebuild Disk3 seems to go wrong causing all the data on that drive just disappear.( Luckily the old drive still seems to have all the data available so I don't think any data is lost just yet. But now the Disk1 Seems to be throwing a lot of error, Structure needs cleaning, can I safely do XFS Repair on this drive? Also another info as well, initially I was trying to replace the Disk1 with one of the new 10TB Drive right after the Parity Swap, which seems to went well (It shows the new Drive name and everything) but I notice that the storage indicated by UnRAID is remain at 2TB, so I end up restarting the array. That's where the weird thing happened, right after the array stopped the Disk1 just suddenly change back to the old 2TB Drive instead of the 10TB New Drive. Update: try todo a xfs repair and completely failed and it looks like all data in there is lost so I was trying to mount the 10TB which was supposed to replace the drive that have the damage xfs but I'm getting this error (Nov 25 13:50:50 Lunar-UnRAID unassigned.devices: Mount of 'sdc1' failed: 'mount: /mnt/disks/IBM-ESXS_ST10000NM0226_E: mount(2) system call failed: Function not implemented.) Wonderif there's anyway for me to mount this to see if the data is still available? Try to do a fdisk does indicated that there's something in it Disk /dev/sdc: 9.03 TiB, 9931038130176 bytes, 2424569856 sectors Disk model: ST10000NM0226 E Units: sectors of 1 * 4096 = 4096 bytes Sector size (logical/physical): 4096 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: 3602AAF0-6DC7-4E9F-BFEC-947C289BD0FD Device Start End Sectors Size Type /dev/sdc1 8 2424569850 2424569843 9T Linux filesystem I think both the 10TB is 4kn drive not sure if that mattere or not Other Question is assuming the old drive for disk3 is still functional with all the data, Would it be possible for me to try to bring the Original Disk 3 online and rebuild the Disk1 that way? lunar-unraid-diagnostics-20241124-2058.zip
-
Remove Extra Cache Drive from cache pool?
Oh! That seems to works! Thankyou! < 3
-
Remove Extra Cache Drive from cache pool?
So it seems to work well. but I can't seems to move the cache drive up 2 slots both seems to be throwing clear data. Any idea how would I reduce the slot to 2? But besides the obvious now there's a cache showed as Not installed in the page the 1TB seems to work just fine
-
Remove Extra Cache Drive from cache pool?
Here's the Diag file for the server if needed lunar-unraid-diagnostics-20241116-1552.zip
-
Remove Extra Cache Drive from cache pool?
So My Build have 4 drives currently in the Cache Pool, 2*256G SSD and 2*1TB SSD, because I figured that I'm generally only used like 200G of the total cache drive, I wonder what's the process of removing both of the 256G SSD from the pool completely?
-
UnRAID Randomly crashes for some reason?
I'll try to remove Coral to see if that fix anything
-
UnRAID Randomly crashes for some reason?
Here's the Diag Files lunar-unraid-diagnostics-20231031-1626.zip
-
UnRAID Randomly crashes for some reason?
Seems to be something to do with the USB Controller? I do have a Google Coral that's been used by docker, and Zigbee stick, Bluetooth used by VMs
-
UnRAID Randomly crashes for some reason?
It have crashed once again but this time with some new Logs syslog
-
UnRAID Randomly crashes for some reason?
As for the server I changes the idle now only time will tell if that fix the issue, I'll try to change CState if it still crashes
-
UnRAID Randomly crashes for some reason?
Yeah I know the read error on disk but I really doubt it's a disk issue tbh, Been having random read error from they for like half a year now, These 3 SAS Disk aren't even 1 years old and even tho they keep having read error they never drop offline.
-
UnRAID Randomly crashes for some reason?
The server been working for over 2 weeks without crashing, but now it crashes again, now I'll try ur solution. mean while here's the Log I get from the Flash Drive with mirror Log to Drive see if there's any info in it that's useful? syslog
-
UnRAID Randomly crashes for some reason?
(Sorry I miss the message ) I'll give it a check tho I have the same issue way back when I'm using a AMD FX8350
-
UnRAID Randomly crashes for some reason?
UnRAID Version: 6.12.3 CPU: R5 3600X So I've been having this issue for a while now where unraid would just randomly crashed out of nowhere. Already tried to turn on Mirror syslog to flash but where it crashes I do check the log file and turns out the crash log doesn't make it into the log file? Any idea what I could do Next? lunar-unraid-diagnostics-20230830-1558.zip
-
Server crash fandomly (Kernel Null Pointer)
So not sure why simply force an update on the container seems to fix it? (It's already the newest)
-
Server crash fandomly (Kernel Null Pointer)
If I start the Frigate it seems to be running correctly but after 10 minutes or so the entire UnRAID will crash. There's also other 2 active Docker Container running as well and they doesn't seems to cause the server crash. Frigate is running using Bridge Pointed to 5000 Port on UnRAID and it's also using a USB EdgeTPU
-
Server crash fandomly (Kernel Null Pointer)
Lately I'm starting to have a issue where the server crash completely and require a hard restart. Log Provided. Interestingly tho. It only seems to start happening after I add a new IP Camera into the frigate running on Docker, and doesn't seems to crash if I don't have the Frigate Docker Started. syslog
-
"Primary script unknown" while reading response header from upstream
Anyone have any idea what might be causing this issue? As far as what I've seen it's not causing any issue besides showing errors in the log. Plugins I have: Dynamix File Manager, Fix Common Problems, GPU Statistics, Spin Down SAS Drives and VM Backup lunar-unraid-diagnostics-20221116-1540.zip
-
[SUPPORT] blakeblackshear - Frigate
Hugh I'll give it a go in a bit
-
[SUPPORT] blakeblackshear - Frigate
It appears this issue is somewhat related to IOMMU on the Motherboard Without IOMMU Enabled it seems to work completely fine but with IOMMU Enabled, It will runs fine on the first day and start crashing the entire unraid after wards for some reason
-
[SUPPORT] blakeblackshear - Frigate
So starting from yesterday I'm not sure why but starting the Frigate Container will cause my entire unraid to crash and rebooted? I have a USB Coral Stick and a GTX1050 I don't really expect anything in the Diag as It always just straight up crash the entire system Tell me if you need anything! lunar-unraid-diagnostics-20221107-0317.zip
-
Ubuntu 22.04.1 Server installation stuck or crashes
Sometime it works fine sometime it just doesn't work for some reason
-
Disk Read Error from a new drive?
Alright
-
Disk Read Error from a new drive?
Ah so In the future should I just not concerned about this kind of error that doesn't really increase?
-
Ubuntu 22.04.1 Server installation stuck or crashes
So I've been having this issue for a little while now Sometimes the installation will just get stuck on installing Missing Packages or Installing Kernels (Freezes) Sometimes I'll lost control of the VM completely during installation (Cursor is still blinking but can't type anything) Any idea what's happening? Diagnostics file provided. lunar-unraid-diagnostics-20221101-1649.zip