Jump to content

dwoods99

Members
  • Content Count

    175
  • Joined

  • Last visited

Community Reputation

0 Neutral

About dwoods99

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed
  1. I spent the whole day yesterday running reiserfsck --check on each of the drives while in maintenance mode. All reported no corruption except for disk7 as expected. Ran reiserfsck --rebuild-tree and then reiserfsck --check again. Now it reports fine. I stopped the array and restarted in non-maintenance mode. Drive is no longer in read only mode, and I can finally access and delete files, as well as get a listing of the movie folder (which failed due to corruptions). Lesson learned... use maintenance mode when using reiserfsck Thanks for the help, it's appreciated.
  2. I updated the file memtest on the flash drive by using Version 5.01 is the same as the one on v6.2.4 install package. Ran the test for 6 hours and 0 errors after 4 cycles/passes. System came back up and tried a parity check, which was very slow. I stopped the process by stopping the array. However this means nothing mounted and so I could not use reiserfsck. I started array but now reiserfsck won't work since they are all mounted with write permissions. Do I have to stop the array and mount the drive manually as read only? What's the best way if I want to do a --check on each of the 11 drives?
  3. Just found in the upgrade help to move from v5 to v6 this command # grep --color lm /proc/cpuinfo flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx lm constant_tsc up arch_perfmon pebs bts aperfmperf pni dtes64 monitor ds_cpl tm2 ssse3 cx16 xtpr pdcm lahf_lm dtherm which implies that my cpu is NOT 64 bit capable and hence why I couldn't get the USB stick to work. My other server shows the required "lm" expected in the cpuinfo output # grep --color lm /proc/cpuinfo flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc nonstop_tsc extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt arat hw_pstate npt lbrv svm_lock nrip_save pausefilter Just posting as a final update in case others find this search thread.
  4. New problem on server running 5.0rc8. Searching didn't provide new ideas to try. I had a failed drive on disk 7. Replaced it with a larger drive, rebuilt from parity. It all seemed fine except it later came up in read only mode after a reboot. I ran reiserfsck --check /dev/md7 and it reported corruption and suggested using --rebuild-tree After doing that, it finished ok but another --check reported more errors and in read only mode. I even attempted a umount /dev/md7 followed by mount /dev/mnt7 /mnt/disk7 to force it. Now I can't seem to be able to access the contents of the sub-folder Movies/1960-1979/ I can cd into it but trying any ls command just hangs there (even a simple ls A*) Therefore I am not able to copy those movies onto other disks for backup before more aggressive rebuild attempts. What else can I try besides a --rebuild-sb as a last resort? root@Moat:/boot/config# reiserfsck --check /dev/md7 reiserfsck 3.6.21 (2009 www.namesys.com) ... Will read-only check consistency of the filesystem on /dev/md7 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Thu Jan 19 23:00:07 2017 ########### Filesystem seems mounted read-only. Skipping journal replay. Checking internal tree.. \/ 1 (of 18|/ 1 (of 143// 2 (of 168\bad_path: block 155484162, pointer 1: The used space (4048) of the child block (256545669) is not equal to the (blocksize (4096) - free space (96) - header size (24)) / 24 (of 168/bad_path: The left delimiting key [2 5 0x46109280 DIR (3)] of the node (32810) must be equal to the first element's key [2 167 0x21c001 IND (1)] within the node. / 25 (of 168-bad_path: The left delimiting key [2 5 0x477cab80 DIR (3)] of the node (131088563) must be equal to the first element's key [2 5 0x46109280 DIR (3)] within the node. / 55 (of 168|bad_path: block 155484162, pointer 54: The used space (4068) of the child block (32776) is not equal to the (blocksize (4096) - free space (0) - header size (24)) /106 (of 168\bad_path: block 155484162, pointer 105: The used space (2712) of the child block (32846) is not equal to the (blocksize (4096) - free space (1220) - header size (24)) / 7 (of 18\/118 (of 170\block 149955: The level of the node (3) is not correct, (2) expected the problem in the internal node occured (149955), whole subtree is skipped finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 3 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Thu Jan 19 23:05:02 2017 ########### root@Moat:/boot/config# reiserfsck --rebuild-tree /dev/md7 reiserfsck 3.6.21 (2009 www.namesys.com) ... Will rebuild the filesystem (/dev/md7) tree Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes Filesystem seems mounted read-only. Skipping journal replay. ########### reiserfsck --rebuild-tree started at Fri Jan 20 01:28:15 2017 ########### Pass 0: ####### Pass 0 ####### Loading on-disk bitmap .. ok, 485191348 blocks marked used Skipping 30567 blocks (super block, journal, bitmaps) 485160781 blocks will be read 0%.. left 0, 32372 /sec 1875 directory entries were hashed with "r5" hash. "r5" hash is selected Flushing..finished Read blocks (but not data blocks) 485160781 Leaves among those 480167 Objectids found 1878 Pass 1 (will try to insert 480167 leaves): ####### Pass 1 ####### Looking for allocable blocks .. finished 0%....20%....40%....60%....80%....100% left 0, 2652 /sec Flushing..finished 480167 leaves read 480166 inserted 1 not inserted ####### Pass 2 ####### Pass 2: 0%....20%....40%....60%....80%....100% left 0, 1 /sec Flushing..finished Leaves inserted item by item 1 Pass 3 (semantic): ####### Pass 3 ######### /Movies/1960-1979vpf-10650: The directory [2 5] has the wrong size in the StatData (139016) - corrected to (138944) Flushing..finished Files found: 1870 Directories found: 7 Pass 3a (looking for lost dir/files): ####### Pass 3a (lost+found pass) ######### Looking for lost directories: Flushing..finished5, 747 /sec Empty lost dirs removed 1 Pass 4 - finisheddone 463088, 506 /sec Deleted unreachable items 2 Flushing..finished The partition is mounted ro. It is better to umount and mount it again. Syncing..finished ########### reiserfsck finished at Fri Jan 20 06:06:09 2017 ########### root@Moat:/# umount /dev/md7 root@Moat:/# mount /dev/md7 /mnt/disk7 root@Moat:~# reiserfsck --check /dev/md7 reiserfsck 3.6.21 (2009 www.namesys.com) ... Will read-only check consistency of the filesystem on /dev/md7 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Fri Jan 20 15:22:01 2017 ########### Filesystem seems mounted read-only. Skipping journal replay. Checking internal tree.. \/ 1 (of 18|/ 1 (of 143// 2 (of 168\bad_path: block 155484162, pointer 1: The used space (4048) of the child block (256545669) is not equal to the (blocksize (4096) - free space (96) - header size (24)) / 24 (of 168/bad_path: The left delimiting key [2 5 0x46109280 DIR (3)] of the node (32810) must be equal to the first element's key [2 167 0x21c001 IND (1)] within the node. / 25 (of 168-bad_path: The left delimiting key [2 5 0x477cab80 DIR (3)] of the node (131088563) must be equal to the first element's key [2 5 0x46109280 DIR (3)] within the node. / 55 (of 168|bad_path: block 155484162, pointer 54: The used space (4068) of the child block (32776) is not equal to the (blocksize (4096) - free space (0) - header size (24)) /106 (of 168\bad_stat_data: The objectid (1437) is marked free, but used by an object [2 1437 0x0 SD (0)] bad_path: block 155484162, pointer 105: The used space (2712) of the child block (32846) is not equal to the (blocksize (4096) - free space (1220) - header size (24)) / 7 (of 18\/118 (of 170\block 149955: The level of the node (3) is not correct, (2) expected the problem in the internal node occured (149955), whole subtree is skipped finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 3 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Fri Jan 20 15:26:24 2017 ########### root@Moat:~# root@Moat:~# tail -333 /var/log/syslog Jan 20 04:40:02 Moat syslogd 1.4.1: restart. Jan 20 07:06:13 Moat kernel: mdcmd (169): spindown 0 Jan 20 07:06:13 Moat kernel: mdcmd (170): spindown 7 Jan 20 15:19:34 Moat kernel: REISERFS (device md7): found reiserfs format "3.6" with standard journal Jan 20 15:19:34 Moat kernel: REISERFS (device md7): using ordered data mode Jan 20 15:19:34 Moat kernel: reiserfs: using flush barriers Jan 20 15:19:34 Moat kernel: REISERFS (device md7): journal params: device md7, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 Jan 20 15:19:34 Moat kernel: REISERFS (device md7): checking transaction log (md7) Jan 20 15:19:34 Moat kernel: REISERFS (device md7): replayed 3 transactions in 0 seconds Jan 20 15:19:34 Moat kernel: REISERFS (device md7): Using r5 hash to sort names Jan 20 15:19:54 Moat kernel: REISERFS error (device md7): vs-7000 search_by_entry_key: search_by_key returned item position == 0 Jan 20 15:19:54 Moat kernel: REISERFS (device md7): Remounting filesystem read-only Jan 20 15:19:54 Moat kernel: REISERFS error (device md7): vs-7000 search_by_entry_key: search_by_key returned item position == 0 Jan 20 15:20:25 Moat last message repeated 192379 times Jan 20 15:21:24 Moat last message repeated 378685 times root@Moat:~# root@Moat:~# reiserfsck --check /dev/md7 reiserfsck 3.6.21 (2009 www.namesys.com) ... Will read-only check consistency of the filesystem on /dev/md7 Will put log info to 'stdout' Do you want to run this program?[N/Yes] (note need to type Yes if you do):Yes ########### reiserfsck --check started at Fri Jan 20 15:22:01 2017 ########### Filesystem seems mounted read-only. Skipping journal replay. Checking internal tree.. \/ 1 (of 18|/ 1 (of 143// 2 (of 168\bad_path: block 155484162, pointer 1: The used space (4048) of the child block (256545669) is not equal to the (blocksize (4096) - free space (96) - header size (24)) / 24 (of 168/bad_path: The left delimiting key [2 5 0x46109280 DIR (3)] of the node (32810) must be equal to the first element's key [2 167 0x21c001 IND (1)] within the node. / 25 (of 168-bad_path: The left delimiting key [2 5 0x477cab80 DIR (3)] of the node (131088563) must be equal to the first element's key [2 5 0x46109280 DIR (3)] within the node. / 55 (of 168|bad_path: block 155484162, pointer 54: The used space (4068) of the child block (32776) is not equal to the (blocksize (4096) - free space (0) - header size (24)) /106 (of 168\bad_stat_data: The objectid (1437) is marked free, but used by an object [2 1437 0x0 SD (0)] bad_path: block 155484162, pointer 105: The used space (2712) of the child block (32846) is not equal to the (blocksize (4096) - free space (1220) - header size (24)) / 7 (of 18\/118 (of 170\block 149955: The level of the node (3) is not correct, (2) expected the problem in the internal node occured (149955), whole subtree is skipped finished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 3 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Fri Jan 20 15:26:24 2017 ########### root@Moat:~#
  5. Thanks for the help and detailed response. Appreciate that you were able to pinpoint ata4 as sdc. DUe to replacing the Big Boy fan on my antec case, and hard to reach screw, I most likely loosened a power cable on the sata enclusures or bumped sata cable connections. I also made sure to better secure the controller card. Once I checked and did all this, I was able to reboot and re-start the parity check. After initial startup, I started seeing normal speeds. After array parity was done, I ran a SMARTshort test on sdc and it came back fine (and no more syslog errors). I'll simply monitor it for now. I was not able to get v6 booting up on my other server (recent thread), but at some point I'll try it on this server (different motherboard).
  6. Finally! Success. Went back to basics using 2GB. Re-formatted, copied virgin 5.0rc8 files, copied my ident.cfg and network.cfg files, ran makebootable as Administrator (right-click on file and select option from drop down menu). Made sure label of USB still set to UNRAID... this was something I found tonight that a refresh of the Win7 drive list showed the label as back to blank -- even though it was clearly in format option. My server FINALLY booted back into UNRAID menu. Back to PC to add more files back (Pro1.key, passwd, shadow, disk.cfg, smb-extra.conf, smbpasswd, share.cfg, shares/ folder), , reboot worked again but of course UNRAID Basic mode (wrong USB for my Pro1.key). Now try registered USB key with back to basic files. Didn't work. Back to PC to run makebootable AGAIN, make sure UNRAID label. Worked.. finally. Now I could grab files from backup v5 USB contents and add back. Run makebootable once again for safe measure. System back up with all the v5 plugins. Only problem was the disks were no longer listed and I had to manually select them in their proper slot. Started array with box checked for "Parity is correct". Side note: even with no added files to v6 installed on a new 16GB Samsung USB, it would not boot on this server, however it boots fine on an old PC (ASUS PB5-E)... so this server will NOT be getting any more attempts to upgrade to v6.
  7. I've attached the full syslog from bootup tonight. Came back up ok and did not require a parity check. Checked last disk that was rebuilt and short test passed. Looking at the end of the syslog before shutdown last night I see these, and I notice /dev/sde reports something, which may coincide with ata4 errors found at end of attached syslog (repeating errors). Jan 16 23:25:14 Moat status[22654]: SMART overall health assessment Jan 16 23:25:15 Moat status[22654]: /dev/sda: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:15 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:15 Moat status[22654]: SMART overall-health self-assessment test result: PASSED Jan 16 23:25:15 Moat status[22654]: /dev/sdb: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:15 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:15 Moat status[22654]: SMART overall-health self-assessment test result: PASSED Jan 16 23:25:15 Moat status[22654]: /dev/sdc: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:15 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:15 Moat status[22654]: SMART overall-health self-assessment test result: PASSED Jan 16 23:25:15 Moat status[22654]: /dev/sdd: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:15 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:15 Moat status[22654]: SMART overall-health self-assessment test result: PASSED Jan 16 23:25:15 Moat status[22654]: /dev/sde: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:15 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:15 Moat status[22654]: /dev/sde: Unknown USB bridge [0x0781:0x5530 (0x103)] Jan 16 23:25:15 Moat status[22654]: Smartctl: please specify device type with the -d option. Jan 16 23:25:15 Moat status[22654]: Use smartctl -h to get a usage summary Jan 16 23:25:15 Moat status[22654]: /dev/sdf: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:15 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:15 Moat status[22654]: SMART overall-health self-assessment test result: PASSED Jan 16 23:25:15 Moat status[22654]: /dev/sdg: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:15 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:15 Moat status[22654]: SMART overall-health self-assessment test result: PASSED Jan 16 23:25:15 Moat status[22654]: /dev/sdh: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:15 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:15 Moat status[22654]: SMART overall-health self-assessment test result: PASSED Jan 16 23:25:16 Moat status[22654]: /dev/sdi: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:16 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:16 Moat status[22654]: SMART overall-health self-assessment test result: PASSED Jan 16 23:25:16 Moat status[22654]: /dev/sdj: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:16 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:16 Moat status[22654]: SMART overall-health self-assessment test result: PASSED Jan 16 23:25:16 Moat status[22654]: /dev/sdk: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:16 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:16 Moat status[22654]: SMART overall-health self-assessment test result: PASSED Jan 16 23:25:16 Moat status[22654]: /dev/sdl: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:16 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:16 Moat status[22654]: SMART overall-health self-assessment test result: PASSED Jan 16 23:25:16 Moat status[22654]: /dev/sdm: smartctl 5.40 2010-10-16 r3189 [i486-slackware-linux-gnu] (local build) Jan 16 23:25:16 Moat status[22654]: Copyright (C) 2002-10 by Bruce Allen, http://smartmontools.sourceforge.net Jan 16 23:25:16 Moat status[22654]: SMART overall-health self-assessment test result: PASSED The parity check is now currently down to 11 hrs on a 3TB drive, running at 79 MB/s This is good now except for the ata4 errors. I suspect the sata multiplier card was loose, or sata connections. I use 4 out 5 sata on motherboard plus 8 on the multiplier. syslog-20170117.txt
  8. Correct, both cause server to reboot and I never see an UNRAID menu. Original licensed USB is 8 GB and I tried 2GB for the second one. Removed all hardware like network card, SATA port multiplier, even the fans. Also all RAM and computer beeped as expected, removed 1 of 2 RAM which BIOS complained about but continued to boot. In all cases, the system kept rebooting after the BIOS, never getting to UNRAID (at least not visually). Other than both chassis fan ports appear dead (CPU fan port ok), all connections are solid. I have nothing left than to get a new motherboard/cpu (or replacement). I'm out of trouble shooting ideas.
  9. Yes, probably Core 2 E4400. It's been a long time Something is stopping the boot process. Still unsure if it's hardware or UNRAID. I wasn't able to find BIOS option to allow me to see the boot up sequence. Using TAB gave minimal output. I did try F10 to pick which to boot from but no change.
  10. Still getting the same messages in syslog. Web access to server Main page from my PC is also painfully slow. Any recommendations?
  11. It's a 4400 Celeron D 2.0 Ghz However UNRAID 5 was working fine before and now the USB with v5 put back on still won't boot to UNRAID.
  12. Couldn't find an answer in posts. I'm running a second server with 5.0.rc8a containing 2 and 3 TB drives. One disk was bad so I replaced it, did the rebuild and it all seemed fine. However later realized the drive was kept in read only mode. I ran reisferfsck --check and later with --rebuild-tree, ran --check again. Looked like it was fixed but still kept the drive in read only mode, even after an array stop and re-start, including a reboot. Did a second --rebuild-tree after --check indicated a problem. After this the server wanted to do an array parity check... which is now painfully slow (take 30 days to finish). Looking at the current syslog indicates another problem but I don't believe it's the same drive. Jan 15 23:34:38 Moat kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 15 23:34:38 Moat kernel: ata4.00: configured for UDMA/33 Jan 15 23:34:38 Moat kernel: ata4: EH complete Jan 15 23:34:39 Moat kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen Jan 15 23:34:39 Moat kernel: ata4.00: irq_stat 0x00400000, PHY RDY changed Jan 15 23:34:39 Moat kernel: ata4: SError: { Persist PHYRdyChg } Jan 15 23:34:39 Moat kernel: ata4.00: failed command: READ DMA EXT Jan 15 23:34:39 Moat kernel: ata4.00: cmd 25/00:00:f0:74:a9/00:04:02:00:00/e0 tag 0 dma 524288 in Jan 15 23:34:39 Moat kernel: res 50/00:00:ef:74:a9/00:00:02:00:00/e0 Emask 0x10 (ATA bus error) Jan 15 23:34:39 Moat kernel: ata4.00: status: { DRDY } Jan 15 23:34:39 Moat kernel: ata4: hard resetting link Jan 15 23:34:46 Moat kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 15 23:34:46 Moat kernel: ata4.00: configured for UDMA/33 Jan 15 23:34:46 Moat kernel: ata4: EH complete Jan 15 23:34:46 Moat kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen Jan 15 23:34:46 Moat kernel: ata4.00: irq_stat 0x00400000, PHY RDY changed Jan 15 23:34:46 Moat kernel: ata4: SError: { Persist PHYRdyChg } Jan 15 23:34:46 Moat kernel: ata4.00: failed command: READ DMA EXT Jan 15 23:34:46 Moat kernel: ata4.00: cmd 25/00:00:50:b6:a9/00:04:02:00:00/e0 tag 0 dma 524288 in Jan 15 23:34:46 Moat kernel: res 50/00:00:4f:b6:a9/00:00:02:00:00/e0 Emask 0x10 (ATA bus error) Jan 15 23:34:46 Moat kernel: ata4.00: status: { DRDY } Jan 15 23:34:46 Moat kernel: ata4: hard resetting link Jan 15 23:34:53 Moat kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 15 23:34:54 Moat kernel: ata4.00: configured for UDMA/33 Jan 15 23:34:54 Moat kernel: ata4: EH complete Jan 15 23:34:54 Moat kernel: ata4.00: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen Jan 15 23:34:54 Moat kernel: ata4.00: irq_stat 0x00400000, PHY RDY changed Jan 15 23:34:54 Moat kernel: ata4: SError: { Persist PHYRdyChg } Jan 15 23:34:54 Moat kernel: ata4.00: failed command: READ DMA EXT Jan 15 23:34:54 Moat kernel: ata4.00: cmd 25/00:00:60:fa:a9/00:04:02:00:00/e0 tag 0 dma 524288 in Jan 15 23:34:54 Moat kernel: res 50/00:00:5f:fa:a9/00:00:02:00:00/e0 Emask 0x10 (ATA bus error) Jan 15 23:34:54 Moat kernel: ata4.00: status: { DRDY } Jan 15 23:34:54 Moat kernel: ata4: hard resetting link Jan 15 23:35:01 Moat kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 15 23:35:01 Moat kernel: ata4.00: configured for UDMA/33 Jan 15 23:35:01 Moat kernel: ata4: EH complete Jan 15 23:35:01 Moat kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen Jan 15 23:35:01 Moat kernel: ata4: irq_stat 0x00400000, PHY RDY changed Jan 15 23:35:01 Moat kernel: ata4: SError: { Persist PHYRdyChg } Jan 15 23:35:01 Moat kernel: ata4: hard resetting link Jan 15 23:35:09 Moat kernel: ata4: SATA link up 1.5 Gbps (SStatus 113 SControl 310) Jan 15 23:35:09 Moat kernel: ata4.00: configured for UDMA/33 Jan 15 23:35:09 Moat kernel: ata4: EH complete Jan 15 23:35:09 Moat kernel: ata4: exception Emask 0x10 SAct 0x0 SErr 0x10200 action 0xe frozen Jan 15 23:35:09 Moat kernel: ata4: irq_stat 0x00400000, PHY RDY changed Jan 15 23:35:09 Moat kernel: ata4: SError: { Persist PHYRdyChg } Jan 15 23:35:09 Moat kernel: ata4: hard resetting link Is this indicating a disk problem or a SATA cable connection to the sata port 4 (or 5 if 0-4)? I had to change the 200mm Big Boy fan on the Antec 900 case, so I'm thinking something came loose after flipping it on its' side. EDIT: Solved - loose sata cables or power to the sata enclosures. Possibly loose sata controller card.
  13. Yes, except didn't realize (never made clear in notes) you had to run make_bootable after you install a version, like going back from v6 to v5. This was causing the failed menu.c32 messages. Now I have a second USB installed with v5 and booting on a second PC. Got the original USB booting into UNRAID menu on second PC but NOT the original server. On server, either USB used, now instead of hanging while booting and never showing UNRAID menu, it is trying to load but causes the server to reboot repeatedly. Tomorrow I will start removing hardware and reboot from bare bones to see if that works, and then slowly add hardware back until boot fails again to pinpoint the cause.
  14. Good question... I don't know. I was wrong about motherboard, it's an Intel DG31PR but I can't find info about 64 bit O/S at http://www.intel.com/content/www/us/en/support/boards-and-kits/desktop-boards/legacy-intel-desktop-boards/intel-desktop-board-dg31pr.html I will try to get another usb installed with UNRAID v5 and boot with that. EDIT: I re-installed 5.0rc8 from zip back onto USB stick updating only important config/*.cfg files and booted using other PC which booted for v6. I get UNRAID error "Failed to load COM32 file menu.c32" although it does exist and is located in root of flash drive.