post-upgrade, / mounts ro and domain resolution is wonky

[ninjaaron]

I just did an upgrade on my raspberry pi server. It now mounts the root file system as read-only. I can fix this with `mount -o remount,rw /`

Also, when I try to ping a domain name, it fails. If I try to ping an IP or an alias from /etc/hosts, it's fine. I can't get pacman to download packages because it can't resolve the host for the mirror.

It also has an NFS server, and the share doesn't mount properly on the clients. ssh/sftp seem to be working fine.

[Gyscos]

I once had the DNS issue, it was caused by an IPv6 DNS server in /etc/resolv.conf while the network didn't actually provide IPv6. Removing the entry in resolv.conf fixed it.
Read-only mount are sometimes caused by a corrupt filesystem. Try to fsck it from another computer to check its status. Or maybe a rw flag in fstab (or in the kernel boot line?) could fix that.

[pepedog]

ro, look at cmdline.pacnew for rw
nfs, search forum for rpcbind for possible answer

[ninjaaron]

Well, thanks to Gyscos, I got DNS working. I checked my /etc/resolv.conf and it was empty. Ran `resolvconf -u`... not exactly sure what this does, but it populated my /etc/reslov.conf and DNS work!

tried to fsck. dirty bit was found and cleaned. still mounting ro. checked /boot/cmdline.txt and it says rw. Explicitly added rw to my fstab... and yet still ro.

haven't tackled NFS yet.

Anyway, I think my question from long ago has been answered: Can you run a file server off a raspberry pi? Yes, you can, but you might not want to...

[MadMe]

could you post your fstab?
i had the same problem. I don't know why but after the upgrade there were no entry for my root directory ...
here is my fstab.

$this->bbcode_second_pass_code('', '
/dev/mmcblk0p1 /boot vfat defaults 0 0
/dev/mmcblk0p2 / ext4 rw,relatime,data=ordered 0 0
')