2.11 mounts root fs "/" as read only for type 2 in

[brad_chuck]

The new 2.11 final ( S.M. - xorg drv ) mounts the root fs "/" as read only when doing a "type 2" full hard drive install.

The error I get is line 35 of the xwin script but I think this is the first thing that must wright to the disk.

I have a SATA hard drive that has worked fine in the past and in fact worked in 2.11b.

[pop-pop]

ditto symptom on my desktop with SATA drive
from my scribbly notes:

Code: Select all

touch: cannot touch "/tmp/bootcnt.txt": Read-only file system
-sh /tmpbootkernel.log: Read-only file system
This script will run X windows for you...
/usr/X11R7/bin/xwin: line 61 /tmp/videomode: Read-only file system
/usr/X11R7/bin/xwin: line 35: /tmp/kbdextlayout.txt: Read only file system

The last statement repeats forever.

[BarryK]

Can you also look in /tmp/bootsysinit.log and /initrd/tmp/bootinit.log.

...ah, no, you probably won't have /tmp/bootsysinit.log as it isn't writable.

[pop-pop]

Can you also look in /tmp/bootsysinit.log and /initrd/tmp/bootinit.log.

Looking at my 2.11 HD partition using Puppy 2.10, /tmp is completely empty. The permissions are OK (same as 2.10):

Code: Select all

drwxr-xr-x    2 root     root         4096 Apr 22  2003 tmp

[pop-pop]

I just got Puppy 2.11 to boot from my SATA HD with this one-line addition to /etc/rc.d/rc.sysinit:

Code: Select all

#v2.11 redirect all output to a log file...
mount -o remount /                                      #16Oct2006pop-pop
exec 1>/tmp/bootsysinit.log 2>&1

Barry, looks like this code to make the drives rw needs to be executed a little earlier maybe?

Code: Select all

#v2.11 redirect all output to a log file...
mount -o remount /                                       #16Oct2006pop-pop
exec 1>/tmp/bootsysinit.log 2>&1
#exec 2>&1

echo -n "Making the filesystem usable..." >/dev/console
STATUS=0
echo -n "Mounting /proc: ";mount /proc;STATUS=`expr $STATUS + $?` #;check_status $?
if [ "`df | grep "initrd"`" = "" ];then
 echo -n "Remounting '/' read-write... ";mount -o remount,rw /;STATUS=`expr $STATUS + $?` #;check_status $?
fi
echo -n "Mounting devpts: ";mount /dev/pts;STATUS=`expr $STATUS + $?` #;check_status $?
mkdir /sys 2>/dev/null
echo -n "Mounting /sys: ";mount /sys;STATUS=`expr $STATUS + $?` #;check_status $?
#STATUS

[yammosk]

Did a full hd "normal" on a primary ext2 partition (flagged with boot). Universal Installer installed everything fine, as usual, Grub was also installed without problems.

However, when booting from the hd, I got the exact same error that the previous posters got. I guess this bug is confirmed.

[grndoor]

The drives are already meant to be remounted "rw" through the action of line 71 of "rc.sysinit":

71 echo -n "Remounting '/' read-write... ";mount -o remount,rw /;STATUS=`expr $STATUS + $?`

However, the effect of line 62 of "rc.sysinit" is to prevent this remounting from taking place:

61 #v2.11 redirect all output to a log file...
62 exec 1>/tmp/bootsysinit.log 2>&1
63 #exec 2>&1

Simply commenting out line 62 solves the problem !!!!

[brad_chuck]

This fix does work. If anyone needs a work around.......

[BarryK]

What text editor are you using?
The offending line is number 54. I'm using Geany.

I just did a full h.d. install, and commented out line 54.

I then installed devx_211.sfs as per my own instructions on
http://puppylinux.com/hard-puppy.htm
...but then Puppy would not boot.

So, I have modified the instructions, uploaded the page.

I mounted the devx_211.sfs then copied its contents, using only 'cp -a'.
I have modified that to 'cp -a --remove-destination', which is a forced
copy that will not follow any target file that is a symlink.
For example, if you used 'cp -a -f' and copied file 'dillo' but the destination
already had 'dillo' as a symlink to say 'opera', then opera would get wiped
out. '--remove-destination' simply deletes the target file first, then the
copy occurs without any surprises.

Anyway, I don't know exactly what caused the copy to mess up booting,
but the '--remove-destination' fixed it.
I suspect though, that as busybox has so many symlinks to it, if the
'devx' module tried to overwrite one of those it would have trashed
the busybox executable.

[WhoDo]

Did a full hd "normal" on a primary ext2 partition (flagged with boot). Universal Installer installed everything fine, as usual, Grub was also installed without problems.

However, when booting from the hd, I got the exact same error that the previous posters got. I guess this bug is confirmed.

...And now double-confirmed!

I got problem with a 2.02 to 2.11 Upgrade AND with a clean install of 2.11 to an empty partition.

