[fedora-arm] Re: Installer failure on SSd drive

----- Original Message ----- > > On 12/5/18 1:05 PM, Robert Moskowitz wrote: >> >> On 12/5/18 1:01 PM, Robert Moskowitz wrote: >>> ===================================================== >>> = Selected Image: >>> = /home/rgm/arm/Fedora-Server-armhfp-29-1.2-sda.raw.xz >>> = Selected Media : /dev/sdc >>> = U-Boot Target : none >>> ===================================================== >>> >>> ***************************************************** >>> ***************************************************** >>> ******** WARNING! ALL DATA WILL BE DESTROYED ******** >>> ***************************************************** >>> ***************************************************** >>> >>>  Type 'YES' to proceed, anything else to exit now >>> >>> = Proceed? yes >>> = Writing: >>> = /home/rgm/arm/Fedora-Server-armhfp-29-1.2-sda.raw.xz >>> = To: /dev/sdc .... >>> 0+337225 records in >>> 0+337225 records out >>> 3242196992 bytes (3.2 GB, 3.0 GiB) copied, 148.012 s, 21.9 MB/s >>> = Writing image complete! >>> mount: /tmp/root: wrong fs type, bad option, bad superblock on >>> /dev/sdc3, missing codepage or helper program, or other error. >>> Error: mount /dev/sdc3 /tmp/root failed >>> >>> what does this mean?  The SSD was in a USB/sata adapter that I have >>> used many times in the past.  I unplugged and replugged the USB and >>> now all 3 partitions are showing and I am using gparted to enlarge >>> the / partition.  But it came up on sdd where before it was on sdc. >>> >> gparted failed to grow the partition. >> >> mount: /tmp/gparted-n5hfh1: wrong fs type, bad option, bad superblock >> on /dev/sdd3, missing codepage or helper program, or other error >> >> So probably a problem with the SSD? >> > same failure with a HD.  I am going to try a different adapter. > > mount: /tmp/root: wrong fs type, bad option, bad superblock on > /dev/sdd3, missing codepage or helper program, or other error. > Error: mount /dev/sdd3 /tmp/root failed What version of the arm-image-installer is this? I fixed a few things in the latest (arm-image-installer-2.10-1). I have seen that when writing out the server image repeatedly, a reboot should 'fix' it.