![]() |
See also DiskNotRecognized [NOTE: .recovery files are only for openslug, not unslung???]
Maybe you have had some unclean shutdown, then the file To find out if flash or your harddisk is mounted you type 'mount': Harddisk:
When installing uNSLUng 6.8, the unslung drive was not being mounted as the rootfs on reboot. The disk was mounted and showing up as /dev/sda1 on /share/flash/data, but the system was still running from internal flash. Eventually traced it down to /linuxrc, which was testing for -e /.sda1root which was not present. touch /.sda1root, then reboot, fixed the problem. When installing uNSLUng 6.8, the unslung drive was not being mounted as the rootfs on reboot. The disk was mounted and showing up as /dev/sda1 on /share/flash/data, but the system was still running from internal flash. Updated /linuxrc to increase the sleep in line 24 from 5 to 10, then reboot, fixed the problem. This was with an Iomega 500GB drive. Another linuxrc fix; While installing unslung 5.5 to a WesternDigital? MyBook? essential 320 MB, the timeout in linuxrc was already increased and a /.sda1root present. The testmounting at /mnt failed, "mount: Mounting /dev/sda1 on /mnt failed: No such device or address" (piping stderr to /linuxrc_log). Inserting a sleep 4 just before the mounting at /mnt solved this problem |