skyking376

I thought for sure there would be parity errors with all the on/off cycles. Parity came back normal! Should I be worried about the "76% used"? What is this by the way? Attached is diagnostics AFTER normal power up and parity check complete. Thank you for inputs. deathstar-diagnostics-20250325-1543.zip

So i'm the tech support for my father-in-law and he is getting old and crap at telling me when things need fixing. Unraid box "wasn't working" for almost a year and he just told me now! WTF dude? Anyway... The symptoms from him were "I'd turn box on, and then about a minute later it would shut itself off". Turned out the bracket holding the cpu fan broke and cpu fan was disconnected from cpu = too warm and shutdown in ~1-2 min after power on. Since this happened for 6-12 months I'm SURE there are probably some disc parity errors and maybe other things? We'll see. I'm currently running a parity check on 4TB system (1 4TB data disc and 1 4TB parity drive). However I looked in syslogs and scrolled just to look at any "red" items. Next to a few red items (unable to write to disk1) is a yellow warning "Rootfs is getting full (currently 76% used)". 1) What does this mean? 2) How to fix/clean/empty whatever is causing this? 3) Any other obvious problems that I may encounter in the coming months? Thank you for your help deathstar-syslog-20250324-2111.zip

Ok, So if I remove this drive from my array (so I can test it on another machine) do I have to rebuild parity when I start array back up? Different question, I know in past versions of unraid there as a "preclear" to write zeros to every part of drive. Does this still exist somewhere so I can get disk 5 tested, precleared, and then I just plug it in (outside of array)? Thank you for help.

I'll try different power and data cables but is there any chance this drive's power issues are from the drive side of things? Meaning drive is faulty or dead?

So after "2nd" parity check finished this morning I did clean shutdown, changed SATA power cables and data cables like instructed. I just powered on and array not started as it detected a new disk (where you can use dropdown to pick which you want to assign). Disk 5 is a "blue square" instead of a green circle like all other drives and it was already preselected in proper spot and on far right in red it say "all data will be overwritten when array started". Ok, I start array and it is going through same process of parity check again! In previous parity checks as array was started parity check was immediately "paused" and in both times I had to click either "resume" or "cancel". I picked "resume" in both cases. So just now it is same thing?!?!? So do I click on "resume" again? I'm in same "loop" as previous...what do I do to add new drive? New diagnostics (as parity process is currently paused) and screen cap. deathstar-diagnostics-20240526-1158.zip

Followed directions from this link: https://docs.unraid.net/unraid-os/manual/storage-management/#adding-disks Got all the way through step 7 and it completed. Expecting to see step 8, but I didn't see any option to "format disk". So I stopped array thinking maybe I after the clear if you stop array, then restart array it would see "new cleared disk". Nope, it is now going through step 7 again with parity check (like it did earlier). Maybe I'm incorrectly thinking "parity check" is same as "preclearing". I never saw any message saying "clearing disk before enter into array" but I am following steps to the letter so....???? Here is screenshot and diagnostics. It's maybe 10 min into "2nd" parity/clear phase and I plan to let it finish (1st one had no errors). What am I doing wrong, and what should I do? deathstar-diagnostics-20240525-2350.zip

Many on this forum have help this noob with very basics. In previous posts I had failing cables and failing drives. After getting everything working normal again I have 2 drives that show up in "Historical Unassigned Devices" section. The 2 drives listed in that section were at some point "not recognized and unmounted", but given instrutions on this forum got those 2 drives to work properly again and Unraid is working great. Does this mean what it's title says "in the past these were detected as unassigned"? Meaning can I click on the little red "X" to remove them from this list? What if any repercussions dose removing them have? Thank you

