Jump to content

iarp

Members
  • Content Count

    68
  • Joined

  • Last visited

Community Reputation

0 Neutral

About iarp

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I have not had any issues stand out to me, other than noticing this just today. root@storage:~# /usr/local/emhttp/plugins/recycle.bin/scripts/rc.recycle.bin purge Removing aged files... Aged files removed root@storage:/mnt/user/downloads/.Recycle.Bin# stat 2019-20\ Offer\ of\ Commitment.pdf File: 2019-20 Offer of Commitment.pdf Size: 427620 Blocks: 840 IO Block: 4096 regular file Device: 22h/34d Inode: 21807502 Links: 1 Access: (0666/-rw-rw-rw-) Uid: ( 99/ nobody) Gid: ( 100/ users) Access: 2019-03-18 12:43:33.000000000 -0400 Modify: 2019-03-18 12:17:50.000000000 -0400 Change: 2019-03-19 02:07:58.000000000 -0400 Birth: - root@storage:/mnt/user/downloads/.Recycle.Bin# stat Auto\ Maintenance_removed\@group.calendar.google.com.ics File: Auto Maintenance_removed@group.calendar.google.com.ics Size: 8075 Blocks: 16 IO Block: 4096 regular file Device: 22h/34d Inode: 924 Links: 1 Access: (0666/-rw-rw-rw-) Uid: ( 99/ nobody) Gid: ( 100/ users) Access: 2019-03-10 13:03:46.000000000 -0400 Modify: 2018-12-24 17:48:18.000000000 -0500 Change: 2019-03-10 13:03:46.000000000 -0400 Birth: - Update: Found the command thats not finding anything: find /mnt/RecycleBin/User\ Shares/*/*/* -atime +$AGE -exec rm -rf {} \; 2>/dev/null removing one /* from the path and it works.
  2. 2019.03.08b Is there any know issues with Age not being respected? I'm not sure why but a couple shares have .Recycle.Bin data from last year still. Age is set to 3 days. When I try running Remove Aged Files manually the page just refreshes and nothing happens. I'm wondering if theres any way to see the delete command its running, maybe theres an error I'm not getting to see Apr 8 15:04:14 storage ool www[25259]: /usr/local/emhttp/plugins/recycle.bin/scripts/rc.recycle.bin 'purge' Apr 8 15:04:14 storage Recycle Bin: User: Files older than 3 days have been removed
  3. I've just run into this issue because it's the first time I've added or edited shares in years. Editing anything NFS on a share is setting an sid value that another share already has. It's not evaluating what shares/flash are set to and using a unique number.
  4. How do we know that the sectors were on parity side? I'll start another check now just to be sure. It'll take another day to run to find out.
  5. I was just wondering, using the log system if there is anyway possible to track down what is located at the sectors listed as being in error. Also does P corrected mean it auto-fixed parity? I'm not sure where these errors came from, I know we've had 3 power outtages in the last 2 weeks but UPS took over and i manually stopped array and shutdown properly before it ran out every time. May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666581768 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666581792 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666581800 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666581816 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666581832 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666581848 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666581872 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666581904 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666581944 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666581984 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666582048 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666582128 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666582240 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666582280 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666582408 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666582864 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666582872 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666582880 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666582888 May 5 04:09:56 storage kernel: md: recovery thread: P corrected, sector=2666583008 I'm just curious if its possible to track what data is at that sector/location to see if the file(s) are still ok or not.
  6. Has anyone else had issues updating the container and the container just disappearing after saying Successfully updated? Every update I've done it always downloads everything, updates accordingly and says successfully, the page refreshes and then its just gone. I do delete the CONTEXT_PATH, and I only keep the Media path field box. Any chance this could be a cause? To get it running again I just Add Container and select the my-airsonic, delete the unneeded fields and apply. I just double checked the version within Airsonic and it wasn't even updated, so I've no idea what changing here that requires me to update it at all.
  7. Are you talking about editing the container settings via the webgui? If so, thats what I'm trying to do. It'll accept any value but blank, blank resets it back to airsonic.
  8. Has anyone managed to blank out the CONTEXT_PATH? I'd much prefer the root url and not have everything prepended with /airsonic/. I've even tried editing the xml file in /boot/config/plugins/dockerMan/ while the docker was off and it still comes right back to airsonic.
  9. It seems the latest version's database files changed names and didn't update the old file names. When it started again after updating I thought I had lost everything. \\servername\appdata\binhex-libresonic\db\ All the files changed from subsonic..... to libresonic.... so subsonic.data is now libresonic.data I did have to remove the docker (without deleting image) and remake it after fixing the file names.
  10. Timing wise it started just as my nightly rsync script executed, it connects to my web servers using rsync and it mirrors the home directories into a backup share along with copies of the databases. Turns out the cache drive WAS in the array when it first went down, however after forcefully restarting the machine as it just wouldn't respond to anything the cache drive had de-selected itself from the array when the system came back up. That was when I posted here, I had forgotten the cache drive was in the array but had somehow removed itself during the reboot. I have since connected the drive to my main computer to read it and it contains the contents of that partial rsync just before going down. I formatted it and it didn't make it 16 minutes into a stress test sitting in my external case. Another Seagate down the tubes.
  11. I didn't say it's not in the system, it's not in the array. Why would a drive outside the array not being used for anything be causing the entire system to go down. I have since powered down and pulled the drive out.
  12. The hard drive SDD is not even in the array, how is it causing my server to crash? This is the 2nd time this week. Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052107 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052108 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052109 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052110 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052111 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052112 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052113 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052114 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052115 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052116 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052117 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052118 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052119 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052120 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052121 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052122 (122096638) Nov 21 18:00:05 storage kernel: REISERFS error (device sdd1): vs-4010 is_reusable: block number is out of range 3582052123 (122096638) followed by 946,635 more lines of the same error message but a different block number.
  13. Made it 32 days uptime before the web and samba crashed again. I am unable to access any shares via windows or telnet cd /mnt/user/. Oct 26 02:01:30 storage logger: mover finished Oct 26 08:12:29 storage kernel: general protection fault: 0000 [#1] PREEMPT SMP Oct 26 08:12:29 storage kernel: Modules linked in: kvm_amd kvm xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat md_mod mvsas k8temp libsas scsi_transport_sas forcedeth sata_nv pata_amd asus_atk0110 acpi_cpufreq [last unloaded: md_mod] Oct 26 08:12:29 storage kernel: CPU: 0 PID: 27905 Comm: shfs Not tainted 4.1.5-unRAID #5 Oct 26 08:12:29 storage kernel: Hardware name: System manufacturer System Product Name/M2N-E, BIOS ASUS M2N-E ACPI BIOS Revis ion 1102 09/21/2007 Oct 26 08:12:29 storage kernel: task: ffff880017ce53c0 ti: ffff880005abc000 task.ti: ffff880005abc000 Oct 26 08:12:29 storage kernel: RIP: 0010:[<ffffffff811533e4>] [<ffffffff811533e4>] __discard_prealloc+0x98/0xb3 Oct 26 08:12:29 storage kernel: RSP: 0018:ffff880005abfb68 EFLAGS: 00010246 Oct 26 08:12:29 storage kernel: RAX: ffff8800103e9e68 RBX: ffff8800103e9e40 RCX: 6411832257641b03 Oct 26 08:12:29 storage kernel: RDX: 8853cb68033c58a7 RSI: ffff8800103e9e40 RDI: ffff880005abfca8 Oct 26 08:12:29 storage kernel: RBP: ffff880005abfb98 R08: 0000000000001ad3 R09: 000000000004b971 Oct 26 08:12:29 storage kernel: R10: ffffffff00001001 R11: ffffffff81160b7d R12: ffff880005abfca8 Oct 26 08:12:29 storage kernel: R13: ffff8800103e9ee0 R14: ffff880005abfca8 R15: 0000000033218126 Oct 26 08:12:29 storage kernel: FS: 00002ba18843c700(0000) GS:ffff88007bc00000(0000) knlGS:0000000000000000 Oct 26 08:12:29 storage kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Oct 26 08:12:29 storage kernel: CR2: 00002ba186dfd000 CR3: 000000007810d000 CR4: 00000000000006f0 Oct 26 08:12:29 storage kernel: Stack: Oct 26 08:12:29 storage kernel: ffff8800750ce200 ffff880005abfca8 ffffc90000b14000 ffffc90000b341e8 Oct 26 08:12:29 storage kernel: ffff880005abfca8 ffff8800748d9800 ffff880005abfbc8 ffffffff81153463 Oct 26 08:12:29 storage kernel: ffff880005abfca8 ffff880017ce53c0 ffffc90000b14000 ffffc90000b14000 Oct 26 08:12:29 storage kernel: Call Trace: Oct 26 08:12:29 storage kernel: [<ffffffff81153463>] reiserfs_discard_all_prealloc+0x44/0x4e Oct 26 08:12:29 storage kernel: [<ffffffff8116fca4>] do_journal_end+0x4e7/0xc78 Oct 26 08:12:29 storage kernel: [<ffffffff81170994>] journal_end+0xae/0xb6 Oct 26 08:12:29 storage kernel: [<ffffffff81157208>] reiserfs_unlink+0x1de/0x23f Oct 26 08:12:29 storage kernel: [<ffffffff81105e6f>] vfs_unlink+0xc5/0x165 Oct 26 08:12:29 storage kernel: [<ffffffff81109c1f>] do_unlinkat+0x107/0x24c Oct 26 08:12:29 storage kernel: [<ffffffff8110150f>] ? SyS_newlstat+0x25/0x2e Oct 26 08:12:29 storage kernel: [<ffffffff8110a36c>] SyS_unlink+0x11/0x13 Oct 26 08:12:29 storage kernel: [<ffffffff81615c6e>] system_call_fastpath+0x12/0x71 Oct 26 08:12:29 storage kernel: Code: 1c 75 bb 0f 0b 85 c0 74 12 48 8b 93 e8 00 00 00 4c 89 ee 4c 89 e7 e8 be 6e 00 00 48 8b 4b 28 44 89 7b 1c 48 8d 43 28 48 8b 53 30 <48> 89 51 08 48 89 0a 48 89 43 28 48 89 43 30 58 5b 41 5c 41 5d Oct 26 08:12:29 storage kernel: RIP [<ffffffff811533e4>] __discard_prealloc+0x98/0xb3 Oct 26 08:12:29 storage kernel: RSP <ffff880005abfb68> Oct 26 08:12:29 storage kernel: ---[ end trace bc43e0cea6afb5a4 ]--- Oct 26 13:12:30 storage kernel: mdcmd (74): spindown 4 Oct 26 13:12:56 storage emhttp: shcmd (289): /usr/sbin/hdparm -y /dev/sda &> /dev/null Oct 26 14:00:02 storage kernel: mdcmd (75): spindown 3 The machine is still running in it's current state. I can telnet into it but that is it. Is there anyway to recover this without hard shutting down?
  14. I've always seemed to struggle with this on multiple unraid machines. I have recently moved up to v6.1.2 from 5. I decided a fresh install would be best after crashing issues and version 5 seemingly having constant permission issues. The crashing has stopped but the permissions have continued. I have 15 shares, all of them are Public. I have never setup users and all but one the machines that connect to the server are Windows based. When I reinstalled the server I also had to remap all the drives on my machines. I did so without it ever asking for credentials, it was always instantly readable. However if I create a folder on one machine almost without fail it will be invisible to other machines until newperms is run. I have run newperms on the entire server twice since updating to v6. Despite that I am constantly having to login to the server and newperms on the folder I just created. It's getting kind of tiring and old having to do this every time. Any suggestions? Does anyone else suffer from this? My co-worker doesn't at his house, however the server we have at work does suffer as well. My current ongoing solution has been to cronjob it at midnight every day.
  15. root@storage:~# newperms /mnt/user/downloads/Folder\ 5/ /mnt/user/downloads/Folder 5/ /usr/local/sbin/newperms: line 21: [: /mnt/user/downloads/Folder: binary operator expected completed, elapsed time: 00:00:00 root@storage:~# newperms /mnt/user/downloads/Folder\ 5/ /mnt/user/downloads/Folder 5/ processing /mnt/user/downloads/Folder 5/ ... chmod -R u-x,go-rwx,go+u,ugo+X /mnt/user/downloads/Folder 5/ ... chown -R nobody:users /mnt/user/downloads/Folder 5/ ... sync completed, elapsed time: 00:00:02 Wrapping $1 on line 21 seems to fix this. if [ -d $1 ] ; then if [ -d "$1" ] ; then I found this issue because despite the major change, I still constantly fight with permissions and constantly have to use newperms.