twg

Members
  • Posts

    126
  • Joined

  • Last visited

Everything posted by twg

  1. no one here use Unraid with Sonos ?
  2. Didn’t find much via search so here goes. Unraid generally has been solid and I haven’t looked at it in a long while besides keeping it up dated to latest version. for awhile I noticed my Sonos could not connect to my music share on unraid. I finally did some googling today and it seems sonos will only connect to nas via SMB1. I’ve got Netbios enabled which I believe is SMB1 and also wsd enabled too. I have “min protocol=SMB1” in the smb-conf file. yet I still cannot have Sonos find my music share. It used to work and not sure when it stopped working, must have been an upgrade or something. anyone with suggestions ?
  3. I had a similar problem trying to upgrade to 6.8.1, I only have 1 network interface so no bonding or anything. I reverted back and just recently tried 6.8.3 and still not working. I had to set my network to static in order for it to work.
  4. I am seeing the same problem, so not fixed yet
  5. There's a problem with 6.8.0. I'm running 6.7.2 with no issues and everytime I update to 6.8.0 the server can't get an IP address. When I revert to 6.7.2 the problem goes away. I tried twice already. Same behaviour.
  6. Brand new, I took it out of the box and tested it once. Paid $180, selling for $150.
  7. so for whatever reason my 6 yr old AOC-SAS2LP cards that used to work are now exhibiting the dropped drive issue, even the brand new replacement spare AOC-SAS card I had... I recently upgraded from 6.3.5 to latest 6.6.2 Unraid so maybe the newer kernels are more finicky with that controller... I went out and bought a LSI 9260-16i... now i'm reading that this card can't be flashed to IT mode... just my bad luck. Before I try to sell this card to recoup my losses, does anyone have anything I can try to get this card to work ? I've read that I can use megacli to force the drives connected to raid0, thereby creating a whole array of raid0 drives, but I don't want to do that beacuse it messes up the drive identifiers and so if a drive goes bad it becomes a problem replacing disks... not to mention I've got an existing array that I don't want to screw up.
  8. Hmm, I just purchased a LSI MegaRAID 9260-16i to replace my AOC-SAS2LP cards which started exhibiting the dropped disk problem... Unraid doesn't see the drives connected to the 9260... googling reveals there isn't an IT mode on the card... how did you get your 9260 working ?
  9. I put a new drive in to replace the failed parity drive and it finished rebuilding the parity drive. I decided to buy another parity and put 2 parity drives to cover myself... and within 2 hours of adding the 2nd parity drive, another one of my disk redballed. The relevent part of the log shows similar errors: Oct 20 14:21:48 Tower emhttpd: shcmd (217): echo 128 > /sys/block/sdp/queue/nr_requests Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#0 CDB: opcode=0x88 88 00 00 00 00 00 82 30 e8 10 00 00 02 f8 00 00 Oct 20 18:09:01 Tower kernel: print_req_error: I/O error, dev sdp, sector 2184243216 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#1 CDB: opcode=0x88 88 00 00 00 00 00 82 30 e6 d0 00 00 01 40 00 00 Oct 20 18:09:01 Tower kernel: print_req_error: I/O error, dev sdp, sector 2184242896 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#2 CDB: opcode=0x88 88 00 00 00 00 00 82 30 e2 d0 00 00 04 00 00 00 Oct 20 18:09:01 Tower kernel: print_req_error: I/O error, dev sdp, sector 2184241872 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#3 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#3 CDB: opcode=0x88 88 00 00 00 00 00 82 30 e1 90 00 00 01 40 00 00 Oct 20 18:09:01 Tower kernel: print_req_error: I/O error, dev sdp, sector 2184241552 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#4 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#4 CDB: opcode=0x88 88 00 00 00 00 00 82 30 dd 90 00 00 04 00 00 00 Oct 20 18:09:01 Tower kernel: print_req_error: I/O error, dev sdp, sector 2184240528 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#5 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#5 CDB: opcode=0x88 88 00 00 00 00 00 82 30 dc 50 00 00 01 40 00 00 Oct 20 18:09:01 Tower kernel: print_req_error: I/O error, dev sdp, sector 2184240208 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#6 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#6 CDB: opcode=0x88 88 00 00 00 00 00 82 30 d8 50 00 00 04 00 00 00 Oct 20 18:09:01 Tower kernel: print_req_error: I/O error, dev sdp, sector 2184239184 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#7 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#7 CDB: opcode=0x88 88 00 00 00 00 00 82 30 d7 08 00 00 01 48 00 00 Oct 20 18:09:01 Tower kernel: print_req_error: I/O error, dev sdp, sector 2184238856 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#8 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#8 CDB: opcode=0x88 88 00 00 00 00 00 82 30 d3 08 00 00 04 00 00 00 Oct 20 18:09:01 Tower kernel: print_req_error: I/O error, dev sdp, sector 2184237832 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#9 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] tag#9 CDB: opcode=0x88 88 00 00 00 00 00 82 30 cf 08 00 00 04 00 00 00 Oct 20 18:09:01 Tower kernel: print_req_error: I/O error, dev sdp, sector 2184236808 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] Read Capacity(16) failed: Result: hostbyte=0x04 driverbyte=0x00 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] Sense not available. Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] Read Capacity(10) failed: Result: hostbyte=0x04 driverbyte=0x00 Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] Sense not available. Oct 20 18:09:01 Tower kernel: sd 13:0:5:0: [sdp] 0 512-byte logical blocks: (0 B/0 B) I'm beginning to think the chances of 3 of my drives failing all within 1-2 days is too coincidental... there must be something else going on... I've attached the output of my diagnostics tower-diagnostics-20181020-1829.zip
  10. I recently had a data drive quit on me, at least Unraid said so, so I replaced it and it went thru a data rebuild. In the process, the server froze, so I rebooted it. It completed rebuilding the data drive and when it finished, I saw the following message: Event: Unraid Parity sync / Data rebuild Subject: Notice [TOWER] - Parity sync / Data rebuild finished (11640829 errors) Description: Duration: 1 day, 6 minutes, 23 seconds. Average speed: 92.2 MB/s Importance: warning What does it mean when it lists all those errors, are those errors in the drive rebuild ? ie. there's bad data ? When I check the drive log, I get a whole bunch of these: Oct 18 20:45:35 Tower kernel: sd 13:0:5:0: [sdo] tag#0 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 18 20:45:35 Tower kernel: sd 13:0:5:0: [sdo] tag#0 CDB: opcode=0x88 88 00 00 00 00 03 9d f4 24 a0 00 00 02 00 00 00 Oct 18 20:45:35 Tower kernel: print_req_error: I/O error, dev sdo, sector 15534924960 Oct 18 20:45:35 Tower kernel: sd 13:0:5:0: [sdo] tag#1 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 18 20:45:35 Tower kernel: sd 13:0:5:0: [sdo] tag#1 CDB: opcode=0x88 88 00 00 00 00 03 9d f4 26 a0 00 00 02 00 00 00 Oct 18 20:45:35 Tower kernel: print_req_error: I/O error, dev sdo, sector 15534925472 Oct 18 20:45:35 Tower kernel: sd 13:0:5:0: [sdo] tag#2 UNKNOWN(0x2003) Result: hostbyte=0x04 driverbyte=0x00 Oct 18 20:45:35 Tower kernel: sd 13:0:5:0: [sdo] tag#2 CDB: opcode=0x88 88 00 00 00 00 03 9d f4 28 a0 00 00 02 00 00 00 Oct 18 20:45:35 Tower kernel: print_req_error: I/O error, dev sdo, sector 15534925984 I've attached the full drive log. So I was getting some really weird issues, multiple drives would drop out on me, different drives everytime I reboot... open my server, seemed like some power cables were loose, so I replugged those in... still multiple drives failing on me, it seems like it's coming from one drive controller, the AOC-SASLP-MV8 controller... luckily I had a spare AOC-SAS2LP-MV8 controller, so I plugged that in... I see almost all of my drives... except my parity drive is not listed... I hear a drive struggling to seek properly, and sure enough it's my parity drive... it seems my parity drive has died... Now I'm not sure what to do... did my original data drive rebuild properly ? considering the errors I got ? I still have the failed data drive... suggestions ? I have a spare drive I can replace the parity drive but hesitant to do anything at this point that may be permanent and damage my data... help!!
  11. i may have another problem which caused this, I noticed my nightly rsync's were failing... and it seems like a mount command is now not working properly ever since I upgraded to latest ver of Unraid, so likely the command mount has probably some new behaviour which is breaking things... it's filling up my rootfs as a result and probably freezing my system... will go for dig and post another thread
  12. thanks, I rebooted and the data rebuild re-started again from 0%... all seems to be going well right now 43% with another 13hrs to go
  13. I was running 6.3.5 for the longest time and recently upgraded to 6.6.1. I followed all the instructions and everything seems to have gone smoothly. Well recently one of my drives went offline. I shutdown Unraid, pulled the bad drive and put in a new drive, restarted Unraid, stopped the array and added the new drive to the array, re-started the array. At this point, Unraid started to recreate my damaged drive (one of the data drives). The next morning, I noticed I couldn't access my Unraid server, no web interface, no telnet, not even the console. I mean the num caps key on my keyboard connected to the Unraid server wasn't even toggling when I pushed it, so it seems the Unraid server is completely frozen. I'm hesitant to shutdown/reboot, but is that my only option right now ? What happens when I reboot, will it resume restoring data from where it left off/crashed ?
  14. is there a way to preserve the directory timestamps ?
  15. I'm getting an exit status 23 with nothing happening... i'm trying to move files from disk 3 to disk 12. I've run the docker safe new permissions script... This is the command: MOVE: Move command (rsync -avRX --partial "Console/Security Camera" "/mnt/disk12/") was interrupted: exit status 23 When I run the rsync manually, I realized I had to change the current dir to /mnt/disk3 but the rsync command actually worked... not sure what the unbalance plugin error could be caused by
  16. well the rebuild completed, not sure why SMB didn't start previously... so I rebooted unRaid and it came up all good... I don't even see the disk24 error anymore... weird... i guess I'll label this case closed
  17. Yes, disk 11 is highest. I only have enough bays for 16 drives hence was confused about the disk24 mount reference. I'm using unRaid 5.0.3 I think. It says the rebuild is happening but oddly I can't access my shares, smb doesn't seem to be running. I have a few other warnings in log above relating to mounting cache drive and such, I have been ignoring it since everything seems to be working but is there something fishy?
  18. well, it looks like it just needed some time... it finished mounting the rest of my disks and now rebuilding the drive... weird... is the disk24 mount error anything to be concerned about though ? Mar 24 22:05:24 Tower emhttp: resized: /mnt/disk5 (Other emhttp) Mar 24 22:05:24 Tower emhttp: shcmd (103): mkdir /mnt/disk6 (Routine) Mar 24 22:05:24 Tower emhttp: shcmd (104): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md6 /mnt/disk6 |$stuff$ logger (Other emhttp) Mar 24 22:05:24 Tower kernel: REISERFS (device md6): found reiserfs format "3.6" with standard journal (Routine) Mar 24 22:05:24 Tower kernel: REISERFS (device md6): using ordered data mode (Routine) Mar 24 22:05:24 Tower kernel: reiserfs: using flush barriers Mar 24 22:05:24 Tower kernel: REISERFS (device md6): journal params: device md6, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine) Mar 24 22:05:24 Tower kernel: REISERFS (device md6): checking transaction log (md6) (Routine) Mar 24 22:05:24 Tower kernel: REISERFS (device md6): Using r5 hash to sort names (Routine) Mar 24 22:05:24 Tower emhttp: shcmd (105): mkdir /mnt/disk7 (Routine) Mar 24 22:05:24 Tower emhttp: shcmd (106): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md7 /mnt/disk7 |$stuff$ logger (Other emhttp) Mar 24 22:05:24 Tower kernel: REISERFS (device md7): found reiserfs format "3.6" with standard journal (Routine) Mar 24 22:05:24 Tower kernel: REISERFS (device md7): using ordered data mode (Routine) Mar 24 22:05:24 Tower kernel: reiserfs: using flush barriers Mar 24 22:05:24 Tower 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 (Routine) Mar 24 22:05:24 Tower kernel: REISERFS (device md7): checking transaction log (md7) (Routine) Mar 24 22:05:24 Tower kernel: REISERFS (device md7): Using r5 hash to sort names (Routine) Mar 24 22:05:24 Tower emhttp: shcmd (107): mkdir /mnt/disk8 (Routine) Mar 24 22:05:24 Tower emhttp: shcmd (108): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md8 /mnt/disk8 |$stuff$ logger (Other emhttp) Mar 24 22:05:24 Tower kernel: REISERFS (device md8): found reiserfs format "3.6" with standard journal (Routine) Mar 24 22:05:24 Tower kernel: REISERFS (device md8): using ordered data mode (Routine) Mar 24 22:05:24 Tower kernel: reiserfs: using flush barriers Mar 24 22:05:24 Tower kernel: REISERFS (device md8): journal params: device md8, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine) Mar 24 22:05:24 Tower kernel: REISERFS (device md8): checking transaction log (md8) (Routine) Mar 24 22:05:24 Tower kernel: REISERFS (device md8): Using r5 hash to sort names (Routine) Mar 24 22:05:24 Tower emhttp: shcmd (109): mkdir /mnt/disk9 (Routine) Mar 24 22:05:24 Tower emhttp: shcmd (110): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md9 /mnt/disk9 |$stuff$ logger (Other emhttp) Mar 24 22:05:24 Tower kernel: REISERFS (device md9): found reiserfs format "3.6" with standard journal (Routine) Mar 24 22:05:24 Tower kernel: REISERFS (device md9): using ordered data mode (Routine) Mar 24 22:05:24 Tower kernel: reiserfs: using flush barriers Mar 24 22:05:24 Tower kernel: REISERFS (device md9): journal params: device md9, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine) Mar 24 22:05:24 Tower kernel: REISERFS (device md9): checking transaction log (md9) (Routine) Mar 24 22:05:24 Tower kernel: REISERFS (device md9): Using r5 hash to sort names (Routine) Mar 24 22:05:25 Tower emhttp: shcmd (111): mkdir /mnt/disk10 (Routine) Mar 24 22:05:25 Tower emhttp: shcmd (112): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md10 /mnt/disk10 |$stuff$ logger (Other emhttp) Mar 24 22:05:25 Tower kernel: REISERFS (device md10): found reiserfs format "3.6" with standard journal (Routine) Mar 24 22:05:25 Tower kernel: REISERFS (device md10): using ordered data mode (Routine) Mar 24 22:05:25 Tower kernel: reiserfs: using flush barriers Mar 24 22:05:25 Tower kernel: REISERFS (device md10): journal params: device md10, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine) Mar 24 22:05:25 Tower kernel: REISERFS (device md10): checking transaction log (md10) (Routine) Mar 24 22:05:25 Tower kernel: REISERFS (device md10): Using r5 hash to sort names (Routine) Mar 24 22:05:25 Tower emhttp: shcmd (113): mkdir /mnt/disk11 (Routine) Mar 24 22:05:25 Tower emhttp: shcmd (114): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md11 /mnt/disk11 |$stuff$ logger (Other emhttp) Mar 24 22:05:25 Tower kernel: REISERFS (device md11): found reiserfs format "3.6" with standard journal (Routine) Mar 24 22:05:25 Tower kernel: REISERFS (device md11): using ordered data mode (Routine) Mar 24 22:05:25 Tower kernel: reiserfs: using flush barriers Mar 24 22:05:25 Tower kernel: REISERFS (device md11): journal params: device md11, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine) Mar 24 22:05:25 Tower kernel: REISERFS (device md11): checking transaction log (md11) (Routine) Mar 24 22:05:25 Tower kernel: REISERFS (device md11): Using r5 hash to sort names (Routine) Mar 24 22:05:25 Tower emhttp: shcmd (115): mkdir /mnt/cache (Other emhttp) Mar 24 22:05:25 Tower emhttp: _shcmd: shcmd (115): exit status: 1 (Other emhttp) Mar 24 22:05:25 Tower emhttp: shcmd (116): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/sdb1 /mnt/cache |$stuff$ logger (Drive related) Mar 24 22:05:25 Tower logger: mount: /dev/sdb1 already mounted or /mnt/cache busy (Drive related) Mar 24 22:05:25 Tower logger: mount: according to mtab, /dev/sdb1 is already mounted on /mnt/cache (Drive related) Mar 24 22:05:25 Tower emhttp: _shcmd: shcmd (116): exit status: 32 (Other emhttp) Mar 24 22:05:25 Tower emhttp: disk24 mount error: 32 (Errors) Mar 24 22:05:25 Tower emhttp: shcmd (117): rmdir /mnt/cache (Other emhttp) Mar 24 22:05:25 Tower emhttp: _shcmd: shcmd (117): exit status: 1 (Other emhttp) Mar 24 22:05:26 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Console No such file or directory (Other emhttp) Mar 24 22:05:26 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Music No such file or directory (Other emhttp) Mar 24 22:05:26 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Personal No such file or directory (Other emhttp) Mar 24 22:05:26 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Pictures No such file or directory (Other emhttp) Mar 24 22:05:26 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Videos No such file or directory (Other emhttp) Mar 24 22:05:26 Tower emhttp: get_filesystem_status: statfs: /mnt/user/mysql No such file or directory (Other emhttp) Mar 24 22:05:26 Tower emhttp: shcmd (118): /usr/local/sbin/emhttp_event disks_mounted (Other emhttp) Mar 24 22:05:26 Tower emhttp_event: disks_mounted (Other emhttp) Mar 24 22:05:26 Tower kernel: mdcmd (53): check CORRECT (unRAID engine) Mar 24 22:05:26 Tower kernel: md: recovery thread woken up ... (unRAID engine) Mar 24 22:05:26 Tower kernel: md: recovery thread rebuilding disk5 ... (unRAID engine) Mar 24 22:05:26 Tower kernel: md: using 5120k window, over a total of 3907018532 blocks. (unRAID engine) Mar 24 22:05:27 Tower emhttp: shcmd (119): :>/etc/samba/smb-shares.conf (Other emhttp) Mar 24 22:05:27 Tower avahi-daemon[1280]: Files changed, reloading. Mar 24 22:05:27 Tower emhttp: Restart SMB... (Other emhttp) Mar 24 22:05:27 Tower emhttp: shcmd (120): killall -HUP smbd (Minor Issues) Mar 24 22:05:27 Tower emhttp: shcmd (121): cp /etc/avahi/services/smb.service- /etc/avahi/services/smb.service (Other emhttp) Mar 24 22:05:27 Tower avahi-daemon[1280]: Files changed, reloading. Mar 24 22:05:27 Tower emhttp: shcmd (122): ps axc | grep -q rpc.mountd (Other emhttp) Mar 24 22:05:27 Tower avahi-daemon[1280]: Service group file /services/smb.service changed, reloading. Mar 24 22:05:27 Tower emhttp: Stop NFS... (Other emhttp) Mar 24 22:05:27 Tower emhttp: shcmd (123): /etc/rc.d/rc.nfsd stop |$stuff$ logger (Other emhttp) Mar 24 22:05:27 Tower mountd[7570]: Caught signal 15, un-registering and exiting. Mar 24 22:05:27 Tower avahi-daemon[1280]: Service "Tower" (/services/smb.service) successfully established. Mar 24 22:05:28 Tower emhttp: shcmd (124): /usr/local/sbin/emhttp_event svcs_restarted (Other emhttp) Mar 24 22:05:28 Tower emhttp_event: svcs_restarted (Other emhttp) Mar 24 22:05:28 Tower emhttp: shcmd (125): /usr/local/sbin/emhttp_event started (Other emhttp) Mar 24 22:05:28 Tower kernel: nfsd: last server has exited, flushing export cache Mar 24 22:05:28 Tower emhttp_event: started (Other emhttp) Mar 24 22:05:43 Tower avahi-daemon[1280]: Invalid response packet from host 192.168.0.119. Mar 24 22:07:23 Tower avahi-daemon[1280]: Invalid response packet from host 192.168.0.119. Mar 24 22:09:04 Tower avahi-daemon[1280]: Invalid response packet from host 192.168.0.119. Mar 24 22:10:44 Tower avahi-daemon[1280]: Invalid response packet from host 192.168.0.119. Mar 24 22:22:18 Tower emhttp: shcmd (126): /usr/sbin/hdparm -y /dev/sdb $stuff$> /dev/null (Drive related) Mar 24 22:23:12 Tower avahi-daemon[1280]: Invalid response packet from host 192.168.0.119.
  19. so most likely it's a bad drive... I couldn't get a smart report from the drive, but after powering down and re-powering up, running short smart test results in: smartctl 6.2 2013-07-26 r3841 [i686-linux-3.9.11p-unRAID] (local build) Copyright © 2002-13, Bruce Allen, Christian Franke, www.smartmontools.org === START OF INFORMATION SECTION === Model Family: Western Digital Caviar Green Device Model: WDC WD15EADS-00P8B0 Serial Number: WD-WMAVU0039302 LU WWN Device Id: 5 0014ee 056d2dfe2 Firmware Version: 01.00A01 User Capacity: 1,500,301,910,016 bytes [1.50 TB] Sector Size: 512 bytes logical/physical Device is: In smartctl database [for details use: -P show] ATA Version is: ATA8-ACS (minor revision not indicated) SATA Version is: SATA 2.6, 3.0 Gb/s Local Time is: Tue Mar 24 21:59:10 2015 EDT SMART support is: Available - device has SMART capability. SMART support is: Enabled === START OF READ SMART DATA SECTION === SMART overall-health self-assessment test result: PASSED General SMART Values: Offline data collection status: (0x84) Offline data collection activity was suspended by an interrupting command from host. Auto Offline Data Collection: Enabled. Self-test execution status: ( 0) The previous self-test routine completed without error or no self-test has ever been run. Total time to complete Offline data collection: (33600) seconds. Offline data collection capabilities: (0x7b) SMART execute Offline immediate. Auto Offline data collection on/off support. Suspend Offline collection upon new command. Offline surface scan supported. Self-test supported. Conveyance Self-test supported. Selective Self-test supported. SMART capabilities: (0x0003) Saves SMART data before entering power-saving mode. Supports SMART auto save timer. Error logging capability: (0x01) Error logging supported. General Purpose Logging supported. Short self-test routine recommended polling time: ( 2) minutes. Extended self-test routine recommended polling time: ( 383) minutes. Conveyance self-test routine recommended polling time: ( 5) minutes. SCT capabilities: (0x303f) SCT Status supported. SCT Error Recovery Control supported. SCT Feature Control supported. SCT Data Table supported. SMART Attributes Data Structure revision number: 16 Vendor Specific SMART Attributes with Thresholds: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE 1 Raw_Read_Error_Rate 0x002f 200 200 051 Pre-fail Always - 872 3 Spin_Up_Time 0x0027 192 180 021 Pre-fail Always - 5366 4 Start_Stop_Count 0x0032 098 098 000 Old_age Always - 2184 5 Reallocated_Sector_Ct 0x0033 200 200 140 Pre-fail Always - 0 7 Seek_Error_Rate 0x002e 100 253 000 Old_age Always - 0 9 Power_On_Hours 0x0032 047 047 000 Old_age Always - 39064 10 Spin_Retry_Count 0x0032 100 100 000 Old_age Always - 0 11 Calibration_Retry_Count 0x0032 100 253 000 Old_age Always - 0 12 Power_Cycle_Count 0x0032 100 100 000 Old_age Always - 79 192 Power-Off_Retract_Count 0x0032 200 200 000 Old_age Always - 22 193 Load_Cycle_Count 0x0032 199 199 000 Old_age Always - 3876 194 Temperature_Celsius 0x0022 122 105 000 Old_age Always - 28 196 Reallocated_Event_Count 0x0032 200 200 000 Old_age Always - 0 197 Current_Pending_Sector 0x0032 200 200 000 Old_age Always - 2 198 Offline_Uncorrectable 0x0030 200 200 000 Old_age Offline - 0 199 UDMA_CRC_Error_Count 0x0032 200 200 000 Old_age Always - 0 200 Multi_Zone_Error_Rate 0x0008 200 199 000 Old_age Offline - 47 SMART Error Log Version: 1 No Errors Logged SMART Self-test log structure revision number 1 Num Test_Description Status Remaining LifeTime(hours) LBA_of_first_error # 1 Short offline Completed without error 00% 39064 - # 2 Extended offline Completed without error 00% 4624 - # 3 Extended offline Completed without error 00% 4456 - # 4 Extended offline Completed without error 00% 4289 - # 5 Extended offline Completed without error 00% 4121 - # 6 Extended offline Completed without error 00% 3954 - # 7 Extended offline Completed without error 00% 3786 - # 8 Extended offline Completed without error 00% 3619 - # 9 Extended offline Completed without error 00% 3451 - #10 Extended offline Completed without error 00% 3285 - #11 Extended offline Completed without error 00% 3116 - #12 Extended offline Completed without error 00% 2948 - #13 Extended offline Completed without error 00% 2783 - #14 Extended offline Completed without error 00% 2613 - #15 Extended offline Completed without error 00% 2445 - #16 Extended offline Completed without error 00% 2278 - #17 Extended offline Completed without error 00% 2110 - #18 Extended offline Completed without error 00% 1943 - #19 Extended offline Completed without error 00% 1775 - #20 Extended offline Completed without error 00% 1610 - #21 Extended offline Completed without error 00% 1445 - SMART Selective self-test log data structure revision number 1 SPAN MIN_LBA MAX_LBA CURRENT_TEST_STATUS 1 0 0 Not_testing 2 0 0 Not_testing 3 0 0 Not_testing 4 0 0 Not_testing 5 0 0 Not_testing Selective self-test flags (0x0): After scanning selected spans, do NOT read-scan remainder of disk. If Selective self-test is pending on power-up, resume after 0 minute delay. so I see pending reallocated sectors so drive is probably on its way out. I bought a new drive and replaced this drive, but when I selected the new drive and started the array, I see unRaid tries to mount the new drive, and it's just sitting there... normally it'll tell me it's rebuilding the array... but it's not right now.. Mar 24 21:22:14 Tower emhttp: writing GPT on disk (sdn), with partition 1 offset 64, erased: 0 (Drive related) Mar 24 21:22:14 Tower emhttp: shcmd (88): sgdisk -Z /dev/sdn $stuff$> /dev/null (Drive related) Mar 24 21:22:16 Tower emhttp: shcmd (89): sgdisk -o -a 64 -n 1:64:0 /dev/sdn |$stuff$ logger (Drive related) Mar 24 21:22:16 Tower kernel: sdn: unknown partition table (Drive related) Mar 24 21:22:17 Tower logger: Creating new GPT entries. Mar 24 21:22:17 Tower logger: The operation has completed successfully. Mar 24 21:22:17 Tower emhttp: shcmd (90): udevadm settle (Other emhttp) Mar 24 21:22:17 Tower kernel: sdn: sdn1 (Drive related) Mar 24 21:22:17 Tower emhttp: Start array... (Other emhttp) Mar 24 21:22:17 Tower kernel: mdcmd (52): start RECON_DISK (unRAID engine) Mar 24 21:22:17 Tower kernel: unraid: allocating 207168K for 4096 stripes (12 disks) Mar 24 21:22:17 Tower kernel: md1: running, size: 1953514552 blocks (Drive related) Mar 24 21:22:17 Tower kernel: md2: running, size: 1953514552 blocks (Drive related) Mar 24 21:22:17 Tower kernel: md3: running, size: 3907018532 blocks (Drive related) Mar 24 21:22:17 Tower kernel: md4: running, size: 2930266532 blocks (Drive related) Mar 24 21:22:17 Tower kernel: md5: running, size: 3907018532 blocks (Drive related) Mar 24 21:22:17 Tower kernel: md6: running, size: 1465138552 blocks (Drive related) Mar 24 21:22:17 Tower kernel: md7: running, size: 1465138552 blocks (Drive related) Mar 24 21:22:17 Tower kernel: md8: running, size: 1953514552 blocks (Drive related) Mar 24 21:22:17 Tower kernel: md9: running, size: 1953514552 blocks (Drive related) Mar 24 21:22:17 Tower kernel: md10: running, size: 1953514552 blocks (Drive related) Mar 24 21:22:17 Tower kernel: md11: running, size: 3907018532 blocks (Drive related) Mar 24 21:22:17 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Console No such file or directory (Other emhttp) Mar 24 21:22:17 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Music No such file or directory (Other emhttp) Mar 24 21:22:17 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Personal No such file or directory (Other emhttp) Mar 24 21:22:17 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Pictures No such file or directory (Other emhttp) Mar 24 21:22:17 Tower emhttp: get_filesystem_status: statfs: /mnt/user/Videos No such file or directory (Other emhttp) Mar 24 21:22:17 Tower emhttp: get_filesystem_status: statfs: /mnt/user/mysql No such file or directory (Other emhttp) Mar 24 21:22:17 Tower emhttp: shcmd (91): udevadm settle (Other emhttp) Mar 24 21:22:17 Tower emhttp: shcmd (92): /usr/local/sbin/emhttp_event array_started (Other emhttp) Mar 24 21:22:17 Tower emhttp_event: array_started (Other emhttp) Mar 24 21:22:17 Tower emhttp: Mounting disks... (Other emhttp) Mar 24 21:22:17 Tower emhttp: shcmd (93): mkdir /mnt/disk1 (Routine) Mar 24 21:22:17 Tower emhttp: shcmd (94): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md1 /mnt/disk1 |$stuff$ logger (Other emhttp) Mar 24 21:22:17 Tower kernel: REISERFS (device md1): found reiserfs format "3.6" with standard journal (Routine) Mar 24 21:22:17 Tower kernel: REISERFS (device md1): using ordered data mode (Routine) Mar 24 21:22:17 Tower kernel: reiserfs: using flush barriers Mar 24 21:22:17 Tower 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 (Routine) Mar 24 21:22:17 Tower kernel: REISERFS (device md1): checking transaction log (md1) (Routine) Mar 24 21:22:18 Tower kernel: REISERFS (device md1): Using r5 hash to sort names (Routine) Mar 24 21:22:18 Tower emhttp: shcmd (95): mkdir /mnt/disk2 (Routine) Mar 24 21:22:18 Tower emhttp: shcmd (96): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md2 /mnt/disk2 |$stuff$ logger (Other emhttp) Mar 24 21:22:18 Tower kernel: REISERFS (device md2): found reiserfs format "3.6" with standard journal (Routine) Mar 24 21:22:18 Tower kernel: REISERFS (device md2): using ordered data mode (Routine) Mar 24 21:22:18 Tower kernel: reiserfs: using flush barriers Mar 24 21:22:18 Tower kernel: REISERFS (device md2): journal params: device md2, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine) Mar 24 21:22:18 Tower kernel: REISERFS (device md2): checking transaction log (md2) (Routine) Mar 24 21:22:18 Tower kernel: REISERFS (device md2): Using r5 hash to sort names (Routine) Mar 24 21:22:18 Tower emhttp: shcmd (97): mkdir /mnt/disk3 (Routine) Mar 24 21:22:18 Tower emhttp: shcmd (98): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md3 /mnt/disk3 |$stuff$ logger (Other emhttp) Mar 24 21:22:18 Tower kernel: REISERFS (device md3): found reiserfs format "3.6" with standard journal (Routine) Mar 24 21:22:18 Tower kernel: REISERFS (device md3): using ordered data mode (Routine) Mar 24 21:22:18 Tower kernel: reiserfs: using flush barriers Mar 24 21:22:18 Tower kernel: REISERFS (device md3): journal params: device md3, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine) Mar 24 21:22:18 Tower kernel: REISERFS (device md3): checking transaction log (md3) (Routine) Mar 24 21:22:18 Tower kernel: REISERFS (device md3): Using r5 hash to sort names (Routine) Mar 24 21:22:18 Tower emhttp: shcmd (99): mkdir /mnt/disk4 (Routine) Mar 24 21:22:18 Tower emhttp: shcmd (100): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md4 /mnt/disk4 |$stuff$ logger (Other emhttp) Mar 24 21:22:18 Tower kernel: REISERFS (device md4): found reiserfs format "3.6" with standard journal (Routine) Mar 24 21:22:18 Tower kernel: REISERFS (device md4): using ordered data mode (Routine) Mar 24 21:22:18 Tower kernel: reiserfs: using flush barriers Mar 24 21:22:18 Tower kernel: REISERFS (device md4): journal params: device md4, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine) Mar 24 21:22:18 Tower kernel: REISERFS (device md4): checking transaction log (md4) (Routine) Mar 24 21:22:18 Tower kernel: REISERFS (device md4): Using r5 hash to sort names (Routine) Mar 24 21:22:18 Tower emhttp: shcmd (101): mkdir /mnt/disk5 (Routine) Mar 24 21:22:18 Tower emhttp: shcmd (102): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md5 /mnt/disk5 |$stuff$ logger (Other emhttp) Mar 24 21:22:18 Tower kernel: REISERFS (device md5): found reiserfs format "3.6" with standard journal (Routine) Mar 24 21:22:18 Tower kernel: REISERFS (device md5): using ordered data mode (Routine) Mar 24 21:22:18 Tower kernel: reiserfs: using flush barriers Mar 24 21:22:18 Tower kernel: REISERFS (device md5): journal params: device md5, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine) Mar 24 21:22:18 Tower kernel: REISERFS (device md5): checking transaction log (md5) (Routine) Mar 24 21:22:19 Tower kernel: REISERFS (device md5): Using r5 hash to sort names (Routine) i'm hesitant to do anything at this point for fear of destroying my data... but i've never noticed it take this long at this point... this is a brand new drive that was not precleared... should I just leave it alone ?
  20. here's the log: Mar 23 18:39:43 Tower kernel: sd 2:0:4:0: [sdm] command f713f540 timed out (Drive related) Mar 23 18:39:43 Tower kernel: sas: Enter sas_scsi_recover_host busy: 1 failed: 1 (Drive related) Mar 23 18:39:43 Tower kernel: sas: trying to find task 0xf71c7400 (Drive related) Mar 23 18:39:43 Tower kernel: sas: sas_scsi_find_task: aborting task 0xf71c7400 (Drive related) Mar 23 18:39:43 Tower kernel: sas: sas_scsi_find_task: task 0xf71c7400 is aborted (Drive related) Mar 23 18:39:43 Tower kernel: sas: sas_eh_handle_sas_errors: task 0xf71c7400 is aborted (Errors) Mar 23 18:39:43 Tower kernel: sas: ata13: end_device-2:4: cmd error handler (Errors) Mar 23 18:39:43 Tower kernel: sas: ata9: end_device-2:0: dev error handler (Drive related) Mar 23 18:39:43 Tower kernel: sas: ata10: end_device-2:1: dev error handler (Drive related) Mar 23 18:39:43 Tower kernel: sas: ata11: end_device-2:2: dev error handler (Drive related) Mar 23 18:39:43 Tower kernel: sas: ata12: end_device-2:3: dev error handler (Drive related) Mar 23 18:39:43 Tower kernel: sas: ata13: end_device-2:4: dev error handler (Drive related) Mar 23 18:39:43 Tower kernel: sas: ata14: end_device-2:5: dev error handler (Drive related) Mar 23 18:39:43 Tower kernel: ata13.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x6 frozen (Errors) Mar 23 18:39:43 Tower kernel: ata13.00: failed command: READ FPDMA QUEUED (Minor Issues) Mar 23 18:39:43 Tower kernel: ata13.00: cmd 60/08:00:68:ed:b6/00:00:a3:00:00/40 tag 0 ncq 4096 in (Drive related) Mar 23 18:39:43 Tower kernel: res 40/00:ff:00:00:00/00:00:00:00:00/40 Emask 0x4 (timeout) (Errors) Mar 23 18:39:43 Tower kernel: ata13.00: status: { DRDY } (Drive related) Mar 23 18:39:43 Tower kernel: ata13: hard resetting link (Minor Issues) Mar 23 18:39:45 Tower kernel: mvsas 0000:02:00.0: Phy6 : No sig fis (Drive related) Mar 23 18:39:46 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[4]:rc= 0 (System) Mar 23 18:39:46 Tower kernel: sas: sas_form_port: phy6 belongs to port4 already(1)! (Drive related) Mar 23 18:39:51 Tower kernel: ata13.00: qc timeout (cmd 0x27) (Drive related) Mar 23 18:39:51 Tower kernel: ata13.00: failed to read native max address (err_mask=0x4) (Minor Issues) Mar 23 18:39:51 Tower kernel: ata13.00: HPA support seems broken, skipping HPA handling (Minor Issues) Mar 23 18:39:51 Tower kernel: ata13.00: revalidation failed (errno=-5) (Minor Issues) Mar 23 18:39:51 Tower kernel: ata13: hard resetting link (Minor Issues) Mar 23 18:39:53 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[4]:rc= 0 (System) Mar 23 18:39:53 Tower kernel: sas: sas_ata_task_done: SAS error 8a (Errors) Mar 23 18:39:53 Tower kernel: sas: sas_ata_task_done: SAS error 8a (Errors) Mar 23 18:39:53 Tower kernel: ata13.00: both IDENTIFYs aborted, assuming NODEV (Drive related) Mar 23 18:39:53 Tower kernel: ata13.00: revalidation failed (errno=-2) (Minor Issues) Mar 23 18:39:54 Tower kernel: mvsas 0000:02:00.0: Phy6 : No sig fis (Drive related) Mar 23 18:39:58 Tower kernel: sas: sas_form_port: phy6 belongs to port4 already(1)! (Drive related) Mar 23 18:39:58 Tower kernel: ata13: hard resetting link (Minor Issues) Mar 23 18:40:04 Tower kernel: ata13.00: qc timeout (cmd 0xef) (Drive related) Mar 23 18:40:04 Tower kernel: ata13.00: failed to set xfermode (err_mask=0x4) (Minor Issues) Mar 23 18:40:04 Tower kernel: ata13.00: disabled (Errors) Mar 23 18:40:04 Tower kernel: ata13.00: device reported invalid CHS sector 0 (Drive related) Mar 23 18:40:04 Tower kernel: ata13: hard resetting link (Minor Issues) Mar 23 18:40:06 Tower kernel: drivers/scsi/mvsas/mv_sas.c 1527:mvs_I_T_nexus_reset for device[4]:rc= 0 (System) Mar 23 18:40:06 Tower kernel: ata13: EH complete (Drive related) Mar 23 18:40:06 Tower kernel: sas: --- Exit sas_scsi_recover_host: busy: 0 failed: 0 tries: 1 (Drive related) Mar 23 18:40:06 Tower kernel: sd 2:0:4:0: [sdm] Unhandled error code (Errors) Mar 23 18:40:06 Tower kernel: sd 2:0:4:0: [sdm] (Drive related) Mar 23 18:40:06 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 (System) Mar 23 18:40:06 Tower kernel: sd 2:0:4:0: [sdm] CDB: (Drive related) Mar 23 18:40:06 Tower kernel: cdb[0]=0x28: 28 00 a3 b6 ed 68 00 00 08 00 Mar 23 18:40:06 Tower kernel: end_request: I/O error, dev sdm, sector 2746674536 (Errors) Mar 23 18:40:06 Tower kernel: md: disk5 read error, sector=2746674472 (Errors) Mar 23 18:40:06 Tower kernel: sd 2:0:4:0: [sdm] READ CAPACITY(16) failed (Drive related) Mar 23 18:40:06 Tower kernel: sd 2:0:4:0: [sdm] (Drive related) Mar 23 18:40:06 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 (System) Mar 23 18:40:06 Tower kernel: sd 2:0:4:0: [sdm] Sense not available. (Drive related) Mar 23 18:40:06 Tower kernel: sd 2:0:4:0: [sdm] READ CAPACITY failed (Drive related) Mar 23 18:40:06 Tower kernel: sd 2:0:4:0: [sdm] (Drive related) Mar 23 18:40:06 Tower kernel: Result: hostbyte=0x04 driverbyte=0x00 (System) Mar 23 18:40:06 Tower kernel: sd 2:0:4:0: [sdm] Sense not available. (Drive related) Mar 23 18:40:06 Tower kernel: sd 2:0:4:0: [sdm] Asking for cache data failed (Drive related) Mar 23 18:40:06 Tower kernel: sd 2:0:4:0: [sdm] Assuming drive cache: write through (Drive related) Mar 23 18:40:06 Tower kernel: sdm: detected capacity change from 1500301910016 to 0 (Drive related) Mar 23 18:40:06 Tower kernel: mvsas 0000:02:00.0: Phy6 : No sig fis (Drive related) Mar 23 18:40:10 Tower kernel: sas: sas_form_port: phy6 belongs to port4 already(1)! (Drive related) Mar 23 18:40:19 Tower kernel: md: disk5 write error, sector=2746674472 (Errors) Mar 23 18:40:19 Tower kernel: REISERFS warning: reiserfs-5090 is_tree_node: node level 14614 does not match to the expected one 1 (Minor Issues) Mar 23 18:40:19 Tower kernel: REISERFS error (device md5): vs-5150 search_by_key: invalid format found in block 343334309. Fsck? (Errors) Mar 23 18:40:19 Tower kernel: md: recovery thread woken up ... (unRAID engine) Mar 23 18:40:19 Tower kernel: REISERFS (device md5): Remounting filesystem read-only (Drive related) Mar 23 18:40:19 Tower kernel: REISERFS error (device md5): vs-13070 reiserfs_read_locked_inode: i/o failure occurred trying to find stat data of [1274 10843 0x0 SD] (Errors) Mar 23 18:40:20 Tower kernel: md: recovery thread has nothing to resync (unRAID engine) I had a drive go down a couple of weeks ago, but turned out to be a bad controller... this drive is one of the oldest drives in the array, which makes sense, also connected to a different controller than the controller that I replaced last couple of weeks ago.
  21. some additional info, i am using high water strategy with 50,000,000 min free space. And I have split level set at 999.
  22. Check out my system... whenever I add new files to the system right now, it seems to want to put it on disk3... yet disk 10 and disk 11 are completely empty... can someone clarify how unraid determines where to put files ? I thought it uses half disk method whereby starts with largest free disk and uses that down by half and then uses the next largest disk and uses its capacity by half...etc...
  23. well dunno, i shut down and rebooted and checked out the syslog and everything seems ok... can anyone comment on the "Align" column ? I noticed all my new drives have an Align of "1"... I stopped using preclear and just relied on unRaid to format my new drives, could that have caused any issues ?
  24. backstory is one of my controller cards died, while it was dying it erroneously reported a bad drive. I've since replaced controller card, and "re-adding" the bad drive (bad drive was replaced with a new drive), stopped array, unraid cleared the drive, and I re-added drive to array. web page seems to show it fine, but I saw this section in the syslog, not sure if it's an issue ? Mar 17 08:32:30 Tower emhttp: shcmd (159): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md10 /mnt/disk10 |$stuff$ logger (Other emhttp) Mar 17 08:32:30 Tower kernel: REISERFS (device md10): found reiserfs format "3.6" with standard journal (Routine) Mar 17 08:32:30 Tower kernel: REISERFS (device md10): using ordered data mode (Routine) Mar 17 08:32:30 Tower kernel: reiserfs: using flush barriers Mar 17 08:32:30 Tower kernel: REISERFS (device md10): journal params: device md10, size 8192, journal first block 18, max trans len 1024, max batch 900, max commit age 30, max trans age 30 (Routine) Mar 17 08:32:30 Tower kernel: REISERFS (device md10): checking transaction log (md10) (Routine) Mar 17 08:32:30 Tower kernel: REISERFS (device md10): Using r5 hash to sort names (Routine) Mar 17 08:32:30 Tower emhttp: shcmd (160): mkdir /mnt/disk11 (Routine) Mar 17 08:32:30 Tower emhttp: shcmd (161): set -o pipefail ; mount -t reiserfs -o user_xattr,acl,noatime,nodiratime /dev/md11 /mnt/disk11 |$stuff$ logger (Other emhttp) Mar 17 08:32:30 Tower logger: mount: wrong fs type, bad option, bad superblock on /dev/md11, Mar 17 08:32:30 Tower logger: missing codepage or helper program, or other error (Errors) Mar 17 08:32:30 Tower logger: In some cases useful info is found in syslog - try Mar 17 08:32:30 Tower logger: dmesg | tail or so Mar 17 08:32:30 Tower logger: Mar 17 08:32:30 Tower emhttp: _shcmd: shcmd (161): exit status: 32 (Other emhttp) Mar 17 08:32:30 Tower emhttp: disk11 mount error: 32 (Errors) Mar 17 08:32:30 Tower emhttp: shcmd (162): rmdir /mnt/disk11 (Other emhttp) Mar 17 08:32:30 Tower emhttp: shcmd (163): mkdir /mnt/cache (Other emhttp) Mar 17 08:32:30 Tower kernel: REISERFS warning (device md11): sh-2021 reiserfs_fill_super: can not find reiserfs on md11 (Minor Issues)
  25. I bought 2 G3s... one I was able to get a key for, the other was blacklisted... both were from a reputable local computer dealer... so who knows ? YMMV