berta123 Posted June 16, 2023 Share Posted June 16, 2023 Hi all, Noticing this error after a power outage. I say noticing because I've been really busy for the last few weeks since I added this drive and it may have been there the whole time. Or maybe it's new. Honestly not sure. At any rate my last added and newest drive in the array is saying Unmountable: unsupported or no file system even when booted into maintenance mode. I'd love some help on next steps? I started to run xfs_repair but then I noticed the drive is set to auto for a file system so I wasn't even sure that was right. Diags attached. Thanks! beta-diagnostics-20230615-2105.zip Quote Link to comment
JorgeB Posted June 16, 2023 Share Posted June 16, 2023 Log is full of unrelated spam, reboot and post new diags after array start. Quote Link to comment
berta123 Posted June 16, 2023 Author Share Posted June 16, 2023 Attached below. Thanks for taking a look @JorgeB beta-diagnostics-20230616-1604.zip Quote Link to comment
JorgeB Posted June 17, 2023 Share Posted June 17, 2023 Looks like disk12 was never formatted, post output of: fdisk -l /dev/sdn Quote Link to comment
berta123 Posted June 17, 2023 Author Share Posted June 17, 2023 (edited) Do I need to be in a certain mode (maintenance etc)? From when the array is started: Disk /dev/sdn: 7.28 TiB, 8001563222016 bytes, 15628053168 sectors Disk model: ST8000NM017B-2TJ Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt Disk identifier: F8C062CD-3423-4A8F-BAEE-836784168F0B Device Start End Sectors Size Type /dev/sdn1 64 15628053134 15628053071 7.3T Linux filesystem Edited June 17, 2023 by berta123 Quote Link to comment
JorgeB Posted June 17, 2023 Share Posted June 17, 2023 hmm, there is a partition there, try this, stop the array, click on that disk, change fs from auto to xfs, start array and post new diags. Quote Link to comment
berta123 Posted June 17, 2023 Author Share Posted June 17, 2023 Updated diagnostics attached. The disk also has a new error message: "Unmountable: Wrong or No Filesystem" beta-diagnostics-20230617-0944.zip Quote Link to comment
JorgeB Posted June 17, 2023 Share Posted June 17, 2023 The partition doesn't respond to any of the supported filesystem, and forcing xfs also doesn't find anything, most likely there never was an Unraid filesystem in that disk, but cannot say for sure, do you have a way of checking if the array is showing all the data you expect? Quote Link to comment
berta123 Posted June 17, 2023 Author Share Posted June 17, 2023 Not really, but the disk is fairly new and 90% of data on the server is entirely replaceable (backups etc) so perhaps the best path is to just wipe the disk and start over? I assume the double parity doesn’t help in this case? Quote Link to comment
Solution JorgeB Posted June 17, 2023 Solution Share Posted June 17, 2023 4 hours ago, berta123 said: I assume the double parity doesn’t help in this case? It doesn't, if you think there's no data there probably best just to format it. Quote Link to comment
berta123 Posted June 18, 2023 Author Share Posted June 18, 2023 4 hours ago, JorgeB said: It doesn't, if you think there's no data they’re probably best just to format it. Ok I’m going to reformat. Maybe as a single disk ZFS with 6.12! Can you give any ideas of what to do to protect against this in the future (besides a full backup which I already do to stuff that is not replaceable) Quote Link to comment
itimpi Posted June 18, 2023 Share Posted June 18, 2023 6 hours ago, berta123 said: Ok I’m going to reformat. Maybe as a single disk ZFS with 6.12! Can you give any ideas of what to do to protect against this in the future (besides a full backup which I already do to stuff that is not replaceable) From my reading of this thread it is not clear there ever really was a problem, or if you had just never got around to formatting the drive after adding it to Unraid (as new drives always show as unmountable until they are formatted from within Unraid). Quote Link to comment
berta123 Posted June 18, 2023 Author Share Posted June 18, 2023 12 minutes ago, itimpi said: From my reading of this thread it is not clear there ever really was a problem, or if you had just never got around to formatting the drive after adding it to Unraid (as new drives always show as unmountable until they are formatted from within Unraid). Yes that certainly is a possibility, but as evidenced by this forum this appears to be something that can happen and I’m not sure I quite understand why parity is no help in this situation. Could I have not just popped out the “unformatted” disk and replaced it with a new disk and had it rebuild the “failed” (unformatted) drive? Quote Link to comment
itimpi Posted June 18, 2023 Share Posted June 18, 2023 33 minutes ago, berta123 said: Could I have not just popped out the “unformatted” disk and replaced it with a new disk and had it rebuild the “failed” (unformatted) drive? You could have but no point as a format is MUCH quicker than a rebuild, and it would still need to be formatted afterwards anyway as a rebuild does not clear an unmountable status. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.