searching for porteus, device not ready, porteus data not found

Technical issues/questions of an intermediate or advanced nature.
Post Reply
rych
Samurai
Samurai
Posts: 147
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 4.0 64 LXDE
Location: NZ

searching for porteus, device not ready, porteus data not found

Post#1 by rych » 03 Mar 2019, 04:53

Booting from my new USB, after the initial menu, the screen shows
searching for porteus-v4.0-x86_64.cfg file
device not ready yet? delaying 6 seconds
At this moment when lucky it just goes through. But usually it times out and displays:
searching for porteus-v4.0-x86_64.cfg file
device not ready yet? delaying 1 seconds.
Porteus data not found.
I have to restart 3 or 4 times for `it` to be `found`.

The problem only happens on my work computers. My USB is a SanDisk (Ultra USB 3.0) -- I've heard of problems with booting from these USBs. Moreover, it has 2 partitions: porteus ext4 following an NTFS partition. You may think it's not meant to work. But it does on some machines, and/or on others after a multiple restart.

So I'm interested in your advice: for example how to increase the 6s. delay above -- no use in the `delay` cheat code inside porteus-v4.0-x86_64.cfg as it's on the very partition (?) porteus boot is having difficulty finding. Or anything else?

User avatar
Ed_P
Contributor
Contributor
Posts: 4576
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

searching for porteus, device not ready, porteus data not found

Post#2 by Ed_P » 03 Mar 2019, 06:11

Any possibility the NTFS partition can be changed to FAT32?
Ed

rych
Samurai
Samurai
Posts: 147
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 4.0 64 LXDE
Location: NZ

searching for porteus, device not ready, porteus data not found

Post#3 by rych » 04 Mar 2019, 07:31

I suspect that the problem is on the level of partition, before file system. Besides, the first partition regardless it containing NTFS or FAT32, is not the one marked as a boot partition:

Code: Select all

# parted -l
Model: SanDisk Ultra USB 3.0 (scsi)
Disk /dev/sda: 30.8GB
Sector size (logical/physical): 512B/512B
Partition Table: msdos
Disk Flags: 

Number  Start   End     Size    Type     File system  Flags
 1      1049kB  22.1GB  22.1GB  primary  ntfs
 2      22.1GB  30.8GB  8610MB  primary  ext4         boot

Code: Select all

# fdisk /dev/sda -l
Disk /dev/sda: 28.7 GiB, 30752000000 bytes, 60062500 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x5dc89c60

Device     Boot    Start      End  Sectors  Size Id Type
/dev/sda1           2048 43245567 43243520 20.6G  7 HPFS/NTFS/exFAT
/dev/sda2  *    43245568 60061695 16816128    8G 83 Linux

roadie
Full of knowledge
Full of knowledge
Posts: 223
Joined: 02 Jan 2011, 18:41
Distribution: Porteus 4.0-RC4
Location: In a hayfield

searching for porteus, device not ready, porteus data not found

Post#4 by roadie » 04 Mar 2019, 19:02

So I'm interested in your advice: for example how to increase the 6s. delay above -- no use in the `delay` cheat code inside porteus-v4.0-x86_64.cfg as it's on the very partition (?) porteus boot is having difficulty finding. Or anything else?


The delay can be changed by rebuilding the initrd, which is quite easy. Open a terminal and cd to where your initrd.xz is. Mount the initrd using mloop, it will create a backup and you can then cd to /tmp/mloop where you'll will find the mounted initrd.

The file you want to edit is "finit"......search for SLEEP and change to whatever you wish. After editing, run makeinitrd......a new initrd.xz will be created in /tmp/mloop.

I've seen this booting problem before, but never found the cause.....never really investigated. I'm somewhat doubtful that increasing the delay will help......but I've been wrong before.

rych
Samurai
Samurai
Posts: 147
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 4.0 64 LXDE
Location: NZ

searching for porteus, device not ready, porteus data not found

Post#5 by rych » 15 Mar 2019, 05:50

I increased the SLEEP to 15 in two places where previously it specified 6 in `finit`, which made it even worse: couldn't go past the 15 sec wait at all no matter how many restarts -- had to fall back to the original `initrd.xz`

User avatar
Ed_P
Contributor
Contributor
Posts: 4576
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

searching for porteus, device not ready, porteus data not found

Post#6 by Ed_P » 15 Mar 2019, 06:06

In the flash drive's /boot/syslinux/porteus.cfg file try adding "from=UUID:xyxyz-abc9" to the APPEND lines, where xyxyz-abc9 is the UUID of your flash drive where the missing .cfg file is located.

The UUID can be found with su & blkid /dev/sdb2 or whatever your flash drive is assigned to.



-Update-

Other options include:

APPEND root=/dev/sd?2
APPEND hd? 2

The problem is determining the values of the ?s. sda or sdb hd0 or hd1 .
Last edited by Ed_P on 18 Mar 2019, 05:30, edited 1 time in total.
Reason: Referenced additional options
Ed

rych
Samurai
Samurai
Posts: 147
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 4.0 64 LXDE
Location: NZ

searching for porteus, device not ready, porteus data not found

Post#7 by rych » 18 Mar 2019, 07:04

Thanks @Ed
I've added literally without double quotes:

Code: Select all

from=UUID:04defda4-a423-4e51-8485-8b65e657213e
and the boot didn't go through complaining about the "from" cheatcode and no such device

It's always /dev/sda2 for me, so I'm going to try adding simply

Code: Select all

from=/dev/sda2
Will report tomorrow. Although the hope is slim.

I probably need to mention that the host disk's partitions are mounted as /mnt/nvme0n1p1 etc. -- it's a new type of disks that Porteus supports only recently. I hope it doesn't interfere with booting.

rych
Samurai
Samurai
Posts: 147
Joined: 04 Jan 2014, 04:27
Distribution: Porteus 4.0 64 LXDE
Location: NZ

searching for porteus, device not ready, porteus data not found

Post#8 by rych » 19 Mar 2019, 07:19

Code: Select all

from=/dev/sda2
also didn't work, complaining that from= cheatcode is incorrect, press enter for the list of devices or something.

Reboot and pray is my only solution so far

User avatar
Ed_P
Contributor
Contributor
Posts: 4576
Joined: 06 Feb 2013, 22:12
Distribution: 4.0 Cinnamon 64-bit ISO
Location: Western NY, USA

searching for porteus, device not ready, porteus data not found

Post#9 by Ed_P » 19 Mar 2019, 14:56

Don't give up rych. Try these other two options.

APPEND root=/dev/sd?2

or

APPEND hd? 2
Ed

Post Reply