cypres0099 Posted January 14, 2018 Share Posted January 14, 2018 I was just logging in to do a routine check on the system when I noticed that Disk 1 is giving me the error "Unmountable: Invalid Partition". I didn't receive any error alerts or anything. I don't think I've changed anything since it was working correctly. I'm currently checking parity since it has been fully checked since November. Any idea what might have happened here? Can I just format the drive and add it to the array to rebuild? Link to comment
JorgeB Posted January 14, 2018 Share Posted January 14, 2018 Don't format, please post your diagnostics: Tools -> Diagnostics Link to comment
cypres0099 Posted January 14, 2018 Author Share Posted January 14, 2018 I appreciate the emphatic response Here's the diagnostic file. Thanks for jumping on this so quickly. mongo-diagnostics-20180114-1502.zip Link to comment
bonienl Posted January 14, 2018 Share Posted January 14, 2018 NO. Do not format, you will loose all data on that disk. Next to diagnostics, you can do the following 1. Start your array in maintenance 2. From Main page click on disk2 3. Perform a file system check and repair (enable HELP for more instructions) Link to comment
cypres0099 Posted January 14, 2018 Author Share Posted January 14, 2018 Running a check now. Link to comment
JorgeB Posted January 14, 2018 Share Posted January 14, 2018 Invalid partition is not the error I would expect for filesystem corruption, do you have any idea how long it's been like that? Did you rebuild that disk recently? The release you're on has a bug were the partition isn't correctly created on a rebuild when using a clean disk. Link to comment
bonienl Posted January 14, 2018 Share Posted January 14, 2018 Assuming you get everything up and running again. Next, it is recommended to convert reiserFS to XFS when using unRAID6. Link to comment
cypres0099 Posted January 14, 2018 Author Share Posted January 14, 2018 1 minute ago, johnnie.black said: Invalid partition is not the error I would expect for filesystem corruption, do you have any idea how long it's been like that? Did you rebuild that disk recently? The release you're on has a bug were the partition isn't correctly created on a rebuild when using a clean disk. I added the disk like a month ago. I just noticed the problem today. 1 minute ago, bonienl said: Assuming you get everything up and running again. Next, it is recommended to convert reiserFS to XFS when using unRAID6. It's still running the check. But it will hopefully be fixed after the check is done? To convert everything to XFS, I'm assuming I'll hookup an external drive and transfer everything off a single disk, format, then transfer it back on? Repeat for all disks? Link to comment
JorgeB Posted January 14, 2018 Share Posted January 14, 2018 The filesystem check won't fix the problem, you need to upgrade to latest and rebuild the disk again. Link to comment
cypres0099 Posted January 14, 2018 Author Share Posted January 14, 2018 Ok, check is finished. 33 minutes ago, johnnie.black said: The filesystem check won't fix the problem, you need to upgrade to latest and rebuild the disk again. So you're saying I need to update to the latest version of Unraid before moving on? Link to comment
JorgeB Posted January 14, 2018 Share Posted January 14, 2018 Yes, you should have updated long ago, you're using a 3 month old rc. Upgrade to v.6.4 stable, reboot, unassign disk2, start the array, emulated disk2 should now mount (unless there are other issues), stop the array, re-assign disk2, start the array to rebuild again. Link to comment
cypres0099 Posted January 14, 2018 Author Share Posted January 14, 2018 Followed your instructions and rebuilding now. You're a legend! Link to comment
Recommended Posts
Archived
This topic is now archived and is closed to further replies.