October 4, 201411 yr I've searched through the forums and found a few other posts about this but none of their fixes have worked for me. When I go to tower it doesn't list any of the user shares. I can see the tower in my network places in windows explorer and can go into the disks and see that the user share folders are still there along with my data. When the system came back online it ran a full parity check. (no errors) I've rebooted several times. I removed the USB, plugged it into my windows pc, and ran check disk. (found nothing) I ran reiserfsck --check from maintenance mode on both my data drives. (found nothing) -- Do I need to run this on my parity or cache drives? Under settings User shares are set to yes. I haven't specified to include or exclude any drives. To be clear before I lost power I had several user shares. I haven't had any issues since first getting my machine running and I haven't made any recent changes. I've attached my syslog after doing another reboot. These lines look interesting but not sure what to do? Oct 4 09:30:14 Tower kernel: ACPI Error: [DSSP] Namespace lookup failure, AE_NOT_FOUND (20130117/psargs-359) Oct 4 09:30:14 Tower kernel: ACPI Error: Method parse/execution failed [\_SB_.PCI0.SAT0.SPT5._GTF] (Node f107b708), AE_NOT_FOUND (20130117/psparse-537) syslog.zip
October 4, 201411 yr Author Update: I tried reformatting my USB drive and then upgrading to 5.05 as a way to start completely fresh. I replaced these files with my old flash config files: disk.cfg flash.cfg ident.cfg network.cfg passwd Plus.key secrets.tdb shadow share.cfg shares (directory and its content) smb-extra.conf smbpasswd super.dat Everything booted fine. I can see my data is all still there but my shares are still not appearing in the shares tab. I double checked the settings and user shares are enabled. At this point I'm wondering if I should just recreate them (I can read the old configs and set them up the same). But I would like to know what happened and what I can do to prevent it. I've also attached my latest syslog. syslog2.zip
October 5, 201411 yr Author That fixed it! Thank you! Any ideas on why losing power (incorrect shutdown) would cause the shares.cfg file to get corrupted? I attached it here. share.old.cfg
October 5, 201411 yr God I love this job. Fixing stuff like this for folks is so much fun ;-). That said, check your individual share settings to make sure they are right. Your settings for "use cache" and disk includes/excludes probably need to be reset.
October 5, 201411 yr As for why it happened, could have been the share.cfg file was open for some reason when you lost power and a bit got flipped or something.
Archived
This topic is now archived and is closed to further replies.