mifronte

I can try the # comment. My other thought was to use a script that returns a non-zero along with the &&.

If I only want to manually move the cache drive contents, can I clear the mover schedule field to disable it from running?

Ahh, so because my drive was pre-formatted without the jumpers. I assumed the WD Disk Diagnostic zero write would have done it, but I guess it does not. Would fdisk or parted in Linux allow me to completely zero out the drive so that I can intall the jumper? I have Ubuntu 10.10 that I can boot from a USB flash drive.

Here is an interesting read on using the parted tool to align these advanced format drives. Is this possible with unRAID? If so, it could also solve the Samsung Spinpoint F4 drives.

I am migrating the drive from a Windows XP machine to my newly built unRAID server. The drive had previously been pre-aligned for Windows XP using the WD Drive Alignment Tool. My intention was to install the jumper on pin 7 & 8 and then run the preclear script. However, with the jumper applied, unRAID gives me tons of errors on boot and the preclear script just hangs. I have two other WD20EARS that works fine with the jumper, but they were never aligned with the WD Drive Alignment Tool.

Is there some test I can perform on the disk without the jumper to see if it is properly aligned in unRAID?

The WD20EARS advanced format drive that had been aligned on Windows XP using the WD Drive Alignment Tool is giving me errors when I applied a jumper to pin 7 & 8. It is fine without the jumper. So is it possible that the WD Align Tool is permanent and therefore no jumper is needed? Can someone hint to as what the errrors are about? Here are a sampling of the errors: Oct 16 15:35:25 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0 Oct 16 15:35:25 Beanstalk kernel: ata20.00: irq_stat 0x00020002, device error via SDB FIS Oct 16 15:35:25 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 16 15:35:25 Beanstalk kernel: ata20.00: cmd 60/08:08:a8:88:e0/00:00:e8:00:00/40 tag 1 ncq 4096 in Oct 16 15:35:25 Beanstalk kernel: res 41/01:00:af:88:e0/ff:00:e8:00:00/40 Emask 0x401 (device error) <F> Oct 16 15:35:25 Beanstalk kernel: ata20.00: status: { DRDY ERR } Oct 16 15:35:25 Beanstalk kernel: ata20.00: configured for UDMA/100 Oct 16 15:35:25 Beanstalk kernel: ata20: EH complete Oct 16 15:35:25 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 Oct 16 15:35:25 Beanstalk kernel: ata20.00: irq_stat 0x00060002, device error via SDB FIS Oct 16 15:35:25 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 16 15:35:25 Beanstalk kernel: ata20.00: cmd 60/08:00:a8:88:e0/00:00:e8:00:00/40 tag 0 ncq 4096 in Oct 16 15:35:25 Beanstalk kernel: res 41/01:00:af:88:e0/ff:00:e8:00:00/40 Emask 0x401 (device error) <F> Oct 16 15:35:25 Beanstalk kernel: ata20.00: status: { DRDY ERR } Oct 16 15:35:25 Beanstalk kernel: ata20.00: configured for UDMA/100 Oct 16 15:35:25 Beanstalk kernel: ata20: EH complete Oct 16 15:35:25 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 Oct 16 15:35:25 Beanstalk kernel: ata20.00: irq_stat 0x00060002, device error via SDB FIS Oct 16 15:35:25 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 16 15:35:25 Beanstalk kernel: ata20.00: cmd 60/08:00:a8:88:e0/00:00:e8:00:00/40 tag 0 ncq 4096 in Oct 16 15:35:25 Beanstalk kernel: res 41/01:00:af:88:e0/ff:00:e8:00:00/40 Emask 0x401 (device error) <F> Oct 16 15:35:25 Beanstalk kernel: ata20.00: status: { DRDY ERR } Oct 16 15:35:25 Beanstalk kernel: ata20.00: configured for UDMA/100 Oct 16 15:35:25 Beanstalk kernel: ata20: EH complete Oct 16 15:35:25 Beanstalk kernel: ata20.00: NCQ disabled due to excessive errors Oct 16 15:35:25 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 Oct 16 15:35:25 Beanstalk kernel: ata20.00: irq_stat 0x00060002, device error via SDB FIS Oct 16 15:35:25 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 16 15:35:25 Beanstalk kernel: ata20.00: cmd 60/08:00:a8:88:e0/00:00:e8:00:00/40 tag 0 ncq 4096 in Oct 16 15:35:25 Beanstalk kernel: res 41/01:00:af:88:e0/ff:00:e8:00:00/40 Emask 0x401 (device error) <F> Oct 16 15:35:25 Beanstalk kernel: ata20.00: status: { DRDY ERR } Oct 16 15:35:25 Beanstalk kernel: ata20.00: configured for UDMA/100 Oct 16 15:35:25 Beanstalk kernel: ata20: EH complete Oct 16 15:35:25 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Oct 16 15:35:25 Beanstalk kernel: ata20.00: irq_stat 0x00060002, device error via D2H FIS Oct 16 15:35:25 Beanstalk kernel: ata20.00: failed command: READ DMA EXT Oct 16 15:35:25 Beanstalk kernel: ata20.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in Oct 16 15:35:25 Beanstalk kernel: res 51/01:00:af:88:e0/ff:00:e8:00:00/e0 Emask 0x1 (device error) Oct 16 15:35:25 Beanstalk kernel: ata20.00: status: { DRDY ERR } Oct 16 15:35:25 Beanstalk kernel: ata20.00: configured for UDMA/100 Oct 16 15:35:25 Beanstalk kernel: ata20: EH complete Oct 16 15:35:25 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Oct 16 15:35:25 Beanstalk kernel: ata20.00: irq_stat 0x00060002, device error via D2H FIS Oct 16 15:35:25 Beanstalk kernel: ata20.00: failed command: READ DMA EXT Oct 16 15:35:25 Beanstalk kernel: ata20.00: cmd 25/00:08:a8:88:e0/00:00:e8:00:00/e0 tag 0 dma 4096 in Oct 16 15:35:25 Beanstalk kernel: res 51/01:00:af:88:e0/ff:00:e8:00:00/e0 Emask 0x1 (device error) Oct 16 15:35:25 Beanstalk kernel: ata20.00: status: { DRDY ERR } Oct 16 15:35:25 Beanstalk kernel: ata20.00: configured for UDMA/100 Oct 16 15:35:25 Beanstalk kernel: sd 20:0:0:0: [sdj] Unhandled sense code Oct 16 15:35:25 Beanstalk kernel: sd 20:0:0:0: [sdj] Result: hostbyte=0x00 driverbyte=0x08 Oct 16 15:35:25 Beanstalk kernel: sd 20:0:0:0: [sdj] Sense Key : 0x3 [current] [descriptor] Oct 16 15:35:25 Beanstalk kernel: Descriptor sense data with sense descriptors (in hex): Oct 16 15:35:25 Beanstalk kernel: 72 03 13 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Oct 16 15:35:25 Beanstalk kernel: e8 e0 88 af Oct 16 15:35:25 Beanstalk kernel: sd 20:0:0:0: [sdj] ASC=0x13 ASCQ=0x0 Oct 16 15:35:25 Beanstalk kernel: sd 20:0:0:0: [sdj] CDB: cdb[0]=0x28: 28 00 e8 e0 88 a8 00 00 08 00 Oct 16 15:35:25 Beanstalk kernel: end_request: I/O error, dev sdj, sector 3907029167

