September 16, 201312 yr Not sure where to start on this one - unRAID was working fine until I tried to swap drives to a different chassis. Had issues with the build and swapped back to the original hardware. Now whenever I'm doing large transfers, seems if I'm doing more than one at a time, unRAID will disconnect from my Mac. I cannot reconnect to unRAID and the transfers just hang in limbo. I cannot reboot unRAID (it cannot unmount user shares) and I am forced to kill it with the power switch. Ideas? Where should I start?
September 16, 201312 yr Author Attack a syslog. See link in my sig. Running 5.0 Final. Current syslog attached. 2013-09-16_unraid_syslog.txt
September 16, 201312 yr Looks like an issue for Joe L. or someone similar. Somehow the partition or disk config data is whacked and will need an expert to sort it out. Suggest holding on any changes until one of the experts can guide you better. In the meantime, can you explain the disk swapping you did between chassis and what versions of unRAID were running if the other chassis was unRAID?
September 16, 201312 yr Author Check for BIOS updates for MB and SATA card. Running latest BIOS - SATA is onboard ports.
September 16, 201312 yr Author In the meantime, can you explain the disk swapping you did between chassis and what versions of unRAID were running if the other chassis was unRAID? It's a long story... I wanted to repurpose my overkill unRAID hardware (AMD x4) as a Steam Box and decided to spin up another box (AMD Barton) I had as unRAID. I took the USB key and the drives out of the AMD x4 box and put it into the AMD Barton box - powered on, confirmed the disks were in the proper locations and powered up the array; no issues. Started behaving strangely on transfers (as it is now) so I swapped back to the AMD x4 box and the issues persist. I had read about swapping hardware is supposed to be as simple as I described it above and have friends with first hand experience in swapping much larger unRAID boxes than mine to new hardware. I suspect the AMD Barton hardware is bad and caused the issue... hoping that I can recover from this.
September 16, 201312 yr Author check disk file systems for disk1, see dgaschk sig for instructions. went to stop the array to restart in maintenance mode and getting a "retry unmounting user share(s)..." loop - any way to force the shares to dismount?
September 17, 201312 yr check disk file systems for disk1, see dgaschk sig for instructions. went to stop the array to restart in maintenance mode and getting a "retry unmounting user share(s)..." loop - any way to force the shares to dismount? Telnet in and run lsof /mnt or check the 'open files' in unMenu. It should identify any open files. Having a window open of share is sometimes enough to keep from stopping so close any windows or turn off devices that are accessing it. If you have addons, do a ps -A and start killing them off, such as python.
September 17, 201312 yr Author Telnet in and run lsof /mnt or check the 'open files' in unMenu. It should identify any open files. Having a window open of share is sometimes enough to keep from stopping so close any windows or turn off devices that are accessing it. If you have addons, do a ps -A and start killing them off, such as python. Bone stock unRAID 5.0 install; no plugins. I made sure to close all windows (and mounts from my Mac). Found a thread to unmount shares including lsof and fuser -mvk, etc... nothing would allow me to unmount /dev/md1 (disk 1). Eventually after trying to kill PID the PID listed on disk 1 I started getting erros when trying to run fuser -mvk /mnt/disk1* /mnt/users*. Ended up killing power to the server and reboting (). Running reiserfsck on drive 1 now - it has found some "bad_indirect_items", but has not yet completed the scan.
September 17, 201312 yr Author disk 1 reiserfsck finished finding 9 errors which can be fixed with --fix-fixable. Going to run that now and see what I get. The support / community on this forum is amazing - thanks everyone for their help and input.
September 17, 201312 yr Author The end result for --fix-fixable is: finished No corruptions found There are on the filesystem: Leaves 180868 Internal nodes 1148 Directories 4756 Other files 7122 Data block pointers 182116419 (182412 of them are zero) Safe links 0 I'm going to run reiserfsck on disk2 to be safe. Do you think this will resolve my issues or are they deeper?
September 17, 201312 yr Author disk2 has found 26 corruptions which can be fixed with --fix-fixable. Lets see how this goes.
September 17, 201312 yr Author results from disk2 finished No corruptions found There are on the filesystem: Leaves 122881 Internal nodes 773 Directories 3927 Other files 15456 Data block pointers 122578843 (0 of them are zero) Safe links 0 Any specific thoughts as to what would have created the corruption?
September 19, 201312 yr Author I think this one might be solved. Does anyone have any idea as to what would have caused this corruption?
Archived
This topic is now archived and is closed to further replies.