mifronte

Is it possible to add the cache drive to the file browser?

Would it be possible to add the cache drive to the file browser list?

I have two Vertex III 120GB in RAID 0 as my system boot drive for Windows 7 64-bit on an Asus P8P67 Deluxe motherboard. I do experience crashes every 2-3 weeks with the computer on 24x7 and sleep enabled. Hard to say what is the root cause between the Intel P67 chipset and the new Sandforce controllers. After all, the Intel Sandybridge did have a major recall when it came out. The unfortunate thing is the OCZ forum is filled with guesses and not facts. You have users there claiming stability when their system does not crash after a day or a week. To me, it is stable only if there are no unknown crashes after several months or a year.

What is this newperms script? I am using unRAID 4.7. The data has been copied from disk4 to disk1. What should my next steps be to remove disk4 from the array? Should I: 01. Stop the array. 02. Un-assign disk4 on the device. 03. Execute initiconfig command. I don't know if I should also un-assign the parity drive or not?

So I decided to run this cp command from the Wiki: cp -r -v -p /mnt/disk4/* /mnt/disk1 | todos > /boot/disk1copy.txt Then I will remove disk4 from the array and execute the initconfig command. After that I will run a parity check. Does that sound correct?

I would like to move data from one drive (disk04) to another (disk01) so that I can free up the slot that is assigned to disk04. Can I run a command on the unRAID server and still maintain parity? My goal is to run disk04 through preclear so that it will replace disk01. But first I need to move the data on disk04 to disk01 and I would prefer to do this locally on the unRAID server.

You are using the Basic version which, I believe, does not support user level security.

Just ordered two. That will completely fill my 20 disks array with 1 spare.

The data rebuild and parity check completed successfully. Everything is back to green. Whew! Now it's time to move the last drive off of this Monoprice two port Sil3132 controller. The controller is so small that the SATA cable to the troubled slot is stretched to its limits. I will probably just use this controller to preclear disks and not to host actual data.

I powered down the server and moved the unresponsive disk to a different slot (different controller and cable). The server is doing a Data-Rebuild now. I thought it would just let me assign the disk to the same slot? Did I do something wrong? The server booted up with the slot showing the disk missing. I went into the device and assign the same disk to the same slot and started up the server. I was hoping if the disk is good, then no Data-Rebuild is required. Attached is the smart report. Does the disk look healthy? smart_sdv.txt

Thanks Joe. I am going to stop the script now while it is still in the post-read phase. Thanks for the information about the when the pre-clear signature is lookd at. This disk may end up being used if the other disk is still responsive after moving to a different controller.

I have a disk being pre-cleared. It is in the post-read phase of cycle 2 out of 3 cycles. I now have a red dot next to one of my disk and would like to power down the server to move the unresponsive disk to a new controller. I would like to preserve the disk being pre-cleared so that unRAID will recognize it as a good pre-cleared disk just in case I need to use it to replace the unresponsive disk. Is there a way to tell the preclear_disk.sh to stop when the second cycle is completed so that I do not have to wait for another cycle to power down the server? If not, when can I ctrl-c out of the script and still preserve the disk as being pre-cleared for unRAID?

I am using version 4.7. I have tried the smartctl -a -d ata /dev/sdp command and failed with the following message: Smartctl: Device Read Identity Failed (not an ATA/ATAPI device) A mandatory SMART command failed: exiting. To continue, add one or more '-T permissive' options. BTW, can I move two disks at the same time to different slots? It appears the non-responding disk is on the Sil3132 controller and I would like to get both disks off the controller.

I would like to try the disk in a different slot, which will be using a different controller and cable. What are the steps once I stop the array, power down, and then move the disk to a different slot? I take it unRAID is going to complain when it powers up and find the disk on a different controller.

Today I checked the array and one of the disk has a red dot next to it. Attached is the excerpt of when the errors started to occur. I tried clicking the SM and HD link for the disk in myMain with no success. Please advise what should I do now? Failed_Disk_Syslog.pdf

Yes. The two drives in the RAID 0 is on my Asus P8P67 Deluxe motherboard Intel SATA III ports. Now if I can tune my Intel i7 2600K CPU and Sapphire HD6850 graphic card to achieve a perfect Windows Experience Index (WEI) of 7.9.

So I decided to get a second OCZ Vertex 3 120 GB and configured the two drives in a RAID 0 as my system drive. Here is the HD Tune results: Test Speed - Fast Block Size - 8 MB

NewEgg lists the Rosewill RC-211 as a SIL3132 which is the same as the Monoprice card. Rahahal, which SIL3134 card are you referring to? I installed the Monoprice SIL3132 card, but have not run a parity check yet to see if they are error free. However, I see this in the syslog: May 25 21:55:24 Beanstalk kernel: scsi17 : sata_sil24 (Drive related) May 25 21:55:24 Beanstalk kernel: ata17: SATA max UDMA/100 host m128@0xd0d04000 port 0xd0d00000 irq 16 (Drive related) May 25 21:55:24 Beanstalk kernel: ata17: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) I noticed it only support UDMA/100 and not UDMA/133 like the SuperMicro AOC-SAT3-MVL8 controllers.

I have two coming from Baldwin Park, CA this Friday. My last two Samsung F4s came from Baldwin Park too and they were double boxed with the plastic bumpers.

Does the SIL3132 from Monoprice behaves in unRAID, meaning, it supports all drive commands and does not cause any errors like the ones that I posted? My SIL3124 card works fine except during parity check where it does not like some commands.

I would like to change my current SIL3124 controller to either the SIL3132 or the JMicron JMB362 to see if I can get rid of these errors on a parity check: May 19 10:16:18 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 19 10:16:18 Beanstalk kernel: ata20.00: irq_stat 0x00020002, failed to transmit command FIS (Minor Issues) May 19 10:16:18 Beanstalk kernel: ata20.00: failed command: READ DMA EXT (Minor Issues) May 19 10:16:18 Beanstalk kernel: ata20.00: cmd 25/00:00:ff:92:ae/00:01:11:00:00/e0 tag 0 dma 131072 in (Drive related) May 19 10:16:18 Beanstalk kernel: res 25/00:00:ff:92:ae/00:01:11:00:00/e0 Emask 0x12 (ATA bus error) (Errors) May 19 10:16:18 Beanstalk kernel: ata20.00: status: { DF ERR } (Drive related) May 19 10:16:18 Beanstalk kernel: ata20: hard resetting link (Minor Issues) May 19 10:16:20 Beanstalk kernel: ata20: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) May 19 10:16:20 Beanstalk kernel: ata20.00: configured for UDMA/100 (Drive related) May 19 10:16:20 Beanstalk kernel: ata20: EH complete (Drive related) May 19 10:18:41 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 19 10:18:41 Beanstalk kernel: ata20.00: irq_stat 0x00020002, failed to transmit command FIS (Minor Issues) May 19 10:18:41 Beanstalk kernel: ata20.00: failed command: READ DMA EXT (Minor Issues) May 19 10:18:41 Beanstalk kernel: ata20.00: cmd 25/00:00:27:f7:87/00:04:12:00:00/e0 tag 0 dma 524288 in (Drive related) May 19 10:18:41 Beanstalk kernel: res 25/00:00:27:f7:87/00:04:12:00:00/e0 Emask 0x12 (ATA bus error) (Errors) May 19 10:18:41 Beanstalk kernel: ata20.00: status: { DF ERR } (Drive related) May 19 10:18:41 Beanstalk kernel: ata20: hard resetting link (Minor Issues) May 19 10:18:43 Beanstalk kernel: ata20: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) May 19 10:18:43 Beanstalk kernel: ata20.00: configured for UDMA/100 (Drive related) May 19 10:18:43 Beanstalk kernel: ata20: EH complete (Drive related) May 19 10:19:50 Beanstalk ntpd[3474]: synchronized to 132.163.4.103, stratum 1 May 19 10:20:43 Beanstalk kernel: ata19.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 19 10:20:43 Beanstalk kernel: ata19.00: irq_stat 0x00020002, failed to transmit command FIS (Minor Issues) May 19 10:20:43 Beanstalk kernel: ata19.00: failed command: READ DMA EXT (Minor Issues) May 19 10:20:43 Beanstalk kernel: ata19.00: cmd 25/00:00:8f:2c:40/00:01:13:00:00/e0 tag 0 dma 131072 in (Drive related) May 19 10:20:43 Beanstalk kernel: res 25/00:00:8f:2c:40/00:01:13:00:00/e0 Emask 0x12 (ATA bus error) (Errors) May 19 10:20:43 Beanstalk kernel: ata19.00: status: { DF ERR } (Drive related) May 19 10:20:43 Beanstalk kernel: ata19: hard resetting link (Minor Issues) May 19 10:20:45 Beanstalk kernel: ata19: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) May 19 10:20:45 Beanstalk kernel: ata19.00: configured for UDMA/100 (Drive related) May 19 10:20:45 Beanstalk kernel: ata19: EH complete (Drive related) May 19 10:21:05 Beanstalk kernel: ata19.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 19 10:21:05 Beanstalk kernel: ata19.00: irq_stat 0x00020002, failed to transmit command FIS (Minor Issues) May 19 10:21:05 Beanstalk kernel: ata19.00: failed command: READ DMA EXT (Minor Issues) May 19 10:21:05 Beanstalk kernel: ata19.00: cmd 25/00:00:97:71:5f/00:01:13:00:00/e0 tag 0 dma 131072 in (Drive related) May 19 10:21:05 Beanstalk kernel: res 25/00:00:97:71:5f/00:01:13:00:00/e0 Emask 0x12 (ATA bus error) (Errors) May 19 10:21:05 Beanstalk kernel: ata19.00: status: { DF ERR } (Drive related) May 19 10:21:05 Beanstalk kernel: ata19: hard resetting link (Minor Issues) May 19 10:21:07 Beanstalk kernel: ata19: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) May 19 10:21:07 Beanstalk kernel: ata19.00: configured for UDMA/100 (Drive related) May 19 10:21:07 Beanstalk kernel: ata19: EH complete (Drive related) May 19 10:21:33 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 19 10:21:33 Beanstalk kernel: ata20.00: irq_stat 0x00020002, failed to transmit command FIS (Minor Issues) May 19 10:21:33 Beanstalk kernel: ata20.00: failed command: READ DMA EXT (Minor Issues) May 19 10:21:33 Beanstalk kernel: ata20.00: cmd 25/00:00:97:a8:87/00:01:13:00:00/e0 tag 0 dma 131072 in (Drive related) May 19 10:21:33 Beanstalk kernel: res 25/00:00:97:a8:87/00:01:13:00:00/e0 Emask 0x12 (ATA bus error) (Errors) May 19 10:21:33 Beanstalk kernel: ata20.00: status: { DF ERR } (Drive related) May 19 10:21:33 Beanstalk kernel: ata20: hard resetting link (Minor Issues) May 19 10:21:36 Beanstalk kernel: ata20: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) May 19 10:21:36 Beanstalk kernel: ata20.00: configured for UDMA/100 (Drive related) May 19 10:21:36 Beanstalk kernel: ata20: EH complete (Drive related) May 19 10:21:41 Beanstalk kernel: ata19.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 (Errors) May 19 10:21:41 Beanstalk kernel: ata19.00: irq_stat 0x00020002, device error via D2H FIS (Errors) May 19 10:21:41 Beanstalk kernel: ata19.00: failed command: READ DMA EXT (Minor Issues) May 19 10:21:41 Beanstalk kernel: ata19.00: cmd 25/00:00:97:94:8f/00:04:13:00:00/e0 tag 0 dma 524288 in (Drive related) May 19 10:21:41 Beanstalk kernel: res 51/84:7f:97:94:8f/00:01:13:00:00/e0 Emask 0x10 (ATA bus error) (Errors) May 19 10:21:41 Beanstalk kernel: ata19.00: status: { DRDY ERR } (Drive related) May 19 10:21:41 Beanstalk kernel: ata19.00: error: { ICRC ABRT } (Errors) May 19 10:21:41 Beanstalk kernel: ata19: hard resetting link (Minor Issues) May 19 10:21:43 Beanstalk kernel: ata19: SATA link up 3.0 Gbps (SStatus 123 SControl 0) (Drive related) May 19 10:21:43 Beanstalk kernel: ata19.00: configured for UDMA/100 (Drive related) May 19 10:21:43 Beanstalk kernel: ata19: EH complete (Drive related) May 19 10:22:48 Beanstalk kernel: ata20: limiting SATA link speed to 1.5 Gbps (Drive related) May 19 10:22:48 Beanstalk kernel: ata20.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6 frozen (Errors) May 19 10:22:48 Beanstalk kernel: ata20.00: failed command: READ DMA EXT (Minor Issues) May 19 10:22:48 Beanstalk kernel: ata20.00: cmd 25/00:00:e7:a5:c3/00:04:13:00:00/e0 tag 0 dma 524288 in (Drive related) May 19 10:22:48 Beanstalk kernel: res 40/00:ff:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout) (Errors) May 19 10:22:48 Beanstalk kernel: ata20.00: status: { DRDY } (Drive related) May 19 10:22:48 Beanstalk kernel: ata20: hard resetting link (Minor Issues) May 19 10:22:50 Beanstalk kernel: ata20: SATA link up 1.5 Gbps (SStatus 113 SControl 10) (Drive related) May 19 10:22:50 Beanstalk kernel: ata20.00: configured for UDMA/100 (Drive related) May 19 10:22:50 Beanstalk kernel: ata20.00: device reported invalid CHS sector 0 (Drive related) May 19 10:22:50 Beanstalk kernel: ata20: EH complete (Drive related) My SuperMicro X7SBE has a PCIeX4 and PCIeX8 slot and so I plan on intalling the new 2 ports controller and just move the two SATA cables over to the new controller. 01. Would either the SIL3132 or the JMicron JMB362 be able to run in a PCIeX4 slot? 02. Which of the two cards is more reliable to work with unRAID? 02. What would I need to do when unRAID starts with the two disks connected to the new controller?

This was the first update of unMENU for me and it looked like I was missing a lot of updats. On notable is that the myMain has changed. I was using the myMain_local.conf file, but a new one was downloaded. The new one has no instructions and so is there a link where I can read up on the MyMain to merge my old myMain_local.conf file? Update: I found the myMain 1.5 thread. Will read up to merge my old conf file.

Thanks Joe. That is one more thing off my mind as I nurse my server that recently had a hiccup.

Running unMENU Version 1.3 Revision: 139 One of my disk (last disk # 16) in the array is not showing up in the File Browser. Just wondering why and how can I get it to show up? I believe it used to show up.

I am getting a lot of these in the syslog when booting: May 18 00:29:27 Beanstalk emhttp: shcmd (25): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md5 /mnt/disk5 2>&1 | logger May 18 00:29:27 Beanstalk emhttp: shcmd (26): set -o pipefail ; mount -t reiserfs -o noacl,nouser_xattr,noatime,nodiratime /dev/md3 /mnt/disk3 2>&1 | logger Does means anything? Also attached is my syslog after a clean boot. Is there anything to indicate why writing to disk16 in the array would cause /mnt/disk16 to be unresponsive to even a simple ls command? syslog_mifronte_20110518.txt