May 24, 20188 yr Hey there, So I was having some HDD issues so I took out the HDD, I didn't stop the array and remove it first... my bad. When I rebooted it with the new HDD I assigned it to the slot and had it rebuild. After it was done nothing was mounted, and it had option to format. So I did that (it's a new drive, still have the old one with data). Which did nothing for me. Now it's at the point where I can't stop the array to change drives, I click and it does it thing but I don't get the usual window where you can assign/unassign drives. Not sure where to go from here, all the other drives seem to be working, and I can access the data fine. Thanks in advance for any help. hades-diagnostics-20180524-0819.zip
May 24, 20188 yr Community Expert 2 hours ago, dfm1980 said: So I was having some HDD issues so I took out the HDD, I didn't stop the array and remove it first... my bad. Really the first bad was not asking before doing anything. And attempting to format was also not the way forward. Hopefully the original disk can be read well enough to get something from it. Is the Unassigned Device in the screenshot the new disk or the original?
May 24, 20188 yr Author What did the format do? It was a new empty hard drive. The old disk was starting to throw errors, I can still access the data through it. The device in the screenshot is the new HDD.
May 24, 20188 yr Community Expert Format means "write an empty filesystem to this disk". That is what it has always meant in every operating system you have ever used. unRAID treats this write exactly as it does any other, by updating parity. If you format a disk in the parity array, parity will agree that the disk contains an empty filesystem, so if you then attempt to rebuild the disk, you will get an empty filesystem. And just because the old disk was having errors doesn't mean there was anything wrong with the disk. Most of the time it is just a bad connection, sometimes a bad cable or controller, rarely a bad disk. And if unRAID had not actually disabled the disk a rebuild wasn't even indicated without further evidence of an actual disk problem. You rebooted before taking these diagnostics and we can't tell anything about what happened before. Also, you are running a very old version of unRAID. Not sure that version even had Notifications. I suspect it did but you probably didn't have them setup. SMART for all disks looks OK. The screenshot shows unRAID still offering to format the unmountable and missing (emulated) disk. So it is unclear what happened when you tried to format. Do you have backups of any important and irreplaceable files from that disk? The screenshot also shows the Stop button is disabled because you haven't checked the box to enable it. Could you maybe explain exactly what you mean by this part I have quoted below? 3 hours ago, dfm1980 said: I click and it does it thing
May 24, 20188 yr Community Expert 1 hour ago, dfm1980 said: The old disk was starting to throw errors, I can still access the data through it. Also, what exactly do you mean by the above? How are you accessing the data of the old disk? It isn't installed and the emulated disk is unmountable.
May 24, 20188 yr Author 4 minutes ago, trurl said: Format means "write an empty filesystem to this disk". That is what it has always meant in every operating system you have ever used. unRAID treats this write exactly as it does any other, by updating parity. If you format a disk in the parity array, parity will agree that the disk contains an empty filesystem, so if you then attempt to rebuild the disk, you will get an empty filesystem. And just because the old disk was having errors doesn't mean there was anything wrong with the disk. Most of the time it is just a bad connection, sometimes a bad cable or controller, rarely a bad disk. And if unRAID had not actually disabled the disk a rebuild wasn't even indicated without further evidence of an actual disk problem. You rebooted before taking these diagnostics and we can't tell anything about what happened before. Also, you are running a very old version of unRAID. Not sure that version even had Notifications. I suspect it did but you probably didn't have them setup. SMART for all disks looks OK. The screenshot shows unRAID still offering to format the unmountable and missing (emulated) disk. So it is unclear what happened when you tried to format. Do you have backups of any important and irreplaceable files from that disk? The screenshot also shows the Stop button is disabled because you haven't checked the box to enable it. Could you maybe explain exactly what you mean by this part I have quoted below? I know what formatting is, I'm not new to computers. I did have a screw up, now I'm trying to fix it. Yes the old disk was starting to fail. So I bought a new bigger one, to not only solve the disk problems, but to upgrade the storage in the array too. The smart test is passing because that's the new HDD. Yes, I have notifications set up. I can access the files outside of the array on another computer. Ya, I know you have to click the check box to get it to stop... I did solve that by disabling auto start, and can get on and assign HDDs again.
May 24, 20188 yr Author I didn't realize that formatting changed parity though. Thank you for that info, just trying to learn more about this since it's my first time having any trouble with it since I built it 7 years ago.
May 24, 20188 yr Community Expert Any write operation to a disk in the array updates parity. And everything except a read is a write. Delete writes the filesystem of the disk the file is deleted from, moving data to another disk is really just a copy then a delete from the source, and as mentioned, delete is a write. And format is a write, "write an empty filesystem". In addition to missing out on new features, there are even more serious problems with using a very old version of unRAID. You are missing numerous fixes, including security fixes. New versions provide better diagnostics. And perhaps most importantly, the helpful people on this forum aren't running the version you are running, and don't even remember it except in a very general way.
May 24, 20188 yr Community Expert 49 minutes ago, dfm1980 said: I know what formatting is, I'm not new to computers. Many people that have used computers for a while don't really know what formatting does. They think it is just what you do to a new disk. And many of the things people know about computers don't always apply to unRAID. This is why I often try to get them to clarify their posts. They think they know what they mean, but what they said is either impossible, or at least missing some crucial details.
May 25, 20188 yr Author 5 hours ago, trurl said: Many people that have used computers for a while don't really know what formatting does. They think it is just what you do to a new disk. And many of the things people know about computers don't always apply to unRAID. This is why I often try to get them to clarify their posts. They think they know what they mean, but what they said is either impossible, or at least missing some crucial details. I get that, but none of this is really helping me with a solution to my problem... this is why I usually try to figure things out on my own. I am asking for what to do next because I am trying not to lose my data at this point. I understand that Unraid is different, I've already admitted to my mistake, now I'm here asking for some help. Not sure why I'm getting the 3rd degree on it. You don't learn from things unless you screw them up. I've actually been away from home for 7 months. I guess my Unraid version will be slightly outdated, but that's not the issue I'm having. If you have a solution, please share it. Thanks.
May 25, 20188 yr Physically, where is the old disk? Still attached to the unraid box, or in another machine? 11 hours ago, dfm1980 said: I can access the data fine. Does this refer to the rest of your disks (expected) or the data on the troubled disk? 1 hour ago, dfm1980 said: I am asking for what to do next because I am trying not to lose my data at this point. So you can't access the data? If you can access it, first thing to do is back it up. Your screenshot doesn't show a disk assigned to slot 1, so when you say you assigned it and it rebuilt the disk, that was after you took the screenshot? Perhaps posting current screenshots and more information about exactly what is the current state of your array would be helpful. Right now it's very confusing trying to parse what happened and what the current situation is, and without accurate information telling you what to try is risky.
May 25, 20188 yr Author The old disk is out of the array, I can still access it in another machine, as well as the data on the array is still intact, the only thing that's missing is Disk 1. I do believe after playing with it more I am facing a DOA HDD. That's why I'm having trouble with the unmountable error, I did not preclear this one. I have ordered a new one. Disk 1 has the brand new 4TB HDD in it, that is apparently not working. I assigned it, and rebuilt it (or I thought anyways, as it didn't work) the screenshots are of the array as it is right now. Right now I'm assuming the solution is to get the new HDD in and rebuild, which will leave a blank HDD, because of the format I did and the parity change. I will just physically copy the old data back to it and rebuild parity and everything should be ok. But I'm no Unraid expert by any means.
May 25, 20188 yr If the new drive is DOA, that explains the Not installed message on the screenshot. It has nothing to do with the Unmountable file system and the inability to access the files on the emulated slot 1. At this point, since you have the original slot 1 drive safe and can read the data, there is no added risk to that data in trying to fix the unmountable file system on slot 1. If it were me, I'd physically remove the new hard drive from the system for now to prevent confusion, and follow the directions here. https://lime-technology.com/wiki/Check_Disk_Filesystems#Drives_formatted_with_ReiserFS_using_unRAID_v5_or_later I'm well aware the page starts out with a warning about not using this page to solve hardware errors. The Unmountable message is what this page deals with, the Not installed is the hardware issue that we will deal with when you rebuild with a new drive. If you can get the emulated file system fixed, then it will rebuild properly on the new drive. If you don't fix the filesystem, the newly rebuilt slot 1 drive will have the same Unmountable file system. Parity doesn't rebuild your files, it rebuilds the entire drive, corrupt filesystem and all. That's why formatting during the rebuild erases your files.
May 25, 20188 yr 16 hours ago, dfm1980 said: You don't learn from things unless you screw them up. By giving good descriptions and asking questions, you can learn from other peoples screw ups. That's way less costly. That's also why people spend time querying exactly what was done to systems or spends time writing very long and descriptive answers. This thread isn't just about you, even if it at this very moment relates to your unRAID problems. Google will continue to pick up this thread when other people has problems - then it helps if they can figure out if their problems matches your problem. Or if the suggested solutions in this tread seems appropriate for their problems.
May 26, 20188 yr Author On 5/25/2018 at 5:16 AM, jonathanm said: If the new drive is DOA, that explains the Not installed message on the screenshot. It has nothing to do with the Unmountable file system and the inability to access the files on the emulated slot 1. At this point, since you have the original slot 1 drive safe and can read the data, there is no added risk to that data in trying to fix the unmountable file system on slot 1. If it were me, I'd physically remove the new hard drive from the system for now to prevent confusion, and follow the directions here. https://lime-technology.com/wiki/Check_Disk_Filesystems#Drives_formatted_with_ReiserFS_using_unRAID_v5_or_later I'm well aware the page starts out with a warning about not using this page to solve hardware errors. The Unmountable message is what this page deals with, the Not installed is the hardware issue that we will deal with when you rebuild with a new drive. If you can get the emulated file system fixed, then it will rebuild properly on the new drive. If you don't fix the filesystem, the newly rebuilt slot 1 drive will have the same Unmountable file system. Parity doesn't rebuild your files, it rebuilds the entire drive, corrupt filesystem and all. That's why formatting during the rebuild erases your files. Thank you, I will try this. I did receive my new drive today. I'll install it after this.
May 28, 20188 yr Author On 5/25/2018 at 5:16 AM, jonathanm said: If the new drive is DOA, that explains the Not installed message on the screenshot. It has nothing to do with the Unmountable file system and the inability to access the files on the emulated slot 1. At this point, since you have the original slot 1 drive safe and can read the data, there is no added risk to that data in trying to fix the unmountable file system on slot 1. If it were me, I'd physically remove the new hard drive from the system for now to prevent confusion, and follow the directions here. https://lime-technology.com/wiki/Check_Disk_Filesystems#Drives_formatted_with_ReiserFS_using_unRAID_v5_or_later I'm well aware the page starts out with a warning about not using this page to solve hardware errors. The Unmountable message is what this page deals with, the Not installed is the hardware issue that we will deal with when you rebuild with a new drive. If you can get the emulated file system fixed, then it will rebuild properly on the new drive. If you don't fix the filesystem, the newly rebuilt slot 1 drive will have the same Unmountable file system. Parity doesn't rebuild your files, it rebuilds the entire drive, corrupt filesystem and all. That's why formatting during the rebuild erases your files. So, I tried what you suggested. This comes up - bad_indirect_item comes up about 1000 times Reiserfs journal '/dev/md1' in blocks [18..8211]: 0 transactions replayed Checking internal tree.. / 12 (of 16)/166 (of 170)bad_indirect_item: block 348 17: The item [2 4 0xf6c2d001 IND (1)] has the bad pointer (1) to the block (3523 21536) bad_indirect_item: block 34817: The item [2 4 0xf6c2d001 IND (1)] has the bad pointer (2) to the block (4117145929) bad_indirect_item: block 34817: The item [2 4 0xf6c2d001 IND (1)] has the bad pointer (3) to the block (2209470250) At the end this is displayed, block 34818: The level of the node (46551) is not correct, (1) expected the problem in the internal node occured (34818), who/ 13 (of 16)/ 1 (of 170) block 34822: The level of the node (56796) is not correct, (1) expected the problem in the internal node occured (34822), who/ 14 (of 16)block 34983: The level of the node (30374) is not correct, (2) expected the problem in the internal node occured (34983), whole subtree isfinished Comparing bitmaps..vpf-10640: The on-disk and the correct bitmaps differs. Bad nodes were found, Semantic pass skipped 3 found corruptions can be fixed only when running with --rebuild-tree ########### reiserfsck finished at Mon May 28 07:43:00 2018 ###########
May 30, 20188 yr Author So after --rebuild-tree and adding the new HD, it rebuilt everything it said. The new drive is empty tho? There doesn't appear to be anything missing.
Archived
This topic is now archived and is closed to further replies.