Ong Hui Hoong

just finish the -vL

should i do it with the parity disk in? it look like writing some data in to parity :(

or should i just format the disk?

afrer with -L, still same, and there is some read write on the parity, did i screw up? :(

using GUI, i have run the check with -n, then without any option. and now running with -L

ok i will do the repair now, i will update again.

i have stop the array and change the files system to sfx. but it still show as unmounted, should i follow the xfs_repair repair 1st?

should i stop now? i start to panic already :(

i started the array follow the instruction, but my folder still missing, is that normal?

ah, too bad then, let me follow ur instruction and start the array now ...

anyway, before i start, 1 question, can i start the array without the disk1? can i emulate the disk1 to confirm the data is there? then 2nd round only i add in the corrupted disk1 for rebuild?

understand very clearly on the instruction, i will do it now, wish me luck #FingerCross ...

yes im using default xfs, using latest stable 6.8.3 version. and is single parity array, with 6 ( 5 ok + 1 corrupted drive) and only 1 data drive needed to be rebuild. this should be the correct order of the HDD, the corrupted drive should be in slot 1 which i have not assign in yet. do let me know the step by step that i need to bring up the corrupted drive.

yea something like that, if can recover 95% i will be happy already.

the server is now up but array not started. so all HDD is 'not in use' per say

oh ya this happen because my boot drive die, i have to start the array in new config. which is y i added in the disk :( very worry now, all my critical data was on that disk. i have my party drive assign correctly now, all my data drive assign correctly also. i need a solution to rebuild the corrupted data drive back from the parity and my other data drive. i still in panic mode now :(

Hi All, i have make a mistake to swap 1 of my data disk with my parity disk, i notice the mistake and stop the array immediately. but the data drive has been corrupted as cannot be detected, but my parity disk i believe still intact. is there anyway i can rebuild back my data drive using the parity drive? i have click the new config, i have add back all the drive to the correct location (except corrupted Data disk i did not add in yet) i start the array with parity is valid option and did not add the corrupted data disk and start array. but all my folder in the corrupted data disk still missing. is there anyway for me to emulate the corrupted disk? since actually all my data still consider there, i just have to use the parity and my other data drive to rebuild back my corrupted disk.

i added in the 2 MQTT variables in now should i able to start/stop VM from HA? i got this error on HA

the vm show up already, but not all my VM, the pfsense is missing, donno when it started showing up, maybe when i was in office it show up, but i cannot turn on or shut it down

er... sorry ah, where do i do the MQTTCacheTime configuration ya ... hehe

Hi, i donno what i did wrong, my HA cannot see my VM info at all this is my UnraidAPI config I'm running a VM HA in UNRAID with the IP address of 192.168.11.119 i hide the docker from UnraidAPI web, because i only wan HA to manage my VM i donno what i miss out, this is the only thing i see from HA, (exclude e docker i disable). do anyone have a end to end guide?

Hi All, i'm having issue using Intel quick Sync, my driver load thing and the go files configuration is done and i know is working becos my plex is hardwar trancoding using qulcik sync, but when i add the same parameter in HandBrake, it does not seem to work. The Intel QSV does show up but when i try to encode a video with it, it will end with error. it will just fail like that. i add the parameter same as the one i did on plex. do need help on this to make it work. I'm running on a Intel Gen 4 i7 4790 processor.

Thanks @SpaceInvaderOne, I'm able to redo as you suggested everything restored anyway how do i do the timezone thing? my timezone is GMT+8, i think this new template will be able to fix the timezone thing now ...

latest update break the docker, config seem to ave more thing now, @SpaceInvaderOne might need to make a new tutorial for all the new option

I'm having the same issue as well