fysmd

Thank you so much for helping so quickly! Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... writing modified primary superblock sb realtime bitmap inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 97 resetting superblock realtime bitmap ino pointer to 97 sb realtime summary inode 18446744073709551615 (NULLFSINO) inconsistent with calculated value 98 resetting superblock realtime summary ino pointer to 98 Phase 2 - using internal log - zero log... 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. So, do I just mount in unassigned drives, or start the array?

Phase 1 - find and verify superblock... bad primary superblock - bad CRC in superblock !!! attempting to find secondary superblock... .found candidate secondary superblock... verified secondary superblock... would write modified primary superblock Primary superblock would have been modified. Cannot proceed further in no_modify mode. Exiting now.

Unraid Pro v6.6.3 - diag attached. I noticed a drive was emulated earlier today (only after the Mrs said that Plex was misbehaving! - must check my notification setting!!) The GUI says that content is emulated but actually, it's not there. The user share is available but the files which were on the faulty drive are not there. At first, navigating to the parent directory in a shell errored: an@Server:/mnt/user/TV$ cd The\ Deuce/ ian@Server:/mnt/user/TV/The Deuce$ ls -la /bin/ls: reading directory '.': Input/output error total 0 ian@Server:/mnt/user/TV/The Deuce$ So I stopped the array and restarted, now I can navigate to the directory, but not the sub directory which was mounted on the failed drive (split season directories) The faulty drive (disk17 appears in unassigned drives section now (ST3000DM001-1CH166_W1F47CAF) How should I proceed? server-diagnostics-20181201-1739.zip

Nahh, the HDHRs are on the same LAN and subnet and pingable, including from the server As I said, I can add manualy and it'll progress but fail to enable properly I had a backup but as I've replaced my USB in the last 12 months, I need to wait for a replacement license from LimeTech - No way the house would function without Plex for that time so I chose to restart from scratch (other than this plex issue it was really easy!) I have recreated a new instance of plex, stopped my other and find that running this new instance (no media added or anything) it auto detects the HDHRs properly and immediately, the rest of the setup process also completes successfully too. I must have some broken config somewhere??

Hey Guys, I've been running LSIO's Plex container for MANY years on unraid with great sucess now (so thank you!) Unfortunately I've recently had hardware issues (failed USB) and so until get a replacment license I rebuilt my machine on a temp Unraid license. Since then, my Plex container has not been able to see my HDHRs and is has no idea that DVR has been configured and running for a long time No DVR so nothing is recording If I try to re-add my DVR, I get the "introducing Live TV & DVR" splash and when I hit "Set up Plex DVR" I get "There was a problem discovering devices" If I manually enter the IP address of one of my HDHRs the setup wizard progresses and says complete but no DVR links appear in my menus

OK, I've done this and got things most;ly back online - it sounds a lot more daunting that it actually is. I found that a fresh install, install temp license, shutdown, pop super.dat on boot USB will not work as a perm license is required So removed it and configured from scratch, assign drives etc. Docker had no config but existing containers started up and ran perfectly - they need to be removed and recreated in order to stop common problem moaning about them, or upgrade them etc. Nice n easy and no Data loss. I do have a small issue with plex (linuxserver.io container), I can't make DVR work again but I suspect this is either unrelated or something to do with mover having begun shifting my container appdata folder off cache to the array.

The trial license button is grey

HELP! My system is down, I've had a second USB stick failure within a year of replacing a very old one I've reformatted and restored to it but it's not happy. I've emailed support as per advise but is there any way I can get my server back online with a temp key or anything?

So I think my issue was a corrupted USB boot. Replacing files as above did get further (booted) but nothing came up properly, Disk was full of chkdsk files etc and so I formatted and started again. Unfortunately, the files in config (mostly plugins) were corrupt so now wresting a restore from backups

I'm having exactly the same, GRUB screen with boot options displays but the countdown from 5s runs to zero then restarts. I can move the selection around and pressing tab to edit options works but none o the boot options (including Memtest) work. I'll try the solution proposed and report.

