mattw

I will try this evening to make these changes. I am curious... the dashboard says that the array is offline, but my shares are up... Why?

So, as a followup... with the array in this state, I am still seeing my shares and the files? I am copying off my movies and kids pics to be safe.

It all started when I wanted to remove my cache drive, the system had been unstable after a ram upgrade and the addition of my first cache drive. So, I shut down and removed the ram. Booted up and everything was good. Did tools>new config and cleared the config and marked the cache drive and not installed. Rebooted to an offline array that wanted me to reassign devices. This is where the problem begins... my parity drive and one of my 2TB data drives are 1 digit different in the serial number and I reversed them and rebooted. System restarted and started a parity check, which I canceled because I thought it was odd. Looked at the disk assignments are realized I had really screwed up. I reassigned the drives and rebooted with parity valid checked to try and avert more damage. Realizing what I had done, I unassigned the parity disk and moved it to the array and started the array. It now tells me that the 2 WD drives are unreadable, I somewhat expected that since it likely over wrote part of one or the other. The cache drive that started all of this was on a PCI controller, I removed the controller and moved the empty cache drive to one of my mobo sata controller ports. So, how screwed am I? I do not have a backup since getting to an offsite backup at 30Mbps is painful. The loss of years worth of movies and all of my digitized cd collection will be painful. I am in this state now... parity drive in array and array not starting, but it knows about my shares. The system now thinks my array is 70% full, was 49% before this adventure. Interesting stuff from the logs... disk 3 sees corruption, was the disk swapped in place of the parity drive. Disk 5 is showing unsupported file system (real parity drive). Dec 18 20:02:36 Tower emhttpd: shcmd (154): mkdir -p /mnt/disk1 Dec 18 20:02:36 Tower emhttpd: shcmd (155): mount -t xfs -o noatime,nouuid /dev/md1 /mnt/disk1 Dec 18 20:02:36 Tower kernel: SGI XFS with ACLs, security attributes, no debug enabled Dec 18 20:02:36 Tower kernel: XFS (md1): Mounting V5 Filesystem Dec 18 20:02:36 Tower kernel: XFS (md1): Ending clean mount Dec 18 20:02:36 Tower emhttpd: shcmd (156): xfs_growfs /mnt/disk1 Dec 18 20:02:36 Tower root: meta-data=/dev/md1 isize=512 agcount=4, agsize=91571160 blks Dec 18 20:02:36 Tower root: = sectsz=512 attr=2, projid32bit=1 Dec 18 20:02:36 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Dec 18 20:02:36 Tower root: = reflink=1 bigtime=1 inobtcount=1 Dec 18 20:02:36 Tower root: data = bsize=4096 blocks=366284638, imaxpct=5 Dec 18 20:02:36 Tower root: = sunit=0 swidth=0 blks Dec 18 20:02:36 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Dec 18 20:02:36 Tower root: log =internal log bsize=4096 blocks=178849, version=2 Dec 18 20:02:36 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Dec 18 20:02:36 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Dec 18 20:02:36 Tower emhttpd: shcmd (157): mkdir -p /mnt/disk2 Dec 18 20:02:36 Tower emhttpd: shcmd (158): mount -t xfs -o noatime,nouuid /dev/md2 /mnt/disk2 Dec 18 20:02:36 Tower kernel: XFS (md2): Mounting V5 Filesystem Dec 18 20:02:37 Tower kernel: XFS (md2): Ending clean mount Dec 18 20:02:37 Tower emhttpd: shcmd (159): xfs_growfs /mnt/disk2 Dec 18 20:02:37 Tower root: meta-data=/dev/md2 isize=512 agcount=4, agsize=91571160 blks Dec 18 20:02:37 Tower root: = sectsz=512 attr=2, projid32bit=1 Dec 18 20:02:37 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Dec 18 20:02:37 Tower root: = reflink=1 bigtime=1 inobtcount=1 Dec 18 20:02:37 Tower root: data = bsize=4096 blocks=366284638, imaxpct=5 Dec 18 20:02:37 Tower root: = sunit=0 swidth=0 blks Dec 18 20:02:37 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Dec 18 20:02:37 Tower root: log =internal log bsize=4096 blocks=178849, version=2 Dec 18 20:02:37 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Dec 18 20:02:37 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Dec 18 20:02:37 Tower emhttpd: shcmd (160): mkdir -p /mnt/disk3 Dec 18 20:02:37 Tower emhttpd: shcmd (161): blkid -t TYPE='xfs' /dev/md3 &> /dev/null Dec 18 20:02:37 Tower emhttpd: shcmd (162): mount -t xfs -o noatime,nouuid /dev/md3 /mnt/disk3 Dec 18 20:02:37 Tower kernel: XFS (md3): Mounting V5 Filesystem Dec 18 20:02:37 Tower kernel: XFS (md3): Corruption warning: Metadata has LSN (1:115531) ahead of current LSN (1:71954). Please unmount and run xfs_repair (>= v4.3) to resolve. Dec 18 20:02:37 Tower kernel: XFS (md3): log mount/recovery failed: error -22 Dec 18 20:02:37 Tower kernel: XFS (md3): log mount failed Dec 18 20:02:37 Tower root: mount: /mnt/disk3: wrong fs type, bad option, bad superblock on /dev/md3, missing codepage or helper program, or other error. Dec 18 20:02:37 Tower root: dmesg(1) may have more information after failed mount system call. Dec 18 20:02:37 Tower emhttpd: shcmd (162): exit status: 32 Dec 18 20:02:37 Tower emhttpd: /mnt/disk3 mount error: Wrong or no file system Dec 18 20:02:37 Tower emhttpd: shcmd (163): umount /mnt/disk3 Dec 18 20:02:37 Tower root: umount: /mnt/disk3: not mounted. Dec 18 20:02:37 Tower emhttpd: shcmd (163): exit status: 32 Dec 18 20:02:37 Tower emhttpd: shcmd (164): rmdir /mnt/disk3 Dec 18 20:02:37 Tower emhttpd: shcmd (165): mkdir -p /mnt/disk4 Dec 18 20:02:37 Tower emhttpd: shcmd (166): mount -t xfs -o noatime,nouuid /dev/md4 /mnt/disk4 Dec 18 20:02:37 Tower kernel: XFS (md4): Mounting V5 Filesystem Dec 18 20:02:37 Tower kernel: XFS (md4): Ending clean mount Dec 18 20:02:37 Tower emhttpd: shcmd (167): xfs_growfs /mnt/disk4 Dec 18 20:02:37 Tower root: meta-data=/dev/md4 isize=512 agcount=4, agsize=122094660 blks Dec 18 20:02:37 Tower root: = sectsz=512 attr=2, projid32bit=1 Dec 18 20:02:37 Tower root: = crc=1 finobt=1, sparse=1, rmapbt=0 Dec 18 20:02:37 Tower root: = reflink=1 bigtime=1 inobtcount=1 Dec 18 20:02:37 Tower root: data = bsize=4096 blocks=488378638, imaxpct=5 Dec 18 20:02:37 Tower root: = sunit=0 swidth=0 blks Dec 18 20:02:37 Tower root: naming =version 2 bsize=4096 ascii-ci=0, ftype=1 Dec 18 20:02:37 Tower root: log =internal log bsize=4096 blocks=238466, version=2 Dec 18 20:02:37 Tower root: = sectsz=512 sunit=0 blks, lazy-count=1 Dec 18 20:02:37 Tower root: realtime =none extsz=4096 blocks=0, rtextents=0 Dec 18 20:02:37 Tower emhttpd: shcmd (168): mkdir -p /mnt/disk5 Dec 18 20:02:37 Tower emhttpd: shcmd (169): blkid -t TYPE='xfs' /dev/md5 &> /dev/null Dec 18 20:02:37 Tower emhttpd: shcmd (169): exit status: 2 Dec 18 20:02:37 Tower emhttpd: shcmd (170): blkid -t TYPE='btrfs' /dev/md5 &> /dev/null Dec 18 20:02:37 Tower emhttpd: shcmd (170): exit status: 2 Dec 18 20:02:37 Tower emhttpd: shcmd (171): blkid -t TYPE='reiserfs' /dev/md5 &> /dev/null Dec 18 20:02:37 Tower emhttpd: shcmd (171): exit status: 2 Dec 18 20:02:37 Tower emhttpd: /mnt/disk5 mount error: Unsupported or no file system Dec 18 20:02:37 Tower emhttpd: shcmd (172): umount /mnt/disk5 Dec 18 20:02:38 Tower root: umount: /mnt/disk5: not mounted. Dec 18 20:02:38 Tower emhttpd: shcmd (172): exit status: 32 Dec 18 20:02:38 Tower emhttpd: shcmd (173): rmdir /mnt/disk5 Dec 18 20:02:38 Tower emhttpd: shcmd (174): sync Dec 18 20:02:38 Tower emhttpd: shcmd (175): mkdir /mnt/user0 Dec 18 20:02:38 Tower emhttpd: shcmd (176): /usr/local/sbin/shfs /mnt/user0 -disks 30 -o default_permissions,allow_other,noatime |& logger Dec 18 20:02:38 Tower emhttpd: shcmd (177): mkdir /mnt/user Dec 18 20:02:38 Tower emhttpd: shcmd (178): /usr/local/sbin/shfs /mnt/user -disks 31 -o default_permissions,allow_other,noatime -o remember=0 |& logger Dec 18 20:02:38 Tower emhttpd: shcmd (180): /usr/local/sbin/update_cron Fix common problems is also reporting this for every share on the drive, somewhat expected i think.

