(NVMe?) searching for porteus, device not ready, porteus data not found

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

(NVMe?) 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?
Last edited by rych on 28 Mar 2019, 06:09, edited 1 time in total.

User avatar
Ed_P
Contributor
Contributor
Posts: 4781
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: 155
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: 155
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: 4781
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: 155
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: 155
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: 4781
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

rych
Samurai
Samurai
Posts: 155
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#10 by rych » 25 Mar 2019, 07:16

Neither of those worked.

User avatar
Ed_P
Contributor
Contributor
Posts: 4781
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#11 by Ed_P » 25 Mar 2019, 14:10

Another thought, when you get the error, reboot the drive. I was booting my flash drive the other day and got the missing file error. I never have problems with that error on that drive so I rebooted it and the second time it booted fine.

I know it sounds like a long shot but it only takes a second or two to try it. :happy62:
Ed

rych
Samurai
Samurai
Posts: 155
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#12 by rych » 26 Mar 2019, 07:06

In my case it's just a thumb drive: I reboot the whole computer and it (the porteus partition) gets eventually recognized. I'm thinking of trying a different USB brand, not SanDisk.

User avatar
francois
Contributor
Contributor
Posts: 5618
Joined: 28 Dec 2010, 14:25
Distribution: xfce plank porteus nemesis
Location: Le printemps, le printemps, le printemps... ... l'hiver s'essoufle.

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

Post#13 by francois » 27 Mar 2019, 00:54

@rych:
I get that type of error when some syntax is not respected. Not always easy to troubleshoot. Please provide the complete paragrah that appears in your bootloader and blkid or fdisk -l.
Prendre son temps, profiter de celui qui passe.

rych
Samurai
Samurai
Posts: 155
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#14 by rych » 27 Mar 2019, 07:39

francois, bootloader? You mean `porteus.cfg`? The relevant entry looks like this, and I think I only added login=root to APPEND:

Code: Select all

LABEL GRAPHICAL
MENU LABEL Graphics mode
KERNEL /boot/syslinux/vmlinuz
INITRD /boot/syslinux/initrd.xz
APPEND changes=/porteus login=root
When successfully booted, the output you request is as follows:

Code: Select all

# blkid
/dev/sda1: LABEL="WorkNTFS" UUID="3E9F371468A908B1" TYPE="ntfs" PTTYPE="dos" PARTUUID="5dc89c60-01"
/dev/sda2: LABEL="PorteusEXT" UUID="04defda4-a423-4e51-8485-8b65e657213e" TYPE="ext4" PARTUUID="5dc89c60-02"
/dev/loop0: TYPE="squashfs"
/dev/loop1: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/loop8: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop14: TYPE="squashfs"
/dev/loop15: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"
/dev/loop20: TYPE="squashfs"
/dev/loop21: TYPE="squashfs"
/dev/loop22: TYPE="squashfs"
/dev/loop23: TYPE="squashfs"
/dev/loop24: TYPE="squashfs"
/dev/loop25: TYPE="squashfs"
/dev/loop26: TYPE="squashfs"
/dev/loop27: TYPE="squashfs"
/dev/loop28: TYPE="squashfs"
/dev/loop29: TYPE="squashfs"
/dev/loop30: TYPE="squashfs"
/dev/loop31: TYPE="squashfs"
/dev/loop32: TYPE="squashfs"
/dev/loop33: TYPE="squashfs"
/dev/loop34: TYPE="squashfs"
/dev/loop35: TYPE="squashfs"
/dev/loop36: TYPE="squashfs"
/dev/loop37: TYPE="squashfs"
/dev/loop38: TYPE="squashfs"
/dev/nvme0n1: PTUUID="8bd3d371-f052-4f03-96af-5fcc23c94d44" PTTYPE="gpt"
/dev/nvme0n1p1: UUID="E698-4546" TYPE="vfat" PARTLABEL="EFI system partition" PARTUUID="c4a71eae-919d-4413-91db-0aa8199ea4f7"
/dev/nvme0n1p2: PARTLABEL="Microsoft reserved partition" PARTUUID="3d08c5fd-6bc1-4ef4-aab7-8cc382aad4b6"
/dev/nvme0n1p3: LABEL="OSDisk" UUID="12C0990AC098F567" TYPE="ntfs" PARTLABEL="Basic data partition" PARTUUID="c5778c49-f3c7-4258-970b-92904276f325"

Code: Select all

# fdisk -l
Disk /dev/loop0: 52.5 MiB, 55058432 bytes, 107536 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


Disk /dev/loop1: 106.2 MiB, 111321088 bytes, 217424 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


Disk /dev/loop2: 90.8 MiB, 95227904 bytes, 185992 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


Disk /dev/loop3: 11.5 MiB, 12091392 bytes, 23616 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


