Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About pg93

  • Rank

Recent Profile Visitors

187 profile views
  1. pg93

    [SUPPORT] malvarez00 - MotionEye

    I am unable to set time zone in UI even after enabling it in the motioneye.conf file "# path to the localtime file # (enable this to configure the system time zone from the UI) local_time_file /etc/localtime" Please guide me how to set time or change timezone for this docker
  2. pg93

    PCIe BUS error

    please check my diagnostics there is no card or device attached to the required pcie port 5 and im not able to figure out which device is having problem. i figured if i switched the graphics cards the iommu group would change and the i will not get this error. also how do i know which pcie port is mapped to the iommu address ?? Sent from my ONEPLUS A5010 using Tapatalk
  3. pg93

    PCIe BUS error

    please help how to solve this error Sent from my ONEPLUS A5010 using Tapatalk
  4. I tried to remove the disk and install spare old disk to rebuild data, the main page now shows as below should i start the sync?? will it affect recovered data or data on other disks??
  5. Hello Everyone, in the morning after i stopped the stalled xfs_repair-L and was trying the below method as suggested by @limetech but the mounting did not succeed as informed by @johnnie.black so i installed a spare disk of 1TB which Unraid didn't accept as its capacity was less than original disk.... then i reinstalled the original 4TB disk with the Corrupted FS and was about to format it leadind to data loss....... I had almost lost hope to get any data back...... but a miracle happened i ran xfs_repair -v one last time without -l or -n and xfs_repair was successful i just lost 1 folder(i checked the lost+found folder but cannot find it) other data seems to be there im still cross checking. I have attached final summary of the successful xfs_repair and my diagnostics. I have following queries: 1. why is the disk2 is still showing that the contents are emulated. 2. should i start the parity sync?? 3. will the parity sync affect data on other disks ?? 4. what steps can be taken to avoid this? 5. i still need support for below error kindly advise Thank you for your superb support guys especially. @johnnie.black @limetech @trurl Disk2 xfs_repair_summary.txt grig-diagnostics-20181108-1346.zip
  6. Agreed, at least this is how OP can try it. I have canceled the xfs_repair -L command and tried to mount the drive i get following msg: root@GRIG:/dev# mount /dev/md2 /tmp/t mount: /tmp/t: wrong fs type, bad option, bad superblock on /dev/md2, missing codepage or helper program, or other error.
  7. xfs_repair is running for more than 11 hours attached status it is stuck at resetting inode 17451088 nlinks from 2 to 18 when i 1st checked in the morning all disks we automatically spinned down please advise should i stop and proceed with following, or insert a new disk and rebuild, only problem is that the new disk i have is a smaller capacity. xfs_repair_l_status.txt
  8. xfs_repair is running with option -L i am waiting for the results, seem it will take a while. Attached is current status report as per the GUI, can i know how severe is this xfs_repair_l_status.txt
  9. pg93

    PCIe BUS error

    Hello everyone, Please advise how to fix below error my syslog is filled with these : Nov 7 21:13:08 GRIG kernel: pcieport 0000:00:1c.4: device [8086:a294] error status/mask=00000001/00002000 Nov 7 21:13:08 GRIG kernel: pcieport 0000:00:1c.4: [ 0] Receiver Error (First) Nov 7 21:13:55 GRIG kernel: pcieport 0000:00:1c.4: AER: Corrected error received: 0000:00:1c.4 Nov 7 21:13:55 GRIG kernel: pcieport 0000:00:1c.4: PCIe Bus Error: severity=Corrected, type=Physical Layer, (Receiver ID) currently array is in maintenance mode and disk2 is under going xfs_repair, but i always get this error and i am not able to figure out which PCIe port this error relates to i have also tried updating bios and changing the slot of the graphics card. grig-diagnostics-20181107-2125.zip
  10. I just now ran the command xfs_repair with option -v and got following output Phase 1 - find and verify superblock... - block cache size set to 1507928 entries Phase 2 - using internal log - zero log... zero_log: head block 94904 tail block 94841 ERROR: The filesystem has valuable metadata changes in a log which needs to be replayed. Mount the filesystem to replay the log, and unmount it before re-running xfs_repair. If you are unable to mount the filesystem, then use the -L option to destroy the log and attempt a repair. Note that destroying the log may cause corruption -- please attempt a mount of the filesystem before doing this. kindly advise should i normally start the array or use xfs_repair -L??
  11. Should i run the xfs_repair in Maintenance mode or can i run it when array is started and my applications are currently running.
  12. The old disk was a 1TB disk and had many SMART Errors (increasing reallocated sector count )due to its old age and unraid was warning me to replace it, about 2 months ago i replaced it with a new 4TB disk. the old disk is not fuctional any more after iunraid successfully rebuilt the data i tried to preclear disk to use it for other purposes during preclear the the disk failed and now even when i try to connect it no unraid doesnot even detect it with unassigned plugin nor do any of my other computers. I also tried with a different usb sata connector, although i can sense the disk spinup. What are my options here??
  13. Ok Diagnostics Attached grig-diagnostics-20181107-1926.zip
  14. please find attached diagnostics let me know if I can proceed with xfs_repair command without the 'n' or is it possible to remove the drive backup format preclear and the reinstall it in the array.http://cloud.tapatalk.com/s/5be2e94ec6787/grig-diagnostics-20181107-1900.zip Sent from my ONEPLUS A5010 using Tapatalk
  15. But the disk is brand new, i dont understand why has this occurred??