RobJ Posted August 27, 2011 Share Posted August 27, 2011 Been having issues with interface resets since I built my new server. Isn't on a specific port. Happens with two setups, exact same motherboard. My motherboard is a Gigabyte GA-870A-UD3. Unsure if it's just BIOS setup (everything set to AHCI). Syslog attached. With your experience, I imagine you have already figured it out, but if not, I have a comment. In the attached syslog, the 'interface fatal error' only occurs on the port with a drive and controller supporting SATA 6gbps. On the 4th exception, the SATA speed is dropped from 6gbps to 3gbps, and there are no further errors reported. That would seem to indicate that the 6gbps SATA support is faulty somewhere, perhaps in the drive (a too early firmware implementation?), or the drive controller, or the driver module, or perhaps the cable itself cannot support the faster speed. This is somewhat normal, if disappointing, in early versions of new technology. Quote Link to comment
RobJ Posted August 27, 2011 Share Posted August 27, 2011 I have installed beta 12 and I get this: Aug 27 12:20:29 Unraid kernel: ata9: sas eh calling libata port error handler I have attached my syslog as this error is everywhere. It only occurs in the setup and identification of drives on the SAS card(s), and is typical. Everything is fine once the drives are set up. Please see my comments about a similar question here. This is a typical scenario in new technology where ambiguities in the applicable 'industry standards' cause all sorts of inconsistencies in the initialization and setup of devices. Windows hides this stuff, and the only indication of a device setup issue might be the cryptic "Error 10" (a PCI card start issue). Linux exposes much of this messiness in the syslog, often in considerable detail, and if you had not seen the syslog, you would not have even known there was a possible issue. But as drivers and devices mature, most of this 'messiness' is dropped from the logging. It is probably still occurring with many of the standard drives and devices, but is well understood and known to be harmless, and therefore no longer exposed in the syslog. We saw similar issues when the first AMD motherboards with the SB600/SB700 chipsets arrived, and I think I recall similar issues with the early port multiplier cards. When the drive and controller could not initially communicate in sync, the error handler would be called and a hard reset issued. It is just an easy way for one device to say "hold on, let's start over from the beginning, I'm an XYZ, what are you?". I expect that in future kernel releases with updated driver modules, most of this will disappear. Quote Link to comment
binfuser Posted August 27, 2011 Share Posted August 27, 2011 It's running really snappy for me, seems the CPU usage is better on my e2180 and network write increases on my e1000/gigabit setup. Quote Link to comment
smoldersonline Posted August 27, 2011 Share Posted August 27, 2011 Thanks a lot for your hard work on the beta's! After upgrading from 5.0-beta6a, Lion's Finder (OS X 10.7.1) reports: "Something wrong with the volume's CNID DB, etc ...". I have read about similar issues with previous beta's, but have not read about a simple and safe way how to best remedy this matter. I'm very grateful for any feedback. Quote Link to comment
greybeard Posted August 27, 2011 Share Posted August 27, 2011 More goodness. I have a new build with three Hitachi 3TB cool spin drives. One on a mobo port, one on an MV8 and one a JMB card. Newly configured flash drive. First started testing with beta 9 and had some of the problems report in these threads. Just updated to beta 12 and everything I have tried (not that I tried a lot) is working perfectly. Web interface is snappy (wasn't in early tests) and a parity check started running at 117MB per second. Of course that will drop as it gets further into the drive. So, for now, things are looking really good. I will do some more experimenting and post the results. 15 bay box with C2SEE - E3400 - Kingston KVR1333D3N9K2/4G DDR3-1333 SASLP-MV8 and JMB PCI Express Hong Kong special. CORSAIR CMPSU-750TX I really hope that this means it is getting close to the end of the beta cycle. A stable 5.0 official release would be a great thing. I too have to thank Tom for all his hard work and everyone that has been testing these betas. Quote Link to comment
Yorgo Posted August 28, 2011 Share Posted August 28, 2011 Still having the same NIC issues. Maybe it's time to bite the bullet and just buy a new card . . . http://lime-technology.com/forum/index.php?topic=14158.msg134868#msg134868 Y I might know what this issue is Please download the attached file and put into root of your flash share (same directory where bzimage/bzroot, etc., is located). Then from command line type this: sysctl -p /boot/sysctl.conf Now see if studdering still happens. Thanks, Tom. 1. Downloaded file and installed on root of flash share. 2. Upgraded from b9 to B12 (installed bzroot and bzimage files in their requisite locations). 3. Rebooted server. 4. Reviewed all drives (okay). 5. Started array. 6. Opened putty telnet session and typed in command as requested (attached copy of output). 7. Accessed test file on my TViX M6500a 8. It stuttered immediately, like before. I've downgraded to b9 again. Test file plays like a charm. Thanks, and let me know if you need anything more or want me to try something else. Y Quote Link to comment
limetech Posted August 28, 2011 Author Share Posted August 28, 2011 I've downgraded to b9 again. Test file plays like a charm. What makes you think it's a NIC problem? Quote Link to comment
crazytony Posted August 28, 2011 Share Posted August 28, 2011 From the machine accessing the unRaid server, can you try accessing files on the unRaid server via both a "user share" and a direct disk share? This will help me determine where in the code to look for this issue. In other words I want to know if it happens: a) when accessing files via user share on unRaid side b) when accessing files via disk share on unRaid side c) or both Accessing the files directly from the unraid server via the /mnt/user and /mnt/disk8 mount works as expected and has no errors(nothing in the syslog or dmesg). Mounting the affected disk remotely (/mnt/disk8) via NFS and going to the same folder works without any issues. Also accessing the user mount using smb from both Windows and Linux works without any issues. So it's just some interaction between the NFS daemon and the user shares. I'm not running permissions or any other NFS options (mount 192.168.1.4:/mnt/user/movies /tmp/test) And just for fun, here is the inode view of one of the folders causing problems (from the unraid server). It's not changing over time: root@mediastorage:/mnt/user/movies/Event Horizon# ls -i . 2147483709 AUDIO_TS/ 2147483710 VIDEO_TS/ root@mediastorage:/mnt/user/movies/Event Horizon# ls -i . 2147483709 AUDIO_TS/ 2147483710 VIDEO_TS/ root@mediastorage:/mnt/user/movies/Event Horizon# ls -i . 2147483709 AUDIO_TS/ 2147483710 VIDEO_TS/ Quote Link to comment
limetech Posted August 28, 2011 Author Share Posted August 28, 2011 Accessing the files directly from the unraid server via the /mnt/user and /mnt/disk8 mount works as expected and has no errors(nothing in the syslog or dmesg). Mounting the affected disk remotely (/mnt/disk8) via NFS and going to the same folder works without any issues. Also accessing the user mount using smb from both Windows and Linux works without any issues. So it's just some interaction between the NFS daemon and the user shares. I'm not running permissions or any other NFS options (mount 192.168.1.4:/mnt/user/movies /tmp/test) With the server up and running with everything exported as you want, please capture the contents of the "/etc/exports" file. It should be short, so from a telnet session type this command: cat /etc/exports and then select/copy/paste it's output and post here. Quote Link to comment
crazytony Posted August 28, 2011 Share Posted August 28, 2011 The b9 and b12 runs use the same exports file (it's the same stick): # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. /mnt/disk8 -async,no_subtree_check,fsid=18 *(rw,insecure,anongid=100,anonuid=99,all_squash) /mnt/user/movies -async,no_subtree_check,fsid=100 *(rw,insecure,anongid=100,anonuid=99,all_squash) /mnt/user/music -async,no_subtree_check,fsid=102 *(rw,insecure,anongid=100,anonuid=99,all_squash) /mnt/user/musicvideos -async,no_subtree_check,fsid=103 *(rw,insecure,anongid=100,anonuid=99,all_squash) /mnt/user/tvshows -async,no_subtree_check,fsid=101 *(rw,insecure,anongid=100,anonuid=99,all_squash) Quote Link to comment
limetech Posted August 28, 2011 Author Share Posted August 28, 2011 The b9 and b12 runs use the same exports file (it's the same stick): # See exports(5) for a description. # This file contains a list of all directories exported to other computers. # It is used by rpc.nfsd and rpc.mountd. /mnt/disk8 -async,no_subtree_check,fsid=18 *(rw,insecure,anongid=100,anonuid=99,all_squash) /mnt/user/movies -async,no_subtree_check,fsid=100 *(rw,insecure,anongid=100,anonuid=99,all_squash) /mnt/user/music -async,no_subtree_check,fsid=102 *(rw,insecure,anongid=100,anonuid=99,all_squash) /mnt/user/musicvideos -async,no_subtree_check,fsid=103 *(rw,insecure,anongid=100,anonuid=99,all_squash) /mnt/user/tvshows -async,no_subtree_check,fsid=101 *(rw,insecure,anongid=100,anonuid=99,all_squash) That looks normal. What is the o.s. and version of the machine you are trying to connect with? Quote Link to comment
crazytony Posted August 28, 2011 Share Posted August 28, 2011 That looks normal. What is the o.s. and version of the machine you are trying to connect with? It's a ubuntu box running 10.04.1: Linux frontmedia 2.6.35-30-generic-pae #56~lucid1-Ubuntu SMP Fri Jul 15 22:49:02 UTC 2011 i686 GNU/Linux It works fine except for files/folders on disk8. Do you want/need my super.dat file? I turned on nfsd debugging and this was in the syslog from running a ls on a broken folder Aug 28 13:40:15 mediastorage kernel: nfsd: ACCESS(3) 20: 81010001 00000064 00000000 00001bb7 00000000 00000000 0x1f Aug 28 13:40:15 mediastorage kernel: nfsd: fh_verify(20: 81010001 00000064 00000000 00001bb7 00000000 00000000) Aug 28 13:40:15 mediastorage kernel: nfsd_dispatch: vers 3 proc 1 Aug 28 13:40:15 mediastorage kernel: nfsd: GETATTR(3) 8: 00010001 00000064 00000000 00000000 00000000 00000000 Aug 28 13:40:15 mediastorage kernel: nfsd: fh_verify(8: 00010001 00000064 00000000 00000000 00000000 00000000) Aug 28 13:40:15 mediastorage kernel: nfsd_dispatch: vers 3 proc 4 Aug 28 13:40:15 mediastorage kernel: nfsd: ACCESS(3) 20: 81010001 00000064 00000000 00001bb7 00000000 00000000 0x1f Aug 28 13:40:15 mediastorage kernel: nfsd: fh_verify(20: 81010001 00000064 00000000 00001bb7 00000000 00000000) Aug 28 13:40:15 mediastorage kernel: nfsd_dispatch: vers 3 proc 1 Aug 28 13:40:15 mediastorage kernel: nfsd: GETATTR(3) 8: 00010001 00000064 00000000 00000000 00000000 00000000 Aug 28 13:40:15 mediastorage kernel: nfsd: fh_verify(8: 00010001 00000064 00000000 00000000 00000000 00000000) This was a working folder: Aug 28 13:42:15 mediastorage kernel: nfsd_dispatch: vers 3 proc 1 Aug 28 13:42:15 mediastorage kernel: nfsd: GETATTR(3) 20: 81010001 00000064 00000000 00001983 00000000 00000000 Aug 28 13:42:15 mediastorage kernel: nfsd: fh_verify(20: 81010001 00000064 00000000 00001983 00000000 00000000) Aug 28 13:42:15 mediastorage kernel: nfsd_dispatch: vers 3 proc 3 Aug 28 13:42:15 mediastorage kernel: nfsd: LOOKUP(3) 20: 81010001 00000064 00000000 00001983 00000000 00000000 VIDEO_TS Aug 28 13:42:15 mediastorage kernel: nfsd: fh_verify(20: 81010001 00000064 00000000 00001983 00000000 00000000) Aug 28 13:42:15 mediastorage kernel: nfsd: nfsd_lookup(fh 20: 81010001 00000064 00000000 00001983 00000000 00000000, VIDEO_TS) Aug 28 13:42:15 mediastorage kernel: nfsd: fh_compose(exp 00:0d/268435460 Secondhand Lions/VIDEO_TS, ino=536874939) Aug 28 13:42:15 mediastorage kernel: nfsd_dispatch: vers 3 proc 3 Aug 28 13:42:15 mediastorage kernel: nfsd: LOOKUP(3) 20: 81010001 00000064 00000000 00001983 00000000 00000000 AUDIO_TS Aug 28 13:42:15 mediastorage kernel: nfsd: fh_verify(20: 81010001 00000064 00000000 00001983 00000000 00000000) Aug 28 13:42:15 mediastorage kernel: nfsd: nfsd_lookup(fh 20: 81010001 00000064 00000000 00001983 00000000 00000000, AUDIO_TS) Aug 28 13:42:15 mediastorage kernel: nfsd: fh_compose(exp 00:0d/268435460 Secondhand Lions/AUDIO_TS, ino=536874938) Edit: it's 10.04.1 not 10.04.3. Quote Link to comment
jinjorge Posted August 28, 2011 Share Posted August 28, 2011 I am up and running with beta 12. I do have one question Is it normal for the cache drive to not automatically spin down like the rest of the drives in the array? Thanks, J Quote Link to comment
peter_sm Posted August 28, 2011 Share Posted August 28, 2011 7. Accessed test file on my TViX M6500a 8. It stuttered immediately, like before. I've downgraded to b9 again. Test file plays like a charm. Thanks, and let me know if you need anything more or want me to try something else. Y I also have a Tvix 6500, what firmware do you have ? and what is the info (media info) of the test-file? EDIT I do have issue with stuttering, but it looks like is a issue with latest MKV file (MKVToolnix/mkvmerge 4.2.0) //Peter Quote Link to comment
Yorgo Posted August 28, 2011 Share Posted August 28, 2011 I've downgraded to b9 again. Test file plays like a charm. What makes you think it's a NIC problem? I'm making an assumption based on posts from b10 on that we're having some kind of driver/ethernet controller issue. A new network card would be short money and a cheap test. I'm willing to try other options if you'd like. Y Quote Link to comment
Yorgo Posted August 28, 2011 Share Posted August 28, 2011 7. Accessed test file on my TViX M6500a 8. It stuttered immediately, like before. I've downgraded to b9 again. Test file plays like a charm. Thanks, and let me know if you need anything more or want me to try something else. Y I also have a Tvix 6500, what firmware do you have ? and what is the info (media info) of the test-file? EDIT I do have issue with stuttering, but it looks like is a issue with latest MKV file (MKVToolnix/mkvmerge 4.2.0) //Peter Hi Peter, TViX firmware is Kalimergo's 2.1.60 (a modified TViX 1.5.16), which has been very solid. The test file is a DVD (not BD) backup of Bringing Up Baby ripped via CloneDVD to DVD File output. The file has always played fine except with the last 3 betas. The only thing that has changed in the system is the unRAID firmware. Thanks, Y Quote Link to comment
peter_sm Posted August 28, 2011 Share Posted August 28, 2011 7. Accessed test file on my TViX M6500a 8. It stuttered immediately, like before. I've downgraded to b9 again. Test file plays like a charm. Thanks, and let me know if you need anything more or want me to try something else. Y I also have a Tvix 6500, what firmware do you have ? and what is the info (media info) of the test-file? EDIT I do have issue with stuttering, but it looks like is a issue with latest MKV file (MKVToolnix/mkvmerge 4.2.0) //Peter Hi Peter, TViX firmware is Kalimergo's 2.1.60 (a modified TViX 1.5.16), which has been very solid. The test file is a DVD (not BD) backup of Bringing Up Baby ripped via CloneDVD to DVD File output. The file has always played fine except with the last 3 betas. The only thing that has changed in the system is the unRAID firmware. Thanks, Y Try this version -> http://tvix.yakumo.se/files/fw_badeip/1.5-Series/BadEIP_M-6x00_1.5.16-Seres_unlocked+NOBDTrail_R1.fwp My "test" file is flawless on my server (NFS) Format : BDAV Format/Info : Blu-ray Video File size : 191 MiB Duration : 35s 280ms Overall bit rate : 45.4 Mbps Maximum Overall bit rate : 48.0 Mbps Quote Link to comment
Auggie Posted August 28, 2011 Share Posted August 28, 2011 With any "recent" 3TB capable beta's, has anyone: 1) Upgraded their parity drive to a 3TB and successfully built parity onto it? 2) Subsequently upgraded a data disk to a 3TB and successfully rebuilt data onto it? In both cases, I'm upgrading from 2TB drives. Yes and Yes... are you having issues with this? Not yet. I haven't dipped my toe into the beta's but it seems b12 is stable enough (data integrity wise) that I will finally wade into it. I was thinking to first upgrade to b12 with existing 2TB drives and run that for a week. If all goes well, upgrade the parity to 3TB and monitor the server for another week, then finally upgrade a data disk to 3TB. But if it's now to the point that there really is no concern with 3TB drives, I won't wait a week to upgrade a data disk to 3TB and will do that once parity has been built on the 3TB parity drive. Quote Link to comment
preproman Posted August 28, 2011 Share Posted August 28, 2011 Having a slight issue with a disk not showing up in the dropdown list under 5.0b12. I have 20 disks in the array and have moved from 4.6 -> 4.7 and that update when well. All disks were present and seen after the update. I followed the update instructions from 4.7 ->5.0b12 and all disks were see EXCEPT FOR disk20. I have attached the output of and ls -al /dev/disk/by-id, ls -al /dev/disk/by-id | grep 5XW1VW5A, a screen shot from 4.7 showing the disk recognized and in the array, and a screen shot from 5.0b12. The only disk that shows up in the dropdown is a disk I recently precleared. root@Darryl_Jacksons_Tower:~# ls -al /dev/disk/by-id | grep 5XW1VW5A lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST32000542AS_5XW1VW5A -> ../../sdx lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST32000542AS_5XW1VW5A-part1 -> ../../sdx1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1VW5A -> ../../sdx lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1VW5A-part1 -> ../../sdx1 total 0 drwxr-xr-x 2 root root 2840 2011-08-26 10:45 ./ drwxr-xr-x 6 root root 120 2011-08-26 10:45 ../ lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-Hitachi_HDS722020ALA330_JK11A8B9HV3T9F -> ../../sdp lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-Hitachi_HDS722020ALA330_JK11A8B9HV3T9F-part1 -> ../../sdp1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-Hitachi_HDS722020ALA330_JK11A8B9HVGXZF -> ../../sdf lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-Hitachi_HDS722020ALA330_JK11A8B9HVGXZF-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST2000DL003-9VT166_5YD0QDE1 -> ../../sde lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST2000DL003-9VT166_5YD0QDE1-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST2000DL003-9VT166_5YD120RZ -> ../../sdc lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST2000DL003-9VT166_5YD120RZ-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST2000DL003-9VT166_5YD14XPC -> ../../sda lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST2000DL003-9VT166_5YD14XPC-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST2000DL003-9VT166_5YD161BQ -> ../../sdt lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST2000DL003-9VT166_5YD161BQ-part1 -> ../../sdt1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST2000DL003-9VT166_5YD4G8JK -> ../../sdg lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST2000DL003-9VT166_5YD4G8JK-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST2000DL003-9VT166_5YD4PTGK -> ../../sdw lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST2000DL003-9VT166_5YD4PTGK-part1 -> ../../sdw1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST32000542AS_5XW13G4P -> ../../sdh lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST32000542AS_5XW13G4P-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST32000542AS_5XW1F0S2 -> ../../sdu lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST32000542AS_5XW1F0S2-part1 -> ../../sdu1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST32000542AS_5XW1NSFL -> ../../sdq lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST32000542AS_5XW1NSFL-part1 -> ../../sdq1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST32000542AS_5XW1VW5A -> ../../sdx lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST32000542AS_5XW1VW5A-part1 -> ../../sdx1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST32000542AS_5XW1XKKD -> ../../sdj lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST32000542AS_5XW1XKKD-part1 -> ../../sdj1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST32000542AS_5XW1Z8QK -> ../../sdk lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST32000542AS_5XW1Z8QK-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST32000542AS_5XW1ZTEF -> ../../sds lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST32000542AS_5XW1ZTEF-part1 -> ../../sds1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-ST32000542AS_5XW2HPMP -> ../../sdo lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-ST32000542AS_5XW2HPMP-part1 -> ../../sdo1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-WDC_WD20EARS-00J2GB0_WD-WCAYY0233190 -> ../../sdm lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-WDC_WD20EARS-00J2GB0_WD-WCAYY0233190-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-WDC_WD20EARS-00J2GB0_WD-WCAYY0234454 -> ../../sdd lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-WDC_WD20EARS-00J2GB0_WD-WCAYY0234454-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA0713298 -> ../../sdi lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA0713298-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA0753888 -> ../../sdl lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-WDC_WD20EARS-00MVWB0_WD-WCAZA0753888-part1 -> ../../sdl1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1077038 -> ../../sdr lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1077038-part1 -> ../../sdr1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1162805 -> ../../sdv lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1162805-part1 -> ../../sdv1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1176843 -> ../../sdn lrwxrwxrwx 1 root root 10 2011-08-26 10:45 ata-WDC_WD20EARS-00MVWB0_WD-WMAZA1176843-part1 -> ../../sdn1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_Hitachi_HDS7220_JK11A8B9HV3T9F -> ../../sdp lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_Hitachi_HDS7220_JK11A8B9HV3T9F-part1 -> ../../sdp1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_Hitachi_HDS7220_JK11A8B9HVGXZF -> ../../sdf lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_Hitachi_HDS7220_JK11A8B9HVGXZF-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST2000DL003-9VT_5YD0QDE1 -> ../../sde lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST2000DL003-9VT_5YD0QDE1-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST2000DL003-9VT_5YD120RZ -> ../../sdc lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST2000DL003-9VT_5YD120RZ-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST2000DL003-9VT_5YD14XPC -> ../../sda lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST2000DL003-9VT_5YD14XPC-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST2000DL003-9VT_5YD161BQ -> ../../sdt lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST2000DL003-9VT_5YD161BQ-part1 -> ../../sdt1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST2000DL003-9VT_5YD4G8JK -> ../../sdg lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST2000DL003-9VT_5YD4G8JK-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST2000DL003-9VT_5YD4PTGK -> ../../sdw lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST2000DL003-9VT_5YD4PTGK-part1 -> ../../sdw1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW13G4P -> ../../sdh lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW13G4P-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1F0S2 -> ../../sdu lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1F0S2-part1 -> ../../sdu1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1NSFL -> ../../sdq lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1NSFL-part1 -> ../../sdq1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1VW5A -> ../../sdx lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1VW5A-part1 -> ../../sdx1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1XKKD -> ../../sdj lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1XKKD-part1 -> ../../sdj1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1Z8QK -> ../../sdk lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1Z8QK-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1ZTEF -> ../../sds lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW1ZTEF-part1 -> ../../sds1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW2HPMP -> ../../sdo lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_ST32000542AS_5XW2HPMP-part1 -> ../../sdo1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WCAYY0233190 -> ../../sdm lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WCAYY0233190-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WCAYY0234454 -> ../../sdd lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WCAYY0234454-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA0713298 -> ../../sdi lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA0713298-part1 -> ../../sdi1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA0753888 -> ../../sdl lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WCAZA0753888-part1 -> ../../sdl1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1077038 -> ../../sdr lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1077038-part1 -> ../../sdr1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1162805 -> ../../sdv lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1162805-part1 -> ../../sdv1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1176843 -> ../../sdn lrwxrwxrwx 1 root root 10 2011-08-26 10:45 scsi-SATA_WDC_WD20EARS-00_WD-WMAZA1176843-part1 -> ../../sdn1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 usb-Lexar_JD_FireFly_AAAFVSBOFUTX6F20-0:0 -> ../../sdb lrwxrwxrwx 1 root root 10 2011-08-26 10:45 usb-Lexar_JD_FireFly_AAAFVSBOFUTX6F20-0:0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c50029efeca0 -> ../../sdh lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c50029efeca0-part1 -> ../../sdh1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c5002aab1ad2 -> ../../sdu lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c5002aab1ad2-part1 -> ../../sdu1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c5002abacec7 -> ../../sdq lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c5002abacec7-part1 -> ../../sdq1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c5002e834d78 -> ../../sdx lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c5002e834d78-part1 -> ../../sdx1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c5002ea3bdd7 -> ../../sdk lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c5002ea3bdd7-part1 -> ../../sdk1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c5002ea6a642 -> ../../sdj lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c5002ea6a642-part1 -> ../../sdj1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c5002eb3788b -> ../../sds lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c5002eb3788b-part1 -> ../../sds1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c5002ebde082 -> ../../sde lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c5002ebde082-part1 -> ../../sde1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c5002f1a0de0 -> ../../sda lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c5002f1a0de0-part1 -> ../../sda1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c5002f1a164a -> ../../sdc lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c5002f1a164a-part1 -> ../../sdc1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c5002f21967a -> ../../sdt lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c5002f21967a-part1 -> ../../sdt1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c5002f9084ed -> ../../sdo lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c5002f9084ed-part1 -> ../../sdo1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c500391593c6 -> ../../sdg lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c500391593c6-part1 -> ../../sdg1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000c500393ba5f9 -> ../../sdw lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000c500393ba5f9-part1 -> ../../sdw1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000cca222d9f75b -> ../../sdp lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000cca222d9f75b-part1 -> ../../sdp1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x5000cca222da2137 -> ../../sdf lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x5000cca222da2137-part1 -> ../../sdf1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x50014ee002725f76 -> ../../sdr lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x50014ee002725f76-part1 -> ../../sdr1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x50014ee057c79f8f -> ../../sdn lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x50014ee057c79f8f-part1 -> ../../sdn1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x50014ee0ad1d409d -> ../../sdv lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x50014ee0ad1d409d-part1 -> ../../sdv1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x50014ee204d36081 -> ../../sdm lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x50014ee204d36081-part1 -> ../../sdm1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x50014ee204f0f7f8 -> ../../sdl lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x50014ee204f0f7f8-part1 -> ../../sdl1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x50014ee25a2867cc -> ../../sdd lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x50014ee25a2867cc-part1 -> ../../sdd1 lrwxrwxrwx 1 root root 9 2011-08-26 10:45 wwn-0x50014ee25a45a4fb -> ../../sdi lrwxrwxrwx 1 root root 10 2011-08-26 10:45 wwn-0x50014ee25a45a4fb-part1 -> ../../sdi1 Quote Link to comment
jdog09 Posted August 28, 2011 Share Posted August 28, 2011 Keep seeing issues with the r8169 driver.. Any suggestions. The AFPD error is during a Time Machine Backup.. Might be related to the stability of the eth0 connection. Aug 28 10:14:07 stadiumNAS kernel: r8169 0000:04:00.0: eth0: link up Aug 28 10:14:39 stadiumNAS last message repeated 2 times Aug 28 10:16:24 stadiumNAS last message repeated 3 times Aug 28 10:17:14 stadiumNAS kernel: ------------[ cut here ]------------ Aug 28 10:17:14 stadiumNAS kernel: WARNING: at net/sched/sch_generic.c:255 dev_watchdog+0xf8/0x17b() Aug 28 10:17:14 stadiumNAS kernel: Hardware name: EP45-UD3P Aug 28 10:17:14 stadiumNAS kernel: NETDEV WATCHDOG: eth0 (r8169): transmit queue 0 timed out Aug 28 10:17:14 stadiumNAS kernel: Modules linked in: md_mod xor pata_jmicron i2c_i801 jmicron i2c_core r8169 ahci libahci Aug 28 10:17:14 stadiumNAS kernel: Pid: 0, comm: kworker/0:0 Not tainted 3.0.3-unRAID #3 Aug 28 10:17:14 stadiumNAS kernel: Call Trace: Aug 28 10:17:14 stadiumNAS kernel: [<c10288ac>] warn_slowpath_common+0x65/0x7a Aug 28 10:17:14 stadiumNAS kernel: [<c12c8bf6>] ? dev_watchdog+0xf8/0x17b Aug 28 10:17:14 stadiumNAS kernel: [<c1028925>] warn_slowpath_fmt+0x26/0x2a Aug 28 10:17:14 stadiumNAS kernel: [<c12c8bf6>] dev_watchdog+0xf8/0x17b Aug 28 10:17:14 stadiumNAS kernel: [<c10312ea>] run_timer_softirq+0x10a/0x182 Aug 28 10:17:14 stadiumNAS kernel: [<c12c8afe>] ? __netdev_watchdog_up+0x52/0x52 Aug 28 10:17:14 stadiumNAS kernel: [<c102ccce>] __do_softirq+0x6b/0xe5 Aug 28 10:17:14 stadiumNAS kernel: [<c102cc63>] ? irq_enter+0x3c/0x3c Aug 28 10:17:14 stadiumNAS kernel: <IRQ> [<c102cb21>] ? irq_exit+0x32/0x53 Aug 28 10:17:14 stadiumNAS kernel: [<c1015bbd>] ? smp_apic_timer_interrupt+0x6c/0x7a Aug 28 10:17:14 stadiumNAS kernel: [<c133584a>] ? apic_timer_interrupt+0x2a/0x30 Aug 28 10:17:14 stadiumNAS kernel: [<c104007b>] ? override_creds+0x1f/0x23 Aug 28 10:17:14 stadiumNAS kernel: [<c11dd604>] ? acpi_safe_halt+0x1c/0x2a Aug 28 10:17:14 stadiumNAS kernel: [<c11dd6db>] ? acpi_idle_enter_c1+0x61/0xb1 Aug 28 10:17:14 stadiumNAS kernel: [<c12985da>] ? cpuidle_idle_call+0x6b/0xa1 Aug 28 10:17:14 stadiumNAS kernel: [<c1001a60>] ? cpu_idle+0x3a/0x52 Aug 28 10:17:14 stadiumNAS kernel: [<c1331077>] ? start_secondary+0xad/0xaf Aug 28 10:17:14 stadiumNAS kernel: ---[ end trace 2eed0f0b922db24c ]--- Aug 28 10:17:14 stadiumNAS kernel: r8169 0000:04:00.0: eth0: link up Aug 28 10:17:46 stadiumNAS last message repeated 8 times Aug 28 10:18:49 stadiumNAS last message repeated 16 times Aug 28 10:19:37 stadiumNAS last message repeated 12 times Aug 28 10:19:39 stadiumNAS afpd[18263]: select: Invalid argument Aug 28 10:19:39 stadiumNAS afpd[18263]: dsi_stream_read: len:-1, Invalid argument Aug 28 10:19:39 stadiumNAS afpd[18263]: dsi_stream_receive: invalid packet, fatal Aug 28 10:19:41 stadiumNAS kernel: r8169 0000:04:00.0: eth0: link up Aug 28 10:19:59 stadiumNAS last message repeated 7 times Aug 28 10:20:09 stadiumNAS afpd[18263]: select: Invalid argument Aug 28 10:20:09 stadiumNAS afpd[18263]: dsi_stream_read: len:-1, Invalid argument Aug 28 10:20:09 stadiumNAS afpd[18263]: dsi_stream_receive: invalid packet, fatal Aug 28 10:20:10 stadiumNAS afpd[18263]: =============================================================== Aug 28 10:20:10 stadiumNAS afpd[18263]: INTERNAL ERROR: Signal 11 in pid 18263 (2-2-0-p6) Aug 28 10:20:10 stadiumNAS afpd[18263]: =============================================================== Aug 28 10:20:10 stadiumNAS afpd[18263]: BACKTRACE: 9 stack frames: Aug 28 10:20:10 stadiumNAS afpd[18263]: #0 /usr/sbin/afpd(netatalk_panic+0x2d) [0x8097dfd] Aug 28 10:20:10 stadiumNAS afpd[18263]: #1 /usr/sbin/afpd() [0x8097f6d] Aug 28 10:20:10 stadiumNAS afpd[18263]: #2 [0xb76e4400] Aug 28 10:20:10 stadiumNAS afpd[18263]: #3 /usr/sbin/afpd(dsi_writeinit+0x60) [0x8094600] Aug 28 10:20:10 stadiumNAS afpd[18263]: #4 /usr/sbin/afpd(afp_over_dsi+0x368) [0x80548f8] Aug 28 10:20:10 stadiumNAS afpd[18263]: #5 /usr/sbin/afpd() [0x8053c55] Aug 28 10:20:10 stadiumNAS afpd[18263]: #6 /usr/sbin/afpd(main+0x660) [0x8070bd0] Aug 28 10:20:10 stadiumNAS afpd[18263]: #7 /lib/libc.so.6(__libc_start_main+0xe6) [0xb72cfb86] Aug 28 10:20:10 stadiumNAS afpd[18263]: #8 /usr/sbin/afpd() [0x8053a51] Aug 28 10:20:18 stadiumNAS afpd[18618]: afp_disconnect: primary reconnect failed Aug 28 10:20:19 stadiumNAS afpd[18618]: dsi_stream_read: len:0, unexpected EOF Aug 28 10:20:26 stadiumNAS afpd[18627]: afp_disconnect: primary reconnect failed Aug 28 10:20:28 stadiumNAS afpd[18627]: dsi_stream_read: len:0, unexpected EOF Aug 28 10:20:36 stadiumNAS afpd[18636]: afp_disconnect: primary reconnect failed Aug 28 10:20:40 stadiumNAS afpd[18636]: dsi_stream_read: len:0, unexpected EOF Aug 28 10:20:47 stadiumNAS afpd[18645]: afp_disconnect: primary reconnect failed Aug 28 10:20:47 stadiumNAS afpd[18645]: dsi_stream_read: len:0, unexpected EOF Quote Link to comment
BRiT Posted August 28, 2011 Share Posted August 28, 2011 Having a slight issue with a disk not showing up in the dropdown list under 5.0b12. Attach your syslog. It includes the device inventory that unRAID sees. Quote Link to comment
preproman Posted August 28, 2011 Share Posted August 28, 2011 Having a slight issue with a disk not showing up in the dropdown list under 5.0b12. Attach your syslog. It includes the device inventory that unRAID sees. Sorry about that, forgot to attach it to another post, the pictures in the first one took up all the allowed 192KB worth of space. Anyway, syslog is attached now. The unRAID machine sees the drive just fine, but you can see from a "grep sdx" that emhttp is complaining about there being "too many devices" root@Darryl_Jacksons_Tower:~# cat /boot/syslog.txt | grep sdx Aug 26 11:38:59 Darryl_Jacksons_Tower kernel: sd 10:0:7:0: [sdx] 3907029168 512-byte logical blocks: (2.00 TB/1.81 TiB) Aug 26 11:38:59 Darryl_Jacksons_Tower kernel: sd 10:0:7:0: [sdx] Write Protect is off Aug 26 11:38:59 Darryl_Jacksons_Tower kernel: sd 10:0:7:0: [sdx] Mode Sense: 00 3a 00 00 Aug 26 11:38:59 Darryl_Jacksons_Tower kernel: sd 10:0:7:0: [sdx] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA Aug 26 11:38:59 Darryl_Jacksons_Tower kernel: sdx: sdx1 Aug 26 11:38:59 Darryl_Jacksons_Tower kernel: sd 10:0:7:0: [sdx] Attached SCSI disk Aug 26 11:38:59 Darryl_Jacksons_Tower emhttp: too many devices to add ../../devices/pci0000:00/0000:00:06.0/0000:02:00.0/host10/port-10:7/end_device-10:7/target10:0:7/10:0:7:0/block/sdx Aug 26 11:40:13 Darryl_Jacksons_Tower emhttp: too many devices to add ../../devices/pci0000:00/0000:00:06.0/0000:02:00.0/host10/port-10:7/end_device-10:7/target10:0:7/10:0:7:0/block/sdx Aug 26 11:40:15 Darryl_Jacksons_Tower emhttp: too many devices to add ../../devices/pci0000:00/0000:00:06.0/0000:02:00.0/host10/port-10:7/end_device-10:7/target10:0:7/10:0:7:0/block/sdx Quote Link to comment
darkside40 Posted August 28, 2011 Share Posted August 28, 2011 Updated from beta10 today and directly reverted back. I am having massive speed issues, writing data to the array dropped from, not really good 25MB/s, to unuseable 3MB/s. I think that could be an issue with the Realtek Nic again. Quote Link to comment
gfjardim Posted August 28, 2011 Share Posted August 28, 2011 Updated from beta10 today and directly reverted back. I am having massive speed issues, writing data to the array dropped from, not really good 25MB/s, to unuseable 3MB/s. I think that could be an issue with the Realtek Nic again. You can try reverting to r8168 driver with the attached package. I didn't test it but it should work with beta12. Just download it and install it with installpkg command. realtek.zip Quote Link to comment
tyrindor Posted August 28, 2011 Share Posted August 28, 2011 With any "recent" 3TB capable beta's, has anyone: 1) Upgraded their parity drive to a 3TB and successfully built parity onto it? 2) Subsequently upgraded a data disk to a 3TB and successfully rebuilt data onto it? In both cases, I'm upgrading from 2TB drives. I've done both, 1x 2TB->3TB Parity, 3x 2TB->3TB Data. It was the exact same method as 1.5TB -> 2TB, except I used the latest preclear_disk beta for 3TB drives. Any problems you have with this are going to be related to your devices not supporting 3TB, some SATA cards and motherboards don't support it. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.