Created attachment 1196046 [details] rdsosreport (remove rhgb quiet and insert rdshell rdinitdebug) Description of problem: installed F25 Alpha to an 64GB usb 3.0 flash drive without any problem. Tried to boot an Acer E15 E5-571G Laptop (8GB Ram) resulting in dracut error. I attach the rdsosreport.txt. For producing this report I deleted rhgb quiet and inserted rdshell rdinitdebug. Version-Release number of selected component (if applicable): F25 Alpha publicly available How reproducible: install F25 Alpha to an usb 3.0 flash medium Steps to Reproduce: 1.install F25 Alpha to an usb 3.0 flash medium 2.boot pc 3. Actual results: dracut error Expected results: successful boot Additional info:
lrwxrwxrwx 1 root 0 9 Aug 30 19:48 usb-_USB_FLASH_DRIVE_19740D000479-0:0 -> ../../sdb lrwxrwxrwx 1 root 0 10 Aug 30 19:48 usb-_USB_FLASH_DRIVE_19740D000479-0:0-part1 -> ../../sdb1 Is the flash drive this one? ID_FS_UUID=0220330d-c3b0-45ab-8c85-b2d293061a31 ID_FS_UUID_ENC=0220330d-c3b0-45ab-8c85-b2d293061a31 ID_FS_TYPE=ext4 ID_FS_PARTUUID=ac102ea2-01 It's only has one ext4 partition.
I know, that the production does not work correctly, the size of written data is only about 1.1GB, that's my problem with Alpha trying to install on a 64GB USB 3.0 stick, Fxx up to F24 it was possible to run Fedora on an USB flash drive. I can not say if the same problem would appear with an installation trial on an external harddrive, currently I have none to try. If dracut is the wrong place, where to put this bug?
just found an old 160GB PATA disk, connected it with an USB 2.0 adapter as external disk to my laptop. Installation of F25 Alpha does not work, there are partitions (i.e. home/joerg) to see, also a "code partition" with 1.1GB. If neccessary I can try to install again, and if I you say, what to log during installation, I willgive the installation log. It is in this case not possible to start boot with this external Pata disk, but I can look into it with F24. Therefore I can also copy logs from the external disk, If I would know, what to look for. This problem is not related to flash media exclusively, it seems to be a problem related to USB 3.0, USB 2.0.
Should be routed to Anaconda. In my opinion it's blocking for Beta. Anaconda can not produce a running build on media connected via USB 2.0 and USB 3.0.
Well the problem is cmdline says root=/dev/mapper/fedora-root, and then it can't be found by dracut, which is true because sdb1 is ext4 not LVM. So at the moment this doesn't appear to be a dracut bug. The questions are, what is the selected installation layout, does the installer actually produce that layout, and does the installer configure the bootloader correctly for the produced layout?
Created attachment 1206475 [details] liveuser anaconda.log after installation Tried again to install, F25 Alpha Workstation, Alpha public delivery, here the anaconda.log copied from the liveuser
Please answer the questions in comment 5. I have no idea what you're doing in the installer so I have no idea how to try to reproduce the problem.
The way of installation was Automatic Partitioning with reclaim space on the installation medium. I documented this in a further installation trial with screenshots (layoutOfLastInstallTrial.png, and step1.png to step5.png). In screenshots because my "Fedora English" is not so good.
Created attachment 1206581 [details] Starting layout of the installation medium
Created attachment 1206582 [details] step 1, choose automatic partioning with reclaim space
Created attachment 1206583 [details] step 2, old memory layout of the installation medium, result of the last installation trial
Created attachment 1206584 [details] step 3, reclaim space, delete old partitions
Created attachment 1206585 [details] step 4, start of installation
Created attachment 1206586 [details] step 5, installation done, according to this report ok, but does not work
tried now wether my installation way causes the error: automatic partitioning with reclaim space. But it isn't, made the installation medium "clean" and used manual partitioning -> same result shown in the dracut error reporting.
I should note, that the installation with manual partitioning installed showed after installation the same partitions as was, when I had chosen automatic partitioning with reclaim space. My wanted partitioning was ignored.
Same Anaconda problem with F25 Beta 1.1.. I hope this problem will be solved for Final. A suggestion is to update the test lists, to enable that problems like this can be solved in F26 Alpha.
Hi, by case I tried to install F25 Beta in legacy mode on an 64GB flash medium. And surprise it works. This means Anaconda problem when installing F25 on an USB flash medium in EFI mode, but in Legacy mode ok. I run an Acer laptop with Win 8.1 on the internal disk. I think this is good news to find a way to solve this EFI - Anaconda problem. Kind regards ( This is a copy of a thread in the test lists)
Hi Richard, this is strange. I am now in F25 EFI on an 32GB USB 3.0 flash medium. I have made the following tests with the 64GB USB 3.0 flash medium (both 32GB and 64GB are Sandisk Ultra) Legacy mode: F25 and F24 installation ok EFI mode: F25 to F22 dracut error, no installation possible on the 64GB stick and F25 installation ok on the 32GB stick What is confusing for me with F25 Alpha I tried to install on an external Pata disk (some hundred GB) connected with an usb adapter (I use always used internal disks from ebay - one of my hobbies is collecting TV films, a disk space consuming job), there also no "EFI installation" was possible. I need now an other TB disk for my hobby, and will it first use for an F25 installation test, but this will take some days to get it. Strange results, the 64GB stick should be ok, because the "Legacy installation" works. I copy this mail to the 2 Bug reports related to Anaconda. Kind regards Joerg
Hi, I want to tell, that with the new 64GB Sandisk Ultra stick sent just from Sandisk, the F25 Beta installation is ok. From the talks with Sandisk, I feel that Sandisk knew the reason, why the installation failed with the previous stick, my idea the firmware of the stick has changed before the production of the current one, but who knows except Sandisk. Kind regards