I tried this and lost the content from the rest of my disks - about to retry to avoid more RFS issues I tried to exclude all RFS disks from all my shares - is this the same thing?

I'm not new to unraid but how do we direct all writes to a particular drive?

So would a couple of these fellas http://www.supermicro.com/products/accessories/addon/aoc-sas2lp-mv8.cfm be better? I'm very confused, these seem to have good feedback in Limetech forums but are also Marvell chipset I think??

I don't have a different controller to try Wonder why it's suddenly happened..

HI, more information: I found that disk3 was causing issues, simply cat filename >/dev/null on a large files from each disk worked fine for all but disk3. Files from disk three would produce no errors but nor were they reading data in any measurable way. (my parity check was also seemingly hung like this). I also found the AHCI setting and changed it, rebooted with disk3 still connected (I replaced the sata cable) and the machine hung while playing risers transaction logs (I waited all day!) I've now disconnected drive3, started in safe mode and am waiting for other drives to mount: Sep 9 10:52:05 server emhttp: shcmd (76): set -o pipefail ; mount -t reiserfs -o noatime,nodiratime /dev/md1 /mnt/disk1 |& logger Sep 9 10:52:05 server kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal Sep 9 10:52:05 server kernel: REISERFS (device md1): using ordered data mode Sep 9 10:52:05 server kernel: reiserfs: using flush barriers Sep 9 10:52:05 server kernel: REISERFS (device md1): journal params: device md1, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Sep 9 10:52:05 server kernel: REISERFS (device md1): checking transaction log (md1) My two controllers are these: https://www.amazon.co.uk/dp/B00ESFEI2E/ref=pe_385721_51767431_TE_dp_2

I do have two small IDE drives but no multipliers :-O which drives seem to be on multipliers (how do I identify these in the diag?) Previous parity checks have all run quickly (no hardware changes) 2017-09-05, 22:10:41 21 hr, 25 min, 35 sec Unavailable Canceled 4 2017-09-03, 11:08:11 21 min, 17 sec Unavailable Canceled 0 2017-09-02, 18:53:16 20 hr, 53 min, 15 sec 26,6 MB/s OK 0 2017-08-02, 12:30:19 14 hr, 30 min, 18 sec 38,3 MB/s OK 0 2017-07-04, 02:41:18 14 hr, 37 sec 39,7 MB/s OK 0 2017-07-02, 12:40:22 14 hr, 40 min, 21 sec 37,9 MB/s OK 0 2017-06-29, 12:22:27 16 hr, 48 min, 46 sec 33,1 MB/s OK 0 2017-06-02, 13:10:38 15 hr, 10 min, 37 sec 36,6 MB/s OK 0 2017-05-29, 23:23:39 14 hr, 13 min, 12 sec 39,1 MB/s OK 0 2017-05-22, 22:18:15 14 hr, 15 min, 37 sec 39,0 MB/s OK 0 any tips / things I should check at all?

Hello all! After some odd behaviour (can't allocate socket?). I had to restart my server last night, Reboot in gui (I had to wait approx 15 mins to get the web page to open!) didn't work. Powerdown didn't work (left it over an hour to do it's thing) so I had to drop power The machine took a VERY long time to come back up and now it's up, things appear to be running but parity check is running VERY slowly at 340KBps and will take well over a month to complete. It's normal done in approx 20 hours. I only see pre clear plugin issues in logs, where else should I be looking / what should I do next? Thanks for any support! Diag attached. server-diagnostics-20170905-0627.zip

HI!, I'm sorry I'm being unclear. I have noticed that files above the split level seem to be getting placed on seemingly random drives. The list I posted is simply the display unraid web gui has when I navigate into my TV share and then a show. I understand that they apply to new writes but I dont follow what logic is used to place files which are created above the split level, it it simply going to use the allocation method defined for the share? some files in the example Iposted have foound their way on to disk7, which I htink has been "full" for a very long time now... I notice that I often have very many more drives spinning that I should have and I suspect that it's because my TV show metadata files are all over my array.

