abs0lut.zer0

Hey all I have been having constant errors with one of my 2 TB drives and now i want to get it out and return it which could take some time, so as not to leave my array unprotected i have put one of my old 1 TB drives in the array and copied all off the 2TB into other disks in the array. So it's empty and i now want to remove the 2TB drive and TRY not to lose my shares ... i have read this http://lime-technology.com/forum/index.php?topic=9340.msg89092#msg89092 but my understanding i will lose my shares... is there any way to replace a big with a small and not lose the shares ? and is that link the current and only way to achieve it? thanks.

my one wd20ears has been giving me errors and i have changed slots and indirectly that means i have changed cables too... i have taken the drive out of the array and then rebuilt it again and still i get a few errors ... here is a part of the syslog .. Sep 11 11:22:08 Terok-Nor kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 11 11:22:08 Terok-Nor kernel: ata1.00: failed command: READ DMA EXT Sep 11 11:22:08 Terok-Nor kernel: ata1.00: cmd 25/00:08:00:f7:ae/00:00:d4:00:00/e0 tag 0 dma 4096 in Sep 11 11:22:08 Terok-Nor kernel: res 51/04:08:00:f7:ae/00:00:d4:00:00/e0 Emask 0x1 (device error) Sep 11 11:22:08 Terok-Nor kernel: ata1.00: status: { DRDY ERR } Sep 11 11:22:08 Terok-Nor kernel: ata1.00: error: { ABRT } Sep 11 11:22:08 Terok-Nor kernel: ata1.00: configured for UDMA/133 Sep 11 11:22:08 Terok-Nor kernel: ata1: EH complete Sep 11 11:22:11 Terok-Nor kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 11 11:22:11 Terok-Nor kernel: ata1.00: failed command: READ DMA EXT Sep 11 11:22:11 Terok-Nor kernel: ata1.00: cmd 25/00:08:00:f7:ae/00:00:d4:00:00/e0 tag 0 dma 4096 in Sep 11 11:22:11 Terok-Nor kernel: res 51/04:08:00:f7:ae/00:00:d4:00:00/e0 Emask 0x1 (device error) Sep 11 11:22:11 Terok-Nor kernel: ata1.00: status: { DRDY ERR } Sep 11 11:22:11 Terok-Nor kernel: ata1.00: error: { ABRT } Sep 11 11:22:11 Terok-Nor kernel: ata1.00: configured for UDMA/133 Sep 11 11:22:11 Terok-Nor kernel: ata1: EH complete Sep 11 11:22:14 Terok-Nor kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 11 11:22:14 Terok-Nor kernel: ata1.00: failed command: READ DMA EXT Sep 11 11:22:14 Terok-Nor kernel: ata1.00: cmd 25/00:08:00:f7:ae/00:00:d4:00:00/e0 tag 0 dma 4096 in Sep 11 11:22:14 Terok-Nor kernel: res 51/04:08:00:f7:ae/00:00:d4:00:00/e0 Emask 0x1 (device error) Sep 11 11:22:14 Terok-Nor kernel: ata1.00: status: { DRDY ERR } Sep 11 11:22:14 Terok-Nor kernel: ata1.00: error: { ABRT } Sep 11 11:22:14 Terok-Nor kernel: ata1.00: configured for UDMA/133 Sep 11 11:22:14 Terok-Nor kernel: ata1: EH complete Sep 11 11:22:17 Terok-Nor kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 11 11:22:17 Terok-Nor kernel: ata1.00: failed command: READ DMA EXT Sep 11 11:22:17 Terok-Nor kernel: ata1.00: cmd 25/00:08:00:f7:ae/00:00:d4:00:00/e0 tag 0 dma 4096 in Sep 11 11:22:17 Terok-Nor kernel: res 51/04:08:00:f7:ae/00:00:d4:00:00/e0 Emask 0x1 (device error) Sep 11 11:22:17 Terok-Nor kernel: ata1.00: status: { DRDY ERR } Sep 11 11:22:17 Terok-Nor kernel: ata1.00: error: { ABRT } Sep 11 11:22:17 Terok-Nor kernel: ata1.00: configured for UDMA/133 Sep 11 11:22:17 Terok-Nor kernel: ata1: EH complete Sep 11 11:22:20 Terok-Nor kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 11 11:22:20 Terok-Nor kernel: ata1.00: failed command: READ DMA EXT Sep 11 11:22:20 Terok-Nor kernel: ata1.00: cmd 25/00:08:00:f7:ae/00:00:d4:00:00/e0 tag 0 dma 4096 in Sep 11 11:22:20 Terok-Nor kernel: res 51/04:08:00:f7:ae/00:00:d4:00:00/e0 Emask 0x1 (device error) Sep 11 11:22:20 Terok-Nor kernel: ata1.00: status: { DRDY ERR } Sep 11 11:22:20 Terok-Nor kernel: ata1.00: error: { ABRT } Sep 11 11:22:20 Terok-Nor kernel: ata1.00: configured for UDMA/133 Sep 11 11:22:20 Terok-Nor kernel: ata1: EH complete Sep 11 11:22:22 Terok-Nor kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0 Sep 11 11:22:22 Terok-Nor kernel: ata1.00: failed command: READ DMA EXT Sep 11 11:22:22 Terok-Nor kernel: ata1.00: cmd 25/00:08:00:f7:ae/00:00:d4:00:00/e0 tag 0 dma 4096 in Sep 11 11:22:22 Terok-Nor kernel: res 51/04:08:00:f7:ae/00:00:d4:00:00/e0 Emask 0x1 (device error) Sep 11 11:22:22 Terok-Nor kernel: ata1.00: status: { DRDY ERR } Sep 11 11:22:22 Terok-Nor kernel: ata1.00: error: { ABRT } Sep 11 11:22:22 Terok-Nor kernel: ata1.00: configured for UDMA/133 Sep 11 11:22:22 Terok-Nor kernel: sd 0:0:0:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08 Sep 11 11:22:22 Terok-Nor kernel: sd 0:0:0:0: [sdb] Sense Key : 0xb [current] [descriptor] Sep 11 11:22:22 Terok-Nor kernel: Descriptor sense data with sense descriptors (in hex): Sep 11 11:22:22 Terok-Nor kernel: 72 0b 00 00 00 00 00 0c 00 0a 80 00 00 00 00 00 Sep 11 11:22:22 Terok-Nor kernel: d4 ae f7 00 Sep 11 11:22:22 Terok-Nor kernel: sd 0:0:0:0: [sdb] ASC=0x0 ASCQ=0x0 Sep 11 11:22:22 Terok-Nor kernel: sd 0:0:0:0: [sdb] CDB: cdb[0]=0x28: 28 00 d4 ae f7 00 00 00 08 00 Sep 11 11:22:22 Terok-Nor kernel: end_request: I/O error, dev sdb, sector 3568236288 Sep 11 11:22:22 Terok-Nor kernel: ata1: EH complete Sep 11 11:22:22 Terok-Nor kernel: md: disk3 read error Sep 11 11:22:22 Terok-Nor kernel: handle_stripe read error: 3568236224/2, count: 1 what i am asking is how i can prove there is something wrong so i can return the disk as the retailer is full of **** and just plugs it in and formats it and says look it's working ... so what can i do? thanks all..