My current server is old, not horribly slow and always runs on less that 110 watts and idles around 60 watts. Specs: Lian Li PC-A77 in silver with EX-H33 bays ASRock FM2A85X Extreme6 AMD A10-6700 12 gig of ddr3 1600 ram 1 parity disk 5 data disks 1 cache disk. 1 DVD drive 1 ASM 1061 2 port PCI card 600 watt Silencer PSU I run between 2 and 4 docker containers at a time, the 2 busiest are Plex and Unraid-API talking to Home Assistant. I would like to make it more modern, would keep the same array with maybe a couple of up sizes. I am thinking a 6 core i5 like a 9600 or a 10600 or 11600 and I do not run a graphics card, so these have integrated graphics. I would try to stay with a 65 watt CPU, fans run slower, chip runs cooler. I would like a mobo with at least 6 SATA onboard, 8 would be even better. I would likely give it 24 or 32 gigs of RAM. I would like to set up a lite VM running Debian to off load or replace a Pi4 utility system I run. It runs PiHole, Smokeping, Nut client and server, Samba and a couple of other minor things such as catching my local backups of HA and my HA test instance, also caught by Unraid and Google Drive. I could not see pinning more than 2 cores to the VM and 4 gig of RAM. Am I way off base? Please provide your thoughts as I have not built Unraid since this system was new.

