Ubuntu 16.04.3 Mount /dev/sda1 as Read Write ?

Root filesystem drive is now write-protected

I tin can't seem to create any new files on my / and tin can't do elementary commands such as passwd.

I institute some advice to run the following, simply as you can see that failed also. Information technology seems I'm stuck with my bulldoze mounting as read only. I'm running Hardy.

$sudo mount -o remount,rw /
mount: block device /dev/sdc1 is write-protected, mounting read-merely

Here'south the info from fdisk and file -s for the drive in question.

$ sudo fdisk -l /dev/sdc

Disk /dev/sdc: 80.0 GB, 80026361856 bytes
255 heads, 63 sectors/rails, 9729 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Deejay identifier: 0x4b36bdea

Device Kicking Start End Blocks Id System
/dev/sdc1 * 1 9327 74919096 83 Linux
/dev/sdc2 9328 9729 3229065 five Extended
/dev/sdc5 9328 9729 3229033+ 82 Linux swap / Solaris
$ sudo fdisk -l /dev/sdc1

Disk /dev/sdc1: 76.7 GB, 76717154304 bytes
255 heads, 63 sectors/track, 9326 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Deejay /dev/sdc1 doesn't contain a valid sectionalisation table
$ sudo fdisk -l /dev/sdc2
$ sudo fdisk -l /dev/sdc5

Deejay /dev/sdc5: 3306 MB, 3306530304 bytes
255 heads, 63 sectors/track, 401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/sdc5 doesn't contain a valid partition tabular array
$ sudo file -s /dev/sdc1
/dev/sdc1: Linux rev ane.0 ext3 filesystem data (needs journal recovery) (errors) (large files)
$ sudo file -s /dev/sdc2
/dev/sdc2: x86 kicking sector, extended sectionalisation table (last)\011
$ sudo file -southward /dev/sdc5
/dev/sdc5: Linux/i386 swap file (new style) 1 (4K pages) size 807257 pages

Hither's the fdisk info for my other 2 drives. I don't think you'll demand it, only here it is anyways.

$ sudo fdisk -l /dev/sda

Deejay /dev/sda: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x0004bb3d

Device Boot Start End Blocks Id System
/dev/sda1 1 30401 244196001 83 Linux
$ sudo fdisk -l /dev/sdb

Disk /dev/sdb: 250.0 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Deejay identifier: 0x00000000

Device Kicking Offset End Blocks Id Organization
/dev/sdb1 1 12159 97667136 83 Linux
/dev/sdb2 12160 24318 97667167+ 83 Linux