Ok, wasn't sure if starting array was safe with red "X" or not as I didn't want to get a parity check to run and possibly start messing up data on disk 4. So just started array, same thing "Device disabled, contents emulated". I don't fully understand what you mean when you say "mounting". I can see disk 4 in UNRAID GUI either when array is started or stopped. When array is stopped (via unraid GUI) I then go to folder and can't see any of my movies/TV shows in folder structures they are normally in (Movies/Kids/TV/etc). It says "folder is empty" at the top network level of "Tower". When array is started I CAN see Movies/Kids/TV/etc in their folder structures below that top level "Tower" folder. Does "mounted" = I can see all my movies/kids/tv data? If that is true then I would say disk is disabled (as it says in GUI with red "X") but mounted (if I understand defintion of mounted is). I still error on side of caution and wait for futher instructions before I do anything. Thank you for helping a noob! deathstar-diagnostics-20240404-1410.zip

So delayed thread, but still an issue. Just had ALL sata cables replaced and new (more wattage compared to old) power supply. PC tech did see fluctuations on old power supply but not enough to “need” a new one but I opted to do it anyway just to eliminate those as a cause. So same thing, array is stopped, I can see the correct hard drive serial number in drop down, and disk 4 has red “X” that says when hovering over red x “device disabled, contents emulated”. Does this mean “mounted” like you said previously? Can I start array? I'm too afraid to do anything so I don't lose data (again). what do I do now? (Edit: added diagnostics file) deathstar-diagnostics-20240403-1641.zip

Just happened to look at server and noticed disk 4 "device is disabled, contents emulated". Before I did anything I downloaded diagnostics before I reboot, shutdown, etc. It is currently running as we speak. This is the youngest of my drives (almost 2 years old). Others are 5-9 years old. I haven't touched unraid in weeks, didn't physically move computer case unraid is in, nobody bumped into it, etc. What does it mean, and what to do? deathstar-diagnostics-20240322-2314.zip

Ran parity check, came back no errors (still attached diagnostics and server has been running since Jan 1st through both parity checks). Any idea why errors show up on 1 parity check but not on 2nd parity check or just mysterious fluke? Thank you for help. deathstar-diagnostics-20240117-2001.zip

OK, will run parity and report back with diagnostics again. Thank you

Parity check runs first day of the month. Only checked it today and noticed "335 errors". No power outages (since Jan 1st) and server has been on whole time (before / after Jan 1st parity check). Followed directions to attach diagnostics file. 1) what are the errors? 2) what do I do? Thank you for help deathstar-diagnostics-20240112-0018.zip

I keep reading "convert" from REISERFS to XFS but nothing for new blank drive and adding to size of array. It has also been many years since I added anything new (instead of going from 2TB -> 4TB) so i don't know where in process to select filesystem? Current setup: 4TB Parity Disk 1 2TB reiserfs DIsk 2 2TB reiserfs Disk 3 2TB reiserfs Disk 4 4TB reiserfs What I want to do: 4TB Parity Disk 1 2TB reiserfs DIsk 2 2TB reiserfs Disk 3 2TB reiserfs Disk 4 4TB reiserfs Disk 5 4TB XFS How do I go about this? I assume: 1) plug in new drive and select new drive in config (since unraid will detect drive change) 2) let new disk 5 drive preclear 3) Is this where you pick filesystem? 4) don't know 5) don't know 6) etc

Ok, I did "new config" and it is rebuilding parity. I "think" this means that data from drives 1-4 (poor disk 5 is lost) are being checked and building parity for future protection (during parity process nothing is safeguarded until parity is complete). So then it is an Easter egg hunt when I try to watch a movie/TV and Kodi says "This file is missing, would you like to delete from Kodi" is when I realize that movie/TV was on failed Disk 5. So then looking ahead to prevent for next time: 1) have backups (in addition to parity drive safety) Yes/No? 2) 2nd parity drive? Yes/No? 3) Since I saw something about updated file system ( REISERFS file system is going away 2025) Can I add new drive and have it with XFS file system with others having older reiserfs system? Meaning a mix of file systems? Yes/No? I really appreciate all the help from a non-tech noob. I try to read a lot but lots of this is over my head, but I try.