I have lost 4 BBB after simple power down. Debian 8, 4.1.30-ti-r69. Serial
console output now reveals:
rootfs contains a file system with errors, check forced.
rootfs:
Duplicate or bad block in use!
rootfs: Multiply-claimed block(s) in inode 6104: 9960
rootfs: Multiply-claimed block(s) in inode 6106: 9961
rootfs: Multiply-claimed block(s) in inode 6107: 9960
rootfs: Multiply-claimed block(s) in inode 6174: 9961
rootfs: (There are 4 inodes containing multiply-claimed blocks.)
rootfs: File
/var/tmp/systemd-private-deb6f9c85d7340c6a91d98a33d4b7943-systemd-timesyncd.service-WrsUyR
(inode #6104, mod time Sat May 21 22:31:30 2016)
has 1 multiply-claimed block(s), shared with 1 file(s):
rootfs:
/var/tmp/systemd-private-acdd2033bf68467fac7dccdc8c4f2114-systemd-timesyncd.service-IU4CO0
(inode #6107, mod time Sat May 21 22:31:30 2016)
rootfs:
rootfs: UNEXPECTED INCONSISTENCY; RUN fsck MANUALLY.
(i.e., without -a or -p options)
fsck exited with status code 4
This output is the same on all 4 devices (with somewhat different folder
names, of course).
What could be the reason for this happening?
Is there anything known about systemd resp. timesyncd creating a problem on
shutdown with privatetemp=True?
Where can timesyncd be set to privatetemp=False? Does that create other
problems?
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/beagleboard/8abde6cf-7922-4462-93cb-d40157829659%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