I am trying to install an advanced format drive that has been aligned in Windows XP with the WD Drive Alignment tool. When I had this drive installed without the jumper, unRAID recognized it as an NTFS drive with no problems. So I applied the jumper to pin 7-8 with the intention of running preclear on the drive to wipe it clean. unRAID did not like that at all. On boot, I started getting a lot of errors such as these: Oct 16 15:35:25 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x2 SErr 0x0 action 0x0 Oct 16 15:35:25 Beanstalk kernel: ata20.00: irq_stat 0x00020002, device error via SDB FIS Oct 16 15:35:25 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 16 15:35:25 Beanstalk kernel: ata20.00: cmd 60/08:08:a8:88:e0/00:00:e8:00:00/40 tag 1 ncq 4096 in Oct 16 15:35:25 Beanstalk kernel: res 41/01:00:af:88:e0/ff:00:e8:00:00/40 Emask 0x401 (device error) <F> Oct 16 15:35:25 Beanstalk kernel: ata20.00: status: { DRDY ERR } Oct 16 15:35:25 Beanstalk kernel: ata20.00: configured for UDMA/100 Oct 16 15:35:25 Beanstalk kernel: ata20: EH complete Oct 16 15:35:25 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 Oct 16 15:35:25 Beanstalk kernel: ata20.00: irq_stat 0x00060002, device error via SDB FIS Oct 16 15:35:25 Beanstalk kernel: ata20.00: failed command: READ FPDMA QUEUED Oct 16 15:35:25 Beanstalk kernel: ata20.00: cmd 60/08:00:a8:88:e0/00:00:e8:00:00/40 tag 0 ncq 4096 in Oct 16 15:35:25 Beanstalk kernel: res 41/01:00:af:88:e0/ff:00:e8:00:00/40 Emask 0x401 (device error) <F> Oct 16 15:35:25 Beanstalk kernel: ata20.00: status: { DRDY ERR } Oct 16 15:35:25 Beanstalk kernel: ata20.00: configured for UDMA/100 Oct 16 15:35:25 Beanstalk kernel: ata20: EH complete Oct 16 15:35:25 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x1 SErr 0x0 action 0x0 Oct 16 15:35:25 Beanstalk kernel: ata20.00: irq_stat 0x00060002, device error via SDB FIS It gets to the point where the drive connection gets downgraded to UDMA/66 before unRAID is up and running. Then unMenu is unresponsive and when I try running the preclear_disk.sh script, it just froze after hitting enter. Even powering down unRAID took an excessive long time. So I decided to attach the drive to my Windows XP machine and run the WD Diagnostic with the jumper. The short SMART test failed. I removed the jumper and ran the short test again and it passed. I am in the process of running the long test now. Then I will zero the drive out using the WD Diagnostic tool. It appears the WD Drive Alignment tool alters the firmware to begin at a certain block and you cannot use the jumper after running the WD Drive Alignment Tool. However, I recalled that I once tested to see if a zeroing of the drive retains the alignment of the drive by the WD Drive Alignment tool and it does not. So I hope to zero the drive after the long SMART test using the WD Diagnostic tool and then unRAID will not complain. Since I have not assigned a parity drive, can I skip the preclear and just install the drive into the array?