Hi All, What is the drive allocation logic for files created above a share's split level? I have split lelvel 2 on my TV share so all files for a sean directory stay together on a disk. I'm seeing show metadata files what sit in the show directory, above season directories on many drives which don't seem to have any relationship to the drives selected for the seasons: Season 01 Disk 3 2016-08-14 14:35 Season 02 Disk 6 2016-08-14 14:35 backdrop.jpg 422 KB Disk 13 2016-08-06 15:23 banner.jpg 44,3 KB Disk 15 2015-07-12 21:14 cover.jpg 210 KB Disk 15 2015-07-12 21:14 fanart.jpg 802 KB Disk 15 2015-07-12 21:14 folder.jpg 210 KB Disk 15 2015-07-12 21:14 poster.jpg 210 KB Disk 15 2015-07-12 21:14 season-all-banner.jpg 44,3 KB Disk 15 2015-07-12 21:14 season-all-poster.jpg 210 KB Disk 15 2015-07-12 21:14 season-all.tbn 210 KB Disk 15 2015-07-12 21:14 season-specials-poster.jpg 115 KB Disk 13 2016-08-06 15:23 season01-poster.jpg 213 KB Disk 15 2015-07-12 21:14 season01.tbn 213 KB Disk 15 2015-07-12 21:14 season02-poster.jpg 167 KB Disk 7 2016-02-12 04:13 season02.tbn 167 KB Disk 7 2016-02-12 04:13 season03-poster.jpg 115 KB Disk 17 2016-09-04 06:32 series.xml 2,06 KB Disk 13 2016-08-13 05:39 tvshow.nfo 1,80 KB Disk 15 2017-03-12 05:55

I feel dumb now - thanks!! I'll go RTF err L

I thought SMART look clean too - no more errors reported. How / where in the diag so I see teh read errors you mention, I'm interested.. I ran a log SMART test and nothing reported.

Diag attached. After a restart the error counter is increasing again, disk still enabled. server-diagnostics-20170306-2239.zip

Unraid 6.3.2 HITACHI_HUA721010KLA330 drive - from SMART: 10 Spin retry count 0x0013 100 100 060 Pre-fail Always Never 0 12 Power cycle count 0x0032 100 100 000 Old age Always Never 74 192 Power-off retract count 0x0032 100 100 000 Old age Always Never 96 193 Load cycle count 0x0012 100 100 000 Old age Always Never 96 194 Temperature celsius 0x0002 157 157 000 Old age Always Never 38 (min/max 15/49) 196 Reallocated event count 0x0032 100 100 000 Old age Always Never 0 197 Current pending sector 0x0022 100 100 000 Old age Always Never 0 198 Offline uncorrectable 0x0008 100 100 000 Old age Offline Never 0 199 UDMA CRC error count 0x000a 200 200 000 Old age Always Never 0 Soon after I added this drive (preclear was fine, only one pass though) my array now shows this drive with 96 errors onthe Main page. No Smart errors report on the dashboard. I've asked Google and she seems to suggest that these are no cause for concern as the counter increases each time the drive parks the heads. I have other similar drives which I was going to add to my array and they all have the same thing in power off and load cycle. Do we think that Unraid should be reporting these values as errors?

Thanks, I dont know about the PSU but four drives are in an external enclosure and the only cards installed are three sata controllers. My issues seem to have been cable related - I found a few older cables which did not have any locking mechanism on either end. Bet I knocked / shifted 'em. Replaced them all and I've not seen any errors since. I've pre-cleared drives and completed parity checks with no errors reported so i think all is well again. Thanks for everybody's help.

Thanks both! That drive is already on a new sata cable, will switch to another port and try. PSU is a modular 550W, dont have specifics to hand.