> there's some other issue in the way the drives > I've turned off journaling, but I'm wondering if Write capability should be used with caution (have backup, and only use unimportant data with it). However, as I cautioned users in the Howto post, HFSPlus is unsupported in mainline Linux. But your use case is different, so you have to test the udev rules to make sure. But for the time that I forgot for many days, it did not cause problem. Usually I don't leave the HFSplus drive plugged in the NAS box permanently if I remember to remove.
I've never seen data corruption using udev rules. > mount -a and the drive is read/write once again. I can then plug back in to the pogo, run a > I plug the drive into my Mac and run Disk Utility > (I'm not to familiar) that can only be remedied if > seemingly because of some level of data corruption > toggle power, the drives are mounted read only > read/write but if I just do a reboot command or > everything before rebooting, I remain able to > an unexpected power loss, or during a reboot? > do your HFSplus drives not become read-only after It now includes mounting HFSplus in Read/Write mode. I've update the howto in the Wiki thread: Maybe that would yield the best results, but then these drives will be purely dedicated to my Pogoplug and not pluggable for Macs I'm leaning toward converting 1 of the drives to EXT3 and copying everything from the HFS+ drives over, then converting the others drives and using them as backups.
I realize this may drift off topic, but it seems like it could be related to the inconsistency in the mounting and access level of the hfsplus drives.Īnd disc related commands keep getting hung up (like fdisk -l or trying to mkdir on a drive, or stopping/starting smbd service). Status: "smbd: ready to serve connections." Process: 4231 ExecReload=/bin/kill -HUP $MAINPID (code=exited, status=0/SUCCES Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enaĪctive: active (running) since Tue 19:37:30 PST 12h ag I've also been seeing some weird behaviors with the Samba sharing of these drives where there are over 20 process IDs for the systemctl status rvice I recently added the 'nofail` option as the boot process seemed to hang on occasion and I was hoping that would help booting continue if there were issues mounting a drive.
LABEL=MGB-500 /mnt/pogo1 hfsplus nofail,force,rwĐĐ LABEL=rootfs / ext3 noatime,errors=remount-ro 0 1 # /etc/fstab: static file system information. Bodhi - I'm able to mount read/write by my entries in /etc/fstab
0 kommentar(er)