Much quieter than a 1U rackmount server. They start at full speed and then slowdown to about 1000 RPMs. Their max is 3900 RPM, so you get the picture. But I may measure the db's from 1m and send you some numbers if you want. Hello startcat. What settings do you use fro the fans in BIOS? 4-pin workstation or 4-pin server? The lowest spin my Delta AFC1212DE fans are running are at 2500 rpm at 4-pin server. How are you getting yours to 1000 rpm?

I have an NTFS disk where the folder names contain Unicode characters (Vietnamese). Doing an ls on the mounted NTFS disk from telnet or the console yields the folder names with a bunch of escape characters. I even shared out the NTFS mount and the folder names on my Windows XP Pro looks fine, but on my Seagate FreeAgent Theater+ (linux based) does not properly display the folder names correctly, which has always been this way even when I was sharing the drive out on a Windows machine. Now my question: How can I safely copy these folders from the mounted NTFS disk to an unRAID disk? Basically, the folders either starts with the letter P or A and I need to copy only folders starting with P to one disk and A to another disk? I read the one thread about Greek characters where the copy process left out some files. In my case, only the folder names have the Unicode characters.

Hi starcat. Unfortuanately, I had not move the data yet. Also, can you tell me your BIOS Serial ATA and Fan settings? For Serial ATA, I have Native Mode set to Auto and SATA ACHI set to Enabled. For FAN, I have it set to 4-pin workstation. I found worstation spins the fans slower than server.

