Virtualbox Slackware 14.2 guest on nvme installpkg read-only errors
Slackware - InstallationThis forum is for the discussion of installation issues with Slackware.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi Didier,
thanks for your details.
I see that Slint is dated around Gen & your file August so my question : is the ISO patch included into the first file?
Taking into account that I linked the Slint into SATA virtual device (before to install) so I don't know how to include your patch before to run ISO distro.
If your patch is included I use the ISO Slint only...
(I found also the e2fcsk options : "e2fcsk -fp -C 0 /dev/nvme0n1p2")
Thank you very much...I let you know my news with installation details.
Bye
Hi Didier,
thanks for your details.
I see that Slint is dated around Gen & your file August so my question : is the ISO patch included into the first file?
Yes it is.
Quote:
Taking into account that I linked the Slint into SATA virtual device (before to install) so I don't know how to include your patch before to run ISO distro.
Yes it is, as in the other ISO. Actually I shipped Slint64-14.2 fully patched before proposing the patches to Slackware.
Quote:
If your patch is included I use the ISO Slint only..
Feel free to. Or wait 24 hours and try the new release
Quote:
(I found also the e2fcsk options : "e2fcsk -fp -C 0 /dev/nvme0n1p2")
Thank you very much...I let you know my news with installation details.
Bye
You are welcome. Best of luck.
Last edited by Didier Spaier; 12-17-2017 at 04:05 PM.
Hello Didier..my test is negative.
It is very very abnormal...the virtual vmdk file have errors.
Below the e2fsck message found:
"Bad magic number in super-block while trying to open /dev/nmve0n1.
The superblock could not be read or does not describe a valid ext2/ext3/ext4 filesystem....."
Following at the installation package phase I try:
"hdparm (read set hard drive parameters)
Error:can't open file for writing read only file system
Error:error thrown
Error:failed to estract file /sbin/hdparm
Error package installation failed."
So I think that there is problems into the partition phase create.
The last trial that I can do is use other tool..diffrerent to cfdisk.
I let you know...but for me it seems very very strange...
Bye
Hello Didier!!
Congratulation for your precious work.
However I installed a Slackware64-current-DVD and the problem is the same :
process stopped because
"/usr/lib/setup/installpkg: line 378 /mnt/var/log/setup/tmp/tmplist_number read-only filesystem"
I also repeat the same ISO in virtual machine with SATA-SATA simulated support(HDD+DVD).
No errors found and installation was completed.
My other tests will be :
new version of Virtualbox (rel 5.2.4) with your new Slint & new version of Virtualbox with new version of Slackware64-current.
I let you know the results.
A little issue:
I saw that your old Slint version try to install all packages without choice (for example by passing some programs instead of other).
Is it correct?
Thank you again and....I wish you (and your family) an Happy Christmas.
Bye
A
A little issue:
I saw that your old Slint version try to install all packages without choice (for example by passing some programs instead of other).
Is it correct?
Yes it is. In the new version that also includes LXDE and MATE, only KDE is optional.
Hello Didier,
I tried others Linux Distro and the same behaviour happened also.
During the installation phase there is a difficult to open the read package.
With Debian we have the same problem:stopped installation for corrupt packages
My thought is that it can be:
not enought memory in /tmp directory during the installation phase or something similare issues.
It is like very fast move and the /tmp space is not empty yet
Taking into account that the configuration SATA-SATA (virtual hdd + DVD) is very good for all kind of distro & all kind of ISO.
Bye
A.
Hi Didier,
nice to write you newly.
Finally I found the problem which we discussed previously.
All installation bugs (and after that) is generated by chipset that I choose: "ICH9".
All incopatibilty start on it.
If I pass PIIX3 as option at the machine configuration all go on very well.
Different case is when the item is "ICH9".
With it all system crash as you know.
The same behaviour is for Debian.
So it is very interesting at this time to know if the problem grow up from kernel module or VirtualBox driver.
What do you think about?
I hope that my discovered is useful for others.
Bye
Alessandro
All installation bugs (and after that) is generated by chipset that I choose: "ICH9".
Yes, this seems to be confirmed by Oracle, and hopefully fixed in VirtualBox 5.2.10 (released April 17 2018), according to the Changelog that includes:
Quote:
Storage: fixed having multiple NVMe controllers with ICH9 enabled (5.2.0 regression)
So I suggest that you upgrade VirtualBox to confirm that the fix works in your case.
Hello Didier,
also the ver 5.2.10 have the same behaviour.
I think that the issue that solve the problem is:
"Serial: fixed possible data corruption when sending data under certain circumstances" in 5.2.12 version
I don't test yet the new version but I let you know as soon as I reach to complete the installation with ICH9 and NVME device without "error data corruption" into data transfer from virtual DVD iso to virtual NVME
Bye
Hello Didier,
confirm the same behaviour in the version 5.2.12 VirtualBox.
Using ICH9 chipset + Sata device + NVME virtual HDD, I think that grows up bug.
I suppose data corrupt during installation phase.
The configuration PIIX3 go on without problems with Sata device and NVME virtual HDD.
Very interesting issue...:-)
Bye
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.