jaj08 Posted January 6, 2011 Share Posted January 6, 2011 Its a new year, so I thought I would start it off by using Unmenu and kicking off some file system checks on each Data drive. But I hit drive #6 and I got the following error. Checking /dev/md6 (/dev/sdg) Sorry, not coded to handle ddf_raid_member on /dev/md6 /dev/md6 mounted on /mnt/disk6 Any ideas? Quote Link to comment
Joe L. Posted January 6, 2011 Share Posted January 6, 2011 Its a new year, so I thought I would start it off by using Unmenu and kicking off some file system checks on each Data drive. But I hit drive #6 and I got the following error. Checking /dev/md6 (/dev/sdg) Sorry, not coded to handle ddf_raid_member on /dev/md6 /dev/md6 mounted on /mnt/disk6 Any ideas? It's your server. Apparently, ddf_raid_member is what is being returned as the file system type when you run vol_id /dev/sdg1 on your server. unMENU is expecting it to say something like this: root@Tower:# vol_id /dev/sdd1 ID_FS_USAGE=filesystem ID_FS_TYPE=reiserfs ID_FS_VERSION=3.6 ID_FS_UUID=983acc60-411e-4064-b9a1-49cf7b959588 ID_FS_UUID_ENC=983acc60-411e-4064-b9a1-49cf7b959588 ID_FS_LABEL= ID_FS_LABEL_ENC= Quote Link to comment
jaj08 Posted January 6, 2011 Author Share Posted January 6, 2011 Weird, wonder how this one disk got setup differently from all the others. 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.