I have updated three ST32000542AS 2TB and one has completely failed a few days later. Two is awaiting to be precleared. The failed one had been working since April 2010 and failed a few days after updating firmware from CC34 to CC35. I also updated a ST31000520AS 1TB and preclear indicated one SMART attribute as failing. I will see how the remaining two unused ST32000542AS fair after preclearing.

Yes I am migrating data as part of a new build. The existing drives will be part of unRAID and so I figured might as well mount the drives locally for speed and eventually conversion. Another factor is the drives are coming from a machine that only has 100 Megabits LAN.

Thanks Joe. I have not jumpered them and was afraid to turn on my unRAID server until I know for sure what to do. I may have lost 2TB on my Seagate ST32000542AS Barracuda LP 2TB drive already, see here, and I am now being extra careful as I continue to get my unRAID server running and migrate the data over to it.

I have two NTFS WD EARS drives with data that I plan to migrate to my unRAID. The drives where installed in my Windows XP workstation so they were aligned with the WD Drive Alignment software. I plan to first mount them as NTFS in unRAID to move the data. Then I will preclear the drives to use as normal unRAID data drives. I know I will need to jumper these drives prior to running preclear, but do I need to jumper them so that I can mount the NTFS volume to move the data?

So my Seagate ST32000542AS Barracuda LP 2TB (mostly full) started to make 10 loud clicking noise on power up. Then all is quiet and the BIOS only recognize the drive as a 4GB ST_M13FQBL drive (what the heck?). This is on a Windows XP machine. I also stuck it in my Unraid server with the same result. Any suggestions to get it back up so that I can recover the data? I had just updated the firmware to CC35 a few days ago too. This is the symptom that my drive is showing. Can a drive be stuck in stand-by mode? Ironically, this occurs after I had trouble getting my Windows XP workstation out of stand-by mode. If so, what can I do? My Unraid build is still not ready (preclearing and waiting on Pro license key) but this is the second Seagate to show problems after upgrading to CC35. The first one showed a Failing_Now SMART attribute after preclearing and it was a Seagate ST31000520AS Barracuda LP 1TB drive. The lame Seagate SeaTools (DOS and Windows) is unable to test this drive connected to the Sil3114 or Sil3124 controllers on my Windows XP workstation. I am running the DOS Seatools version on the Unraid server since it has the on-board SATA ports to verify why preclear showed a failing SMART Attribute. Edit: The lame DOS Seatools does not have the feature to read SMART attributes, but the 1TB drive passed the short SMART test. THe 2TB drive is only recognized as a ST_M13FQBL drive and Seatools can't do anything to it. I am hating Seagate today.