Cheers

[wombat]

Good Evening Everyone, yes this booting problem after installing P2.11 to your hard drive is easily fixed.
As mentioned line 54 is causing this problem in that location.
After having installed your new Puppy system to your hard drive, taking over the entire partition you selected, reboot your system on the CD once again, and allow a desktop to be achieved running purely on the CD.

Use your Puppy Drive Mount tool in Menu > Utilities to mount the applicable hard drive. Then minimise those windows.

Open the Edit program on the top of the desktop, (Geany) navigate in this program using the File > Open route to the /etc/rc.d/rc.sysinit file and open it.
On the Menubar, select Search > Go to line > 54 then you will have line 54 hilighted. "exec 1>/tmp/bootsysinit.log 2>&1"
Place a # in front of that line, so that it will now be
# exec 1>/tmp/bootsysinit.log 2>&1
Then save and exit that program.
When the system is rebooted your machine should boot and operate normally.
Certainly is magic stuff, certainly is a great system.
Cheers Wombat.

[brad_chuck]

Pesky line numbers...

I did not look at the line number, it is 54 for me too.

Just to be clear...

[nyu]

Hi ALL,
If I commented out Line 54 and then remastered a CD, will I fix the
problem to install puppy2.11 in a hard disk?
nyu

[RazzBear]

Had the same problem as everybody but what worked for me was changing the line in menu.lst for the grub boot loader

from kernel /boot/vmlinuz root=/dev/hda1 ro vga=normal
to kernel /boot/vmlinuz root=/dev/hda1 rw vga=normal

[JimDandy]

Anyone know why this workaround wouldn't work in my case? Fresh install of 2.11 to my hard drive. Same read-only errors everyone else reports. Commented out that line 54 in rc.sysinit, but I'm still getting the same error. I'll try modifying my menu.lst, but evidently this workaround isn't a total solution to the problem.

[JimDandy]

Changing RO to RW got me into X, but now half the programs I try to start, including the terminal, MUT, and xvesa config close as soon as I open them. Also, I'm getting a report of no RAM avaiable in the taskbar. Any ideas what's up here? Thanks.

[Fishy]

My original 2.11 install caused a major crash of not only Puppy but my /home of my debian partition I am not sure what I did wrong in trying to clean up problem but S--- does happen. My question is, has the iso been modified to correct the glitch or when will it be corrected. I see no reason to re-install Puppy 2.11 from the original iso until it is completely debugged.

What really hurts is that I had come to completely depend on Puppy as bullet proof.

Cheers

[WhoDo]

Hi ALL,
If I commented out Line 54 and then remastered a CD, will I fix the
problem to install puppy2.11 in a hard disk?
nyu

Yes. I've done it and the problem is gone in all subsequent installs from the remastered disk.

[nyu]

Hi ALL,
If I commented out Line 54 and then remastered a CD, will I fix the
problem to install puppy2.11 in a hard disk?
nyu

Yes. I've done it and the problem is gone in all subsequent installs from the remastered disk.

Hi Whodo,
Big thanks!
nyu

[veronicathecow]

Hi, help really appreciated on this problem. I am a technician (Windows, sorry but I am trying to do the right thing

I have tried lots of versions (at least eight) of Puppy on different machines and all work lovely off CD but never install to HDD ever!

I have been running Ubuntu on my main desktop for a month. I have also installed DSL, Ubuntu, PC Linux all to this Laptop without a hitch...

I am currently trying to put it on a Compaq PResario 1200 with 124 of RAM (4 on internal graphics). I have had a number of errors when trying to use GRUB. I have used the Ultimate Boot CD tools to clean / wipe / delete etc all MBRs / partitions / filesystems etc but am still having problems.

I was just trying Wombats instructions (which seemed very clear and newbies like me appreciate that) but the grub auto config took me to expert setup and every menu item on that just took me straight back to the menu!

On reboot it comes up with "This is not a bootable disk"

I rebooted onto the CD, tried to mount the HDD using Puppy mount and I get "FAILURE! In the case of removable media......"

I tried editing the file as described and saved it but on reboot it came up with "This is not a bootable disk" (I should point out that whilst running the Puppy Universal Installer program the memory indicators say "No memory"

Next I tried running GRUB Simple mode enter the partition as /dev/hda and GRUB comes back with "The partition /dev/hda is not linux" even though Puppy drive mounter says /dev/hda ext3 and says it cannot mount it with the error message shown earlier. (It mounts a CD fine)

I tried MUT and although no errors occur, nothing shows up on the file list (have switched to show hidden) and I still get the same error "The partition /dev/hda is not linux"

Gparted shows the HDD as /dev/hda1 fat32 mount point of /mnt/hda1
flag Boot

Tried GRUB with a mount point of /mnt/hda1 but same error.

Sorry to go on but I've tried everything I can think off and more....

Cheers
Tony