1 other tidbit of info that might help is that after a power outage the other mean solar day, my drives seem to be mounting at different points. For example, my /dev/sdc (the bulldoze that I'k having trouble with), I retrieve used to be /dev/hdd. And I've had to recreate some of my symlinks.

$ less /etc/fstab
# /etc/fstab: static file organisation data.
#
# <file system> <mount point> <type> <options> <dump> <laissez passer>
proc /proc proc defaults 0 0
# /dev/hdb1
UUID=ff7ccb24-0212-4208-bf6a-f1c32f39ed3a / ext3 defaults,errors=remount-ro 0 1
# /dev/hdb5
UUID=5d0bfc71-1f98-4094-b6e7-3865d7d51a23 none swap sw 0 0
/dev/hda /media/cdrom0 udf,iso9660 user,noauto,exec 0 0
/dev/fd0 /media/floppy0 auto rw,user,noauto,exec 0 0

#
/dev/sda1 /mnt/sda1 car defaults 0 0
/dev/sdb1 /mnt/sdb1 machine defaults 0 0
/dev/sdb2 /mnt/sdb2 auto defaults 0 0
/dev/sdc1 /mnt/sdc1 auto defaults 0 0
/dev/sdc2 /mnt/sdc2 auto defaults 0 0

I appreciate the help.

---

Re: Root filesystem drive is now write-protected

get rid of the auto selection on the harddrives, and add a FS type

endeavour to mount a disk by hand, with

Code:

sudo  mountain /dev/sdc1 /mnt/sdc1

your fstab should expect this (im using lvm, but you lot should use the /dev/thirty):

/dev/lvm_main/root / ext3 defaults 1 i
/dev/sda1 /data1 ext3 defaults 1 2
/dev/lvm_main/dwelling house /home ext3 defaults 1 2
/dev/lvm_main/opt /opt ext3 defaults 1 two
/dev/lvm_main/tmp /tmp ext3 defaults ane two
/dev/lvm_main/usr /usr ext3 defaults 1 ii
/dev/lvm_main/usr.local /usr/local ext3 defaults i ii
/dev/lvm_main/var /var ext3 defaults 1 two
/dev/lvm_main/var.tmp /var/tmp ext3 defaults 1 2

"Please choose a dissimilar password, the 1 y'all have chosen is in use by UID 1432"

---

Re: Root filesystem drive is now write-protected

Your file organisation is probable damaged and thus mounted ro

Boot a alive CD (y'all can non run fsck on a mounted partition) and run :

Code:

fsck -rfv /dev/sdxy

where /dev/sdxy == your ubuntu root partition (/dev/sdb1 I think)

There are two mistakes one tin can brand along the route to truth...not going all the fashion, and not starting.
--Prince Gautama Siddharta

#ubuntuforums web interface

---

Re: Root filesystem bulldoze is at present write-protected

You lot tin also force a check on a particular division past manually setting its mount count to 30 or more than. For example, to force a check on /dev/sda1 on next reboot:

Code:

sudo tune2fs -C xxx /dev/sda1

When you adjacent reboot a cheque should be run earlier the fs is mounted read/write.

Don't endeavour to make something "fast" until y'all are able to quantify "slow".

---

Re: Root filesystem drive is now write-protected

You guys are awesome. Buy yourselves a cup of coffee for me.

When I get home tonight, I'll pop the live cd in, run the fsck, and have a await at my fstab again. Hopefully all will be good over again.

---

Re: Root filesystem drive is now write-protected

Tried fsck from live cd

Code:

ubuntu@ubuntu:~$ sudo fsck -rfv /dev/sda3 fsck 1.40.eight (13-Mar-2008) e2fsck 1.twoscore.8 (13-Mar-2008) Laissez passer 1: Checking inodes, blocks, and sizes Pass 2: Checking directory structure Pass 3: Checking directory connectivity Laissez passer iv: Checking reference counts Pass five: Checking group summary information    162417 inodes used (nine.58%)     7907 non-contiguous inodes (four.9%)          # of inodes with ind/dind/tind blocks: 19107/445/0  3514095 blocks used (51.83%)        0 bad blocks        1 large file    129299 regular files    15777 directories       69 graphic symbol device files       26 cake device files        2 fifos      465 links    17209 symbolic links (16138 fast symbolic links)       26 sockets --------   162873 files ubuntu@ubuntu:~$

Rebooted from hdd and nevertheless got a read-merely filesystem. I can write to information technology as su, or sudo, but it's only not comfy....

Whatsoever ideas?

Asus 1005HA CPU:N280 HDD:160G RAM:2G Ubuntu 10.04 and/or Mint nine

Also have bedraggled Fujitsu-Siemens Amilo D 1845 [now one-half-bricked by upgrade ]
知 者 不 言。言 者 不 知。

---

Re: Root filesystem bulldoze is now write-protected

Is the partition total ?

Run

Or to see just the root segmentation :

There are ii mistakes one can make along the road to truth...not going all the mode, and not starting.
--Prince Gautama Siddharta

#ubuntuforums spider web interface

---

Re: Root filesystem drive is now write-protected

bodhi, Namaste

Thanks for your reply. yet no joy.

here's the effect:

Code:

ed@ubuntu:~$ df -h Filesystem            Size  Used Avail Use% Mounted on /dev/sda3              26G   14G   11G  57% / varrun                252M  108K  252M   one% /var/run varlock               252M     0  252M   0% /var/lock udev                  252M   68K  252M   1% /dev devshm                252M   52K  252M   ane% /dev/shm lrm                   252M   38M  214M  sixteen% /lib/modules/2.half dozen.24-19-generic/volatile /dev/sda2             9.9G  4.5G  5.5G  45% /media/deejay-vi gvfs-fuse-daemon       26G   14G   11G  57% /home/ed/.gvfs /dev/sdb1             5.4G  335M  5.1G   vii% /media/My Book /dev/sdb3             156G   47G  101G  32% /media/disk-4 /dev/sdb4              59G  944M   58G   2% /media/deejay-5 /dev/sdb2              79G   39G   40G  l% /media/disk-7 ed@ubuntu:~$ df -h | egrep /$ /dev/sda3              26G   14G   11G  57% / ed@ubuntu:~$

The only thought I have is that it might be considering I tried to have the windows segmentation open up at kicking via fstab. Here's fstab as soon working with the 'offending'line commented out. I'll comment out the other division every bit well and reboot to come across if that gives any joy.

Code:

ed@ubuntu:~$ cat /etc/fstab # /etc/fstab: static file arrangement information. # # <file system> <mount point>   <type>  <options>       <dump>  <laissez passer> proc            /proc           proc    defaults        0       0 # /dev/sda3 UUID=f62e3f18-02e0-486f-b46a-54a67f105f08 /               ext3    relatime,errors=remount-ro 0       1 # /dev/sda4 UUID=d3dd670e-5b93-4d68-a2de-445b5a31e3ec none            swap    sw              0       0 /dev/cdrom       /media/cdrom0   udf,iso9660 user,noauto,exec,utf8 0       0 # hopefully this volition get share partition mounted at kick /dev/sda2 /media/deejay-half-dozen vfat rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush 0 0 # same for windows sectionalization mounted at kick #/dev/sda1 /media/25_02_42_ fuseblk rw,nosuid,nodev,noatime,allow_other,blksize=4096 0 0 ed@ubuntu:~$

Thanks again. Organisation working fine otherwise.

Salaam/Shalom/Shanthi/Dorood/Peace
ed

Asus 1005HA CPU:N280 HDD:160G RAM:2G Ubuntu 10.04 and/or Mint 9

As well have decrepit Fujitsu-Siemens Amilo D 1845 [now half-bricked by upgrade ]
知 者 不 言。言 者 不 知。

---

Re: Root filesystem bulldoze is now write-protected

What is all this about? It is perfectly normal that you cannot write to the root directory (/) as a normal user. Moerover, in that location is no reason for you to write in the /

The output of your fsck indicates that your drive is in a perfect state.

In conclusion, you do non have any problem. Delight practice not attempt to create i.

---

Re: Root filesystem drive is at present write-protected

Originally Posted by vanadium

What is all this about? Information technology is perfectly normal that yous cannot write to the root directory (/) every bit a normal user. Moerover, at that place is no reason for you to write in the /

The output of your fsck indicates that your drive is in a perfect land.

In conclusion, you do not have whatsoever trouble. Please practise not attempt to create 1.

If you expect at the kickoff post once more, yous will see this is non a prtitions problem. The drive is beingness remounted read-merely for some reason

biggunks - Could you please post the output of:

Code:

ls -l /dev/disk/by-uuid/

That's just then we can make sure you lot ran fsck on the right volume.

Final edited by chrisccoulson; July fifth, 2008 at xi:34 AM.

---

mcdonaldloyarround1950.blogspot.com

Source: https://ubuntuforums.org/showthread.php?t=834235

Bagikan Artikel ini