Disk /dev/loop4: 4 KiB, 4096 bytes, 8 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


Disk /dev/loop5: 17.1 MiB, 17887232 bytes, 34936 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


Disk /dev/loop6: 16 KiB, 16384 bytes, 32 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


Disk /dev/loop7: 2.7 MiB, 2772992 bytes, 5416 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


Disk /dev/nvme0n1: 238.5 GiB, 256060514304 bytes, 500118192 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: gpt
Disk identifier: 8BD3D371-F052-4F03-96AF-5FCC23C94D44

Device          Start       End   Sectors  Size Type
/dev/nvme0n1p1   2048    718847    716800  350M EFI System
/dev/nvme0n1p2 718848    980991    262144  128M Microsoft reserved
/dev/nvme0n1p3 980992 500117503 499136512  238G Microsoft basic data




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


Disk /dev/loop8: 11.9 MiB, 12488704 bytes, 24392 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


Disk /dev/loop9: 636 KiB, 651264 bytes, 1272 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


Disk /dev/loop10: 8.3 MiB, 8716288 bytes, 17024 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


Disk /dev/loop11: 140 KiB, 143360 bytes, 280 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


Disk /dev/loop12: 556 KiB, 569344 bytes, 1112 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


Disk /dev/loop13: 932 KiB, 954368 bytes, 1864 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


Disk /dev/loop14: 368 KiB, 376832 bytes, 736 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


Disk /dev/loop15: 1.1 MiB, 1187840 bytes, 2320 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


Disk /dev/loop16: 4 KiB, 4096 bytes, 8 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


Disk /dev/loop17: 4 KiB, 4096 bytes, 8 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


Disk /dev/loop18: 49.8 MiB, 52248576 bytes, 102048 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


Disk /dev/loop19: 14.3 MiB, 15024128 bytes, 29344 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


Disk /dev/loop20: 2.7 MiB, 2801664 bytes, 5472 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


Disk /dev/loop21: 800 KiB, 819200 bytes, 1600 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


Disk /dev/loop22: 63.1 MiB, 66162688 bytes, 129224 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


Disk /dev/loop23: 40 KiB, 40960 bytes, 80 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


Disk /dev/loop24: 19 MiB, 19959808 bytes, 38984 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


Disk /dev/loop25: 4.3 MiB, 4538368 bytes, 8864 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


Disk /dev/loop26: 6.2 MiB, 6545408 bytes, 12784 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


Disk /dev/loop27: 1.8 MiB, 1904640 bytes, 3720 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


Disk /dev/loop28: 864 KiB, 884736 bytes, 1728 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


Disk /dev/loop29: 588 KiB, 602112 bytes, 1176 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


Disk /dev/loop30: 13.3 MiB, 13959168 bytes, 27264 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


Disk /dev/loop31: 924 KiB, 946176 bytes, 1848 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


Disk /dev/loop32: 344 KiB, 352256 bytes, 688 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


Disk /dev/loop33: 8.2 MiB, 8634368 bytes, 16864 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


Disk /dev/loop34: 15.6 MiB, 16359424 bytes, 31952 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


Disk /dev/loop35: 1.3 MiB, 1372160 bytes, 2680 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


Disk /dev/loop36: 10.4 MiB, 10919936 bytes, 21328 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


Disk /dev/loop37: 17.5 MiB, 18366464 bytes, 35872 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


Disk /dev/loop38: 75 MiB, 78659584 bytes, 153632 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

neko
DEV Team
DEV Team
Posts: 1424
Joined: 09 Feb 2013, 09:55
Distribution: APorteus-FVWM-ja-x86_64.iso
Location: japan

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

Post#15 by neko » 27 Mar 2019, 09:01

@rych

1. Porteus ISO are expanded in the root of /dev/sda2

2. BIOS did mount & read /dev/sda2@/boot/syslinux/vmlinuz /dev/sda2@/boot/syslinux/initrd.xz

3. Program of /dev/sda2@/boot/syslinux/initrd.xz running under /dev/sda2@/boot/syslinux/vmlinuz can not mount /dev/sda2.

Maybe, the driver for /dev/sda might not be running at boot.

But, from result "blkid" command of your report Porteus did mount /dev/sda1,2.
So, vmlinux and 000-kernel include the driver for /dev/sda.
Maybe, the driver for /dev/sda might be dynamically linked to kernel.

-----------------------------------------------
If the above reasoning is correct,
[How to fix]
1. By rebuild kernel, in order to set that the driver be static linked to kernel.

Or,
2. By modify initrd, insert the driver that is piched up from 000-kernel, activate it in initrd.

-----------------------------------------------
Question:
"When successfully booted, "
How to boot ?


Thanks.

Post Reply