LinuxQuestions.org - remount partition as rw

- Linux - General (https://www.linuxquestions.org/questions/linux-general-1/)

- - remount partition as rw (https://www.linuxquestions.org/questions/linux-general-1/remount-partition-as-rw-682779/)

remount partition as rw

Hi all,

I am trying to reset a password of a user but that is giving me error.

Code:

[root@RHEL4 /]# passwd vikas

Changing password for user vikas.

New UNIX password:

Retype new UNIX password:

passwd: Authentication token lock busy

I even tried vipw

Code:

[root@RHEL4 /]# vipw

vipw: /etc/ptmptmp: Read-only file system

Code:

[root@RHEL4 /]# touch abc

touch: cannot touch `abc': Read-only file system

I tried remounting (forcefully too) with rw but all in vain.

Code:

[root@RHEL4 /]# mount -o remount,rw /

mount: block device /dev/sda3 is write-protected, mounting read-only

[root@RHEL4 /]#

[root@RHEL4 /]# mount -o remount,rw / -force

[root@RHEL4 /]# echo $?

0

This is a production server, I can not come into single user mode.

Can anyone help me with this ?
PLEASE HELP ME OUT.

Regards,
VIKAS

Quote:

Originally Posted by vikas027 (Post 3339057)

Hi all,

I am trying to reset a password of a user but that is giving me error.

Code:

[root@RHEL4 /]# passwd vikas

Changing password for user vikas.

New UNIX password:

Retype new UNIX password:

passwd: Authentication token lock busy

I even tried vipw

Code:

[root@RHEL4 /]# vipw

vipw: /etc/ptmptmp: Read-only file system

Code:

[root@RHEL4 /]# touch abc

touch: cannot touch `abc': Read-only file system

I tried remounting (forcefully too) with rw but all in vain.

Code:

[root@RHEL4 /]# mount -o remount,rw /

mount: block device /dev/sda3 is write-protected, mounting read-only

[root@RHEL4 /]#

[root@RHEL4 /]# mount -o remount,rw / -force

[root@RHEL4 /]# echo $?

0

This is a production server, I can not come into single user mode.

Can anyone help me with this ?
PLEASE HELP ME OUT.

Regards,
VIKAS

Unfortunately the only thing that usually fixes this when you can force a remount is to reboot the server. Most of the time I've encountered this means somethings gone wonky with the controller. I've seen firmware fix this issue when it's reoccurring and or hardware replacements made to fix.