August 28, 20169 yr Hello everyone, System setup: i'm relativly new/unexpierenced to unraid. I set up a free-licence unraid v5 server(1 parity(2TB) aka disk1 - 1 data disk(2TB) aka disk2) a year ago, it worked fine. A few months back i bought my basic unraid v6 license. The Upgrade-Guide from unraid v5 to v6 in this forum didn't worked for me. So i started to setup a new unraid v6 server from scratch. The old data drive wouldn't be recognised under unraid v6 and the webui is saying: "Clear will completely clear (set to zero) the new disk. Once clear completes, the array may be Started, expanding the array to include the new disk. Caution: any data on the new disk will be erased! If you want to preserve the data on the new disk, reset the array configuration and rebuild parity instead. " Here's my problem: I want to save my unraid v5 disk2 files to an external disk, format the disk2 within the new setup unraid v6 server and put my files back on the server. Therefore i need a way to mount my disk2 (unraid v5 disk) on my win10 machine to copy my files to the external drive. Is there an easy way to mount it under win10? How can i do it/any guides? (Old guides talking about reset the parity disk, but didn't saw that feature in unraid v6) I tried an old wintech sata-to-usb-interface, but i can't mount it like that. Thanks for your help in advance! P.S. I attatched the unraid-diagnostic zip file. Pics of disk2 are in the following post! unraid-diagnostics-20160828-0916.zip
August 28, 20169 yr Community Expert In your OP you talk about parity aka disk1 and 1 data aka disk2. Parity is actually disk0 and the first data disk is disk1. This is the way unRAID refers to them and calling them disk1 and disk2 as you did can only lead to confusion. The best way to refer to specific disk drives is by their serial number. It is sometimes useful to shorten that to the last 4 characters as that is typically enough to uniquely identify a disk. From your syslog: Aug 28 09:11:14 Tower kernel: md: import disk0: [8,32] (sdc) WDC_WD20EFRX-68AX9N0_WD-WMC300307801 size: 1953514552 Aug 28 09:11:14 Tower kernel: md: import disk1: [8,64] (sde) WDC_WD10EALX-009BA0_WD-WMATR1286296 size: 976762552 Aug 28 09:11:14 Tower kernel: md: import disk2: [8,16] (sdb) WDC_WD20EARX-00PASB0_WD-WCAZAH575172 size: 1953514552 So you have: 2TB Parity (disk0) ending in 7801 1TB disk1 ending in 6296 2TB disk2 ending in 5172 The screenshots seem to refer to disk2-5172. PIC 2 shows that disk shouldn't be used in unRAID due to its bad SMART. Is that the disk you want to get the data from? unRAID uses filesystems that cannot be read by Windows without installing some other software so we won't take that approach for now. Your syslog indicates you added disk2 after you already had the parity array established. It wants to clear disk2 so parity will remain valid. Since you shouldn't be using that disk anyway it probably makes sense to try to copy the data from the disk to disk1 (if it has enough space). Instead of assigning that disk to your array, you should use the Unassigned Devices plugin to mount it outside the array and copy the data that way. See search tips in my sig. There are other possible approaches to this including New Config and rebuilding that disk to another but we should really get some more clarity before we discuss them. Please clarify what exactly you want to do and we can tell you how to get there. Don't do anything else without further instructions or you may lose that data.
August 28, 20169 yr Community Expert There is also another disk in your syslog and SMART Aug 28 09:16:59 Tower emhttp: WDC_WD1002FAEX-00Y9A0_WD-WMAW30930095 (sdf) 976762584 but it hasn't been assigned. What do you want to do with that disk?
October 5, 20169 yr Author Excuse me, my mistake. This weekend i can finally work on my server again. It will re upload my syslog. Just like i had it, just 2 disks. Gesendet von iPhone mit Tapatalk
October 31, 20169 yr Author Here's my unraid diagnostics. Like it was on unraid v5 setup. Parity: 2TB WD RED (WDC_WD20EFRX-...) Data: 2TB WD Green (WDC_WD10EALX-...) The data drive is the one i can't loose, so i'll have to try to save it to an external drive or s.th. similar.(looking into "trurl's" guide) unraid-diagnostics-20161030-1044.zip
October 31, 20169 yr Community Expert Here's my unraid diagnostics. Like it was on unraid v5 setup. Parity: 2TB WD RED (WDC_WD20EFRX-...) Data: 2TB WD Green (WDC_WD10EALX-...) The data drive is the one i can't loose, so i'll have to try to save it to an external drive or s.th. similar.(looking into "trurl's" guide) Your latest description doesn't match the drives in your screenshot or in your diagnostics. The missing drive in the screenshot is a 1TB serial ending 6296. That drive does not appear in syslog or smart. There is a 2TB unassigned drive in syslog and smart. Do you want to rebuild the missing 1TB onto the unassigned 2TB? That unassigned 2TB drive has SMART issues and I don't recommend using it in unRAID. Or do you instead want to get the data from the unassigned 2TB? If so what about the missing disk1? Please clarify.
October 31, 20169 yr I set up a free-licence unraid v5 server(1 parity(2TB) aka disk1 - 1 data disk(2TB) aka disk2) a year ago, it worked fine. trurl's advice was dead on, and I'm afraid your renaming of the drives (parity as disk 1 and Disk 1 as disk2) may have confused your own self as well. Your first diagnostics show your parity drive (7801) assigned correctly, but your original Disk 1 (5172) is assigned to Disk 2, and a new 1TB drive (6296) assigned to Disk 1, and that has probably ruined your parity. But all is not lost, just run the 'New config' tool from the Tools menu, and ONLY assign 5172 to Disk 1, and don't assign a parity drive. If you wish you can assign another drive, so you can copy the data to it, perhaps assign 6296 to Disk 2. This should allow you to read 5172 (your original Disk 1 that you called disk2), and copy the data to 6296. Be warned however, that as trurl said, 5172 is bad and getting worse, numerous bad sectors, so you may have trouble copying some files. A few months back i bought my basic unraid v6 license. The Upgrade-Guide from unraid v5 to v6 in this forum didn't worked for me. I'm curious what didn't work for you. I can see you assigned the wrong drive, and once that happened, you could not have assigned the correct drive without doing a New config, basically starting over. Was that possibly the problem? So i started to setup a new unraid v6 server from scratch. The old data drive wouldn't be recognised under unraid v6 and the webui is saying: "Clear will completely clear (set to zero) the new disk. Once clear completes, the array may be Started, expanding the array to include the new disk. Caution: any data on the new disk will be erased! If you want to preserve the data on the new disk, reset the array configuration and rebuild parity instead. " Here's my problem: I want to save my unraid v5 disk2 files to an external disk, format the disk2 within the new setup unraid v6 server and put my files back on the server. Therefore i need a way to mount my disk2 (unraid v5 disk) on my win10 machine to copy my files to the external drive. Is there an easy way to mount it under win10? How can i do it/any guides? (Old guides talking about reset the parity disk, but didn't saw that feature in unraid v6) I tried an old wintech sata-to-usb-interface, but i can't mount it like that. I see you were able to see the drive in Windows 10, but you would have had to install a ReiserFS driver, before you could actually see the files on it.
November 3, 20169 yr Author Here's my unraid diagnostics. Like it was on unraid v5 setup. Parity: 2TB WD RED (WDC_WD20EFRX-...) Data: 2TB WD Green (WDC_WD10EALX-...) The data drive is the one i can't loose, so i'll have to try to save it to an external drive or s.th. similar.(looking into "trurl's" guide) Your latest description doesn't match the drives in your screenshot or in your diagnostics. The missing drive in the screenshot is a 1TB serial ending 6296. That drive does not appear in syslog or smart. There is a 2TB unassigned drive in syslog and smart. Do you want to rebuild the missing 1TB onto the unassigned 2TB? That unassigned 2TB drive has SMART issues and I don't recommend using it in unRAID. Or do you instead want to get the data from the unassigned 2TB? If so what about the missing disk1? Please clarify. my fault, see attachment! I want to save my data from the 2TB WD Green(WDC_WD10EALX-...) unassigned drive you see in the syslog and smart logs. I dont really know the best way to that,... The 1TB disk i pulled out of the system to get the original setup of my server (one 2TB WD Red as parity, one 2TB WD Green as data) For me it seems like after pulling out my 2TB WD Green and using a 1TB WD Drive, my server made a new parity... So now it's looking for the 1TB Drive... My next step ist to put my server in its original setup, let the parity do it's thing. That should be fine or not?
November 3, 20169 yr Community Expert Still confused I want to save my data from the 2TB WD Green(WDC_WD10EALX-...) unassigned drive you see in the syslog and smart logs. I dont really know the best way to that,...WDC WD10EALX-whatever is not a 2TB drive, it is a 1TB drive, and it would be better as I mentioned to refer to the last 4 characters of the serial, since many drives will be identical for the first many characters. The 1TB disk i pulled out of the system to get the original setup of my server (one 2TB WD Red as parity, one 2TB WD Green as data) For me it seems like after pulling out my 2TB WD Green and using a 1TB WD Drive, my server made a new parity... So now it's looking for the 1TB Drive... This does not make any sense either. The only way you would get unRAID to "made a new parity" is by setting a new config and letting it build parity, which would have taken a noticeably long time. My next step ist to put my server in its original setup, let the parity do it's thing. That should be fine or not? I don't have any idea what you mean by "let the parity do it's thing". Maybe you don't either. The latest screenshot is showing 7801 as parity which matches what we already saw. But I don't think we can assume anything about parity without a very clear and detailed description of how you got to this point. Probably best to just concentrate on the data disks. Which drives exactly do you have data on that you want to keep (please specify last 4 digits of serial for each)? Are all the drives you have data on that you want to keep actually connected to your server in the latest screenshot? The latest screenshot is showing a 1TB drive ending 6296 as missing, and it has been replaced with a 2TB drive ending 5172, which I think may be the drive you are talking about trying to get the data from. As already mentioned, that disk has problems and should not be used in the array again, but it might be possible to copy the data from it. So, assuming 5172 is the 2TB drive that you want to get the data from, what about the missing 1TB drive 6296? Does it also have data on it that you want to keep?
November 3, 20169 yr Author Yes, your right about the WD 2TB drive ending ... 5172. Thats the drive my data is on and which i need to save. My idea was to put an the WD 1TB Drive (...6296) seen in my system and copy my files from ...5172 to the ...6296 drive, like you asssumed.
November 3, 20169 yr Community Expert No, it's complety wiped. Should i pre-format it? How would you do that? Format means "write an empty filesystem to this disk". That is what it has always meant in every operating system you have ever used. What filesystem would you format it to? You must let unRAID format any disk it will use in the array or cache. You aren't going to be able to do that without setting a new config. Is the 2TB disk attached? Set disk1 slot to unassigned and see if it will let you start the array.
November 4, 20169 yr Community Expert Parity is basically meaningless at this point, since it is either based on the 2TB drive that's failing, or it's based on the 1TB drive that has no data on it, and in any case we don't know which. Go to Tools - New Config. Assign the 1TB drive 6296 to disk1. Assign the 2TB drive 5172 to disk2. Don't assign any drive to parity. Then post a screenshot showing Array Devices and Array Operation.
November 7, 20169 yr Community Expert Looks like the 1TB already has an empty XFS filesystem on it, so unRAID must have formatted it at some point. Unfortunately, it doesn't think the 2TB drive with your data has a filesystem, so it is offering to format it. DON'T DO IT. Do you know what its filesystem is supposed to be?
November 7, 20169 yr Looks like the 1TB already has an empty XFS filesystem on it, so unRAID must have formatted it at some point. Unfortunately, it doesn't think the 2TB drive with your data has a filesystem, so it is offering to format it. DON'T DO IT. Do you know what its filesystem is supposed to be? Since the disk was used in V5, it should be ReiserFS. I'd try manually setting the file system type in the disk setting to Reiser and see if it mounts.
November 7, 20169 yr Community Expert Looks like the 1TB already has an empty XFS filesystem on it, so unRAID must have formatted it at some point. Unfortunately, it doesn't think the 2TB drive with your data has a filesystem, so it is offering to format it. DON'T DO IT. Do you know what its filesystem is supposed to be? Since the disk was used in V5, it should be ReiserFS. I'd try manually setting the file system type in the disk setting to Reiser and see if it mounts. Sounds reasonable. You will have to Stop then click on Disk 2 to get to the page where you can choose its filesystem. Post another screenshot if you get stuck.
November 9, 20169 yr Author I tried it out(ReiserFS,see screenshots), It's says: "unmountable Disk" After that i tried to mount it as the other two disk formats(xfs and the third one), same result:"unmountable Disk"
Archived
This topic is now archived and is closed to further replies.