:'( :'( :'( :'( :'( :'( I hope the adapter goes to that nice quiet place where all good adapters go to rest.....

Thank you very much Raj

Hey all I live in South Africa where most tech is TOO expensive and i only EVER want to have a 6 disk unRAID build. So the question IS.... Do i get a cheap 6 sata connector mobo or sata card with a cheap mobo.. I DO REALLY WANNA HAVE 3TB SUPPORT FOR 5.x BUILDS ON THIS MOBO .. (sorry about the caps but this advice will have to last me at least 2+ years on my limited budget) thanks for ANY advice.

anybody? :'(

My server has run a monthly parity check and then this has happened, is there someone who can please try make me understand what has caused these errors. i have attached a screenshot of the web page. i have attached a syslog of the parity check i have attached a short smart check of the mentioned disk (i know about the 44 temperature it has always done that on that slot even with a different disk) i am thinking after reading what i can understand, i think i might have a bad sata cable or a faulty power supply as i did run the disk through 3 preclears i am not sure if it can be faulty? so any help would be appreciated. thank you smart.txt syslogparity01082011.zip

Again, someone is getting hung up about the 'beta' label. All current releases, except the latest betas, are known to have a known bug which could strike at any time, causing significant loss of data. I know which version of the software I would rather trust my data to ... see my sig. so 4.7 is gonna be updated soon to avoid this bug ? as i have a card that from what i read WILL not be supported under 5.0x builds of unraid...

Hey all I have a question, i have read somewhere that the array is as fast as the fastest drives. I realize the copies to the array will be as fast as the 5900rpm drive. So if i have want to have only green drives 5900rpm's as my data drives, will it make a REAL difference if i have a 7200rpm parity drive ? I am thinking that maybe parity checks will go faster? or will it just really be a waste of electricity and a heater? Thanks

I think the reason for the freeze is an combination of sleeping drives if it was sleeping drives then this thread should not exist as this is nothing to do with unraid's disk performance (if you slept the disks you should expect the delay)

my two cents how i see this on this page.. http://lime-technology.com/technology it quotes.... Ease of installation Easy capacity expansion. Ease of integration with other systems. Easy recovery from disk device failure. Immunity from catastrophic full data loss. Good multiple-stream read performance. Adequate write performance. so i have always thought in the logic of reading and writing to a single drive.... as it all depends on what type of allocation method you use as well... eg. i use high water so therefore if i do multiple copies at the same time they will go to the same drive and it does also hang for me for a while.. like i said just my interpretation of unraid....

do you use a app for file listings or just the command line?

agreed, i fully went into the unRAID move knowing that it was a one man show and i did my research to see the amazing community behind it, BUT there are still some questions that can ONLY be answered by limetech.

I am also waiting for the outcome of this post to do an upgrade to start testing 5.x series... so bump.. bump..

Raj, are these boards working with any size drives 3+TB's or is there BIOS upgrades..? as a novice to any HDD larger than 3TB, i have only read about having certain controller cards that come with the HDD's that you have use. and can one put these HDD's into a drive cage (a ICYDOCK 5 in 1 for instance) thanks

thank you very much for the full explanation.. i have looked here http://lime-technology.com/wiki/index.php?title=UnRAID_Manual#Allocation_method and have not seen an explanation on reserve space.. so thanks once again

i thought high water takes care of this automagically.... ?

so... then for high water there is no worry about free space ?

i have seen several threads about free space can someone PLEASE put this to bed with a best practice guide for the different types of allocation methods

just started testing the new version have been on 4.x for over 6 months and thought time to start testing... and i could not have said it any better myself.. thanks for all the hard work, look forward to the v5 final with your extensions...

just started testing the new version have been on 4.x for over 6 months and thought time to start testing... and i could not have said it any better myself.. thanks for all the hard work, look forward to the v5 final with your extensions...

if i may i think the greens are magnificent, please if you can give the non coders like me a way to change the colors back to how it was IF you do change them.. )... thanks

+1

i am not doubting what you said, it's just not written into law (FAQ or best practices with unRAID) anywhere.... (or did i miss it.?)

No, it indicates exactly the same thing. It indicates the share will not reserve any free space on any disk it uses. It might result in a file being created where there is insufficient space to hold it in its entirety and an out-of-space error when there is sufficient space on other drives. so for those of us that need a recap ... it IS recommended to have a free space on each disk or you will get and out of space error if certain disks are full???... is it not intelligent (sorry maybe bad word) enough to make sure this does not happen?