Attached is my first two ever PreClear outputs of a Seagate ST31000520AS Barracuda LP 1TB (Preclear sdj.txt) and WD 10EADS Caviar Green 1TB (PreClear sdk.txt). I think everything looks OK, please review to see if I am interpreting the files correctly. There is one SMART Unknown_Attribute (Vendor ID # 184) with a Failing_Now in PreClear sdj.txt! Should I be concerned? The PreClear sdk.txt has a message of "Not in smartctl database". Should I be concern? The /tmp/read_speedsdj file says 57.8 MB/s and /tmp/read_speedsdk says 41.0 MB/s. Is this the average read throughput? How can I get it to be higher? The second reading is really low and this is on the Syba SD-PCXSA2-2E2R Sil3124 base PCI-X 64-bit 133MHz SATA controller. PreClear_sdj.txt PreClear_sdk.txt

Attached are the outputs of the cat /proc/partitions and ls -l /dev/disk/by-id commands. Hope this can tell you why the model/serial column are not displaying in UnMenu Main page. Also I don't know why some drives are labeled ata and some are labeled scsi-sata. Initially, I had piped the outputs of these two commands to two text files in /tmp. However, I could not find a way to download those two files to my Windows machine. I tried logging in as root using ftp in a Windows command prompt, but I could not change to the /tmp directory. So I ended moving the two files to the /boot share and then access that share. Outputs.txt

the disk devices are detected by looking at the contents of /proc/partitions cat /proc/partitions The model/serial numbers are then found by matching the devices with the contents of a listing of /dev/disk/by-id ls -l /dev/disk/by-id I am a little confused...am I suppose to edit some UnMenu configuration file to match the output of these two commands for both information to show up on the Main page of UnMenu under the listing for Drive Partitions that are not in the protected array? Right now everything shows (dev, temp, size) up except the model/serial column.

Newbie here. How can I get the drive models and serial numbers to show up on the main page under the Drive Partitions - Not In Protected Array section? The other columns have information for the 11 drives, but not the model/serial column. The funny thing is I think when I first started up UnMenu, the information was there. I have 11 drives, but none have been assigned since I have yet to complete the preclearing stage. I am running the free version of Unraid 4.5.6. while I complete my hardware build.

To have a logical and ordered 1:1 mapping so that if the need arises for manual load balancing of buses and controller based on usage patterns.

On the SATA to SFF-8087 Mini SAS Reverse breakout cable, each SATA connection is labeled from 0-3. Does anyone know how this corresponds to the actual drive bays from the front? Does the 0-3 slots for each SAS drive plane go from left to right or vice versa?

Well, in my quest to save money, I purchased a refurbished Delta AFC1212DE-PWM 120mm fan from eBay for less than 2/3 the price of a new fan. The only caveat is that the wires are terminated with a Dell 5-pin connector and not the PWM standard Molex KK 4-pin connector. In addition, the wires/pin position is different from the standard PWM fan. The good news is that I was able to extract the wires from the connector using a push pin and then rearrange the wires to match the standard PWM fans. The 5-pin connector does fit the standard 4-pin PWM fan header (with the 5th pin slot over hanging the 4-pin fan header) and so I should be good to go. I am now waiting for my thermal paste to install the CPU heatsink before I can test to see if the modified fan works. Since it is a refurbished unit, I hope it function normally. If the fan works out, I will order two more to complete the 120mm fan wall bracket when it arrived. The latest information is that it should be shipping on October 20, 2010.

I am in the midst of building my Unraid server with the Norco RPC-4224. I hit a snag in that the 120mm fan wall bracket will not be shipping until October 20, 2010 and the wires of the 80mm fans that shipped with the unit is too short to reach my motherboard fan headers. I plan on using the Delta AFC1212DE-PWM fans. According to starcat on this forum, this fan has enough static pressure to keep all 20 drives cool under load and yet can be slowed down via the motherboard PWM feature to be quiet when the server is not under load. The downside of this fan is that it is kind of expensive for a new one. However, I plan on testing a refurbished fan from eBay for $10. The only caveat is that it is terminated with the Dell 5-pin instead of the standard PWM 4-pin. However, since the fan is a genuine Delta AFC1212DE-PWM, I plan on modifying the termination to see if it will work with the standard PWM 4-pin fan header.

Thanks ohlwiler for the testing. I am in the process of putting together my server with the same hardware and will be splitting the two AOC-SAT2-MV8 cards into the 133 MHz and 100 MHz slots. At least you affirmed my initial assumption that splitting the cards so as to not use the shared PCI-X buses on the Supermìcro X7SBE is beneficial.