Hello, I just wanted to see if anyone has ran into this before. I have my existing bulk media server running on Ubuntu 14.04.4 64-bit server. Last night, I shut it down and removed my current OS drive and did a fresh 16.04 install on an Intel S3700 200GB SSD I had laying around. I have 24 spinning disks in the chassis (Norco 4224) hooked up to (3) Dell H310's flashed to the latest P20 IT firmware. This is the system I was working on.
The install went fine, an when I booted it up the first time, I did my usual apt-get update && apt-get dist-upgrade. I noticed when it updated to the latest kernel and ran update-grub that it was spewing errors about trying to mount all my unmounted data disks and not recognizing the filesystem type (all 24 spinners were unmounted and not even in /etc/fstab at this point).
After doing the update, I added the disks to /etc/fstab and rebooted. I was greeted by 24 errors about none of the filesystems being recognized. Want to feel your heart skip a beat? That's where I was... So, I tried to manually mount a couple of the disks with mount /dev/sdc1 /mnt/test and mount -t ext4 /dev/sdc1 /mnt/test all to be greeted with filesystem not recognized. Next, I tried to make sure the filesystem's were intact
fsck.ext4 -v /dev/sdc1 returned a clean ext4 filesystem and ensured that the superblocks were okay (I did verify backups were present with mke2fs -n /dev/sdc1 as well).
So, the filesystems "appear" okay, but are not mountable. Next, I happenned to run and fdisk -l (not the best way to look at GPT labeled disks), and noticed that all of my disks had a mix of labels from Linux Filessytem to msdos. So, I confirmed this in gparted and saw the same weirdness?!?! I really didn't want to have to re-label each disk as gpt in gparted and restore the partition, but it was looking like that was my only recourse. On a whim, I shut down the system and pulled out the S3700 and put back in my old 14.04.4 server install. When it booted, everything mounted automatically and all of the disks showed gpt partitions with no issues.
This whole endeavor, left a very bad taste in my mouth about 16.04. Has anyone seen this or have any ideas what steps I should try to troubleshoot this?
Sorry, for the wall of text.
The install went fine, an when I booted it up the first time, I did my usual apt-get update && apt-get dist-upgrade. I noticed when it updated to the latest kernel and ran update-grub that it was spewing errors about trying to mount all my unmounted data disks and not recognizing the filesystem type (all 24 spinners were unmounted and not even in /etc/fstab at this point).
After doing the update, I added the disks to /etc/fstab and rebooted. I was greeted by 24 errors about none of the filesystems being recognized. Want to feel your heart skip a beat? That's where I was... So, I tried to manually mount a couple of the disks with mount /dev/sdc1 /mnt/test and mount -t ext4 /dev/sdc1 /mnt/test all to be greeted with filesystem not recognized. Next, I tried to make sure the filesystem's were intact
fsck.ext4 -v /dev/sdc1 returned a clean ext4 filesystem and ensured that the superblocks were okay (I did verify backups were present with mke2fs -n /dev/sdc1 as well).
So, the filesystems "appear" okay, but are not mountable. Next, I happenned to run and fdisk -l (not the best way to look at GPT labeled disks), and noticed that all of my disks had a mix of labels from Linux Filessytem to msdos. So, I confirmed this in gparted and saw the same weirdness?!?! I really didn't want to have to re-label each disk as gpt in gparted and restore the partition, but it was looking like that was my only recourse. On a whim, I shut down the system and pulled out the S3700 and put back in my old 14.04.4 server install. When it booted, everything mounted automatically and all of the disks showed gpt partitions with no issues.
This whole endeavor, left a very bad taste in my mouth about 16.04. Has anyone seen this or have any ideas what steps I should try to troubleshoot this?
Sorry, for the wall of text.