I am still rockin the old Lian Li PC-A77 in silver. Using Lian Li EX-H33 kits I can get 12 3.5" drives in very cleanly and cool. Could ramp up the density to 20 drives with the right 5.25" bay adapters.

I have installed this and allowed it to index but stopped the process before it completed. I have not been able to find good docs regarding what it will actually delete since it sounds like the user has no control... I will have some dupes, they will not have the same name and some may end up in odd places. The odd places contain the content that I want gone, not my photo/media/music folders that I want the removed from. Am I overlooking docs somewhere? Matt

So, I found my problem... the DBNAME was not pointed to a mapped location.

I am running Unraid Plus 6.11.5 with docker containers Plex and Tasmobackup. Please see the dashboard cut below... the cpu is running high because I have a preclear running as well. But, this problem exists when no preclear is running as well. What worries me is the Tasmobackup log size in the cut below. I can't seem to find the logfile to save my soul. The only 2 that I run often or allow to autostart are Plex and Tasmobackup. The Tasmobackup logs are being spammed by the following entry: I really do not have enough knowledge to troubleshoot this problem. Here are the container settings for Tasmobackup.

Thanks for confirming!

I am running Unraid on an ASRock FM2A85X Extreme6, so this board while really nice is only PCI-e 2.0. It is my understanding that a PCI-e 3.0 card is backwards compatible with PCI-e 2.0. This indicates to me that I should be able to install any of the LSI Sata HBA's into the system for more Sata ports. But, before I buy one and flash it to IT mode, I wanted to confirm my thinking. I also assume that the throughput should be comparable to my 7 onboard Sata ports that I am currently using? I am currently planning to replace older 1-3tb drives as I can afford newer drives, but currently have all of my ports full between pairity, cache and online data. Thanks Matt

So, I have a crappy old D-link DNS-343 nas that had an ftp client onboard that I used to login to my local server and grabbed the /etc and /var directories in case of a system failure I would have my base configs for things like smokeping, nut and a couple of other services. I have not been able to find an unraid equivalent that I can schedule to pull a copy once a day and overwrite the existing copy on my nas. I have tried Filezilla, but it seems to have no automation and almost everything else I have found is an ftp server, not client. What am I missing? BTW neither system has any inbound internet access, only outbound so I am not super worried about attacks from the outside. Thanks Matt

Thanks for the help and confirmation.

Posting this as a follow up... I have not tired to bring the array online, but I did make a brand new USB key and placed my key file on it and the system is booting 6.11.5 and I was able to register the new key with my Plus license! My CPU is an AMD A4-5300 with 8 gigs of ram... These are the installed drives and I believe the first 2 that cannot be read are the parity drives. How should I proceed?

Ok, so back in '13 life really screwed me over for a bit. My machine with my Unraid key backup literally caught fire, we had 2 young kids and some major heath stuff going on. Not a problem, the server was fine. Forward a few months and the server was not fine, it died and I did not have time or energy to revive it. Now, I have the hardware alive only to find out what had died was the USB key. I think I have the GUID of the old drive and I have my Plus license key and I had an old copy of the Unraid image. Today I restored the image, but need to get my Plus key to work. I think that I need to have someone do some magic with the GUID of my new drive to get it working? I think I can identify the parity drive because it should be one of the two largest drives in the server, and of the 2 I think I built it will the parity drive on the last sata port in the system. I also believe that the drives sda to sde are in the order the system was built. Just have to get this key issue sorted. Tom Mortensen with Lime had helped me get it going back then and I worked with him on some beta ethernet drivers in this version to support my mobo. Not even sure if he is still with them. I will also need an image of 5.0.4, I think. Any help would be appreciated greatly. If I get it running, I will want to upgrade to something current, if I can. Thanks Matt PS can I bring the server up with the parity drive and the first 2 drives only without screwing up the other drives?