Devlah

Forum Replies Created

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • in reply to: SAMBA Network Share conundrum #11592

    Devlah
    Participant

    Oh, just remembered that you asked for these.

    
    root@slitaz:/home/tux# cat /proc/mounts
    rootfs / rootfs rw 0 0
    devpts /dev/pts devpts rw,relatime,mode=600 0 0
    tmpfs / tmpfs rw,relatime,size=2800508k 0 0
    proc /proc proc rw,relatime 0 0
    sysfs /sys sysfs rw,relatime 0 0
    tmpfs /dev/shm tmpfs rw,relatime 0 0
    usbfs /proc/bus/usb usbfs rw,relatime 0 0
    fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
    /dev/sda1 /media/sda1 ext4 rw,relatime,barrier=1,data=ordered 0 0
    /dev/sdc1 /media/sdc1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0
    /dev/sdb2 /media/sdb2 fuseblk rw,relatime,user_id=0,group_id=0,allow_other,blksize=4096 0 0
    

    Hopefully this will be helpful in some way. This was done from the terminal in Ophcrack.

    in reply to: SAMBA Network Share conundrum #11591

    Devlah
    Participant

    Ok. Reporting back. I happened to have a copy of Ophcrack (powered by SLItaz) on hand, and decided to live-boot that on the machine. The 5TB drive not only was mounted properly, but all of it’s media was fully accessible to me in that environment. I then proceeded to attempt to wipe and install the new GeexBox distro mentioned earlier, and when it got to the first menu (asking if I want to run or install) the USB keyboard become unresponsive during the 5 seconds I had to decide. Fortunately, I happen to have an older PS/2 keyboard lying around and used that instead. This allowed me to reboot and choose “Install” at the menu. After displaying the ASCII “GeexBox” logo, it displayed: “Unable to find root file system, dropping to shell.”

    Now, while I was in Ophcrack, the original partition was still available to me, and was formatted EXT4, and still flagged as boot. It’s contents were also available for browsing. I decided to do a hardware report while I was in Ophcrack, and found the CPU being used BTW: 2x Intel(R) Pentium(R) CPU 2.80GHz with 3111MB of RAM

    GeexBox 3.1 seemed to work just fine with the 2TB drive, but not with the 5TB drive, and I recall the kernel config setting you mentioned earlier, so I know that I could in theory re-install using that image and possibly be fine, but in the interests of contributing to the project, I’m willing to try something else if you have any suggestions.

    in reply to: SAMBA Network Share conundrum #11588

    Devlah
    Participant

    Will do.

    in reply to: SAMBA Network Share conundrum #11586

    Devlah
    Participant

    Alrighty then. Thanks for all the help.

    in reply to: SAMBA Network Share conundrum #11584

    Devlah
    Participant

    Oh well…Fresh install it is.
    Incidentally, where would I find the Kernel config?

    in reply to: SAMBA Network Share conundrum #11582

    Devlah
    Participant

    Well, that seemed to work, as far as doing…stuff….
    Here’s what I got though…
    http://pastebin.com/AaNNG8D3

    I’m guessing I’m going to need to do a manual reboot perhaps…

    in reply to: SAMBA Network Share conundrum #11577

    Devlah
    Participant

    The Original image used to setup this machine was: geexbox-3.1-x86_64.iso. That was back on 2/5/2017

    I’ve now downloaded: geexbox-devel-20170215-rabd3c04-x86_64.iso

    Hopefully this will make a difference.

    in reply to: SAMBA Network Share conundrum #11574

    Devlah
    Participant

    Done. However…When executing “opkg upgrade” every package “has no valid architecture, ignoring.”

    It IS a fairly old machine, I’m not entirely certain that the chip architecture supports x64. I’ll have to investigate. If it does, then it’ll be worth it to make a new Live USB and start all over.

    in reply to: SAMBA Network Share conundrum #11568

    Devlah
    Participant

    Out of curiosity, is there a method I could use to apply the update remotely, or do I need to uproot the machine from it’s place of residence and treat it like a fresh install?

    in reply to: SAMBA Network Share conundrum #11566

    Devlah
    Participant
    
    # cd /root
    # mkdir sdb1
    # mkdir sdb2
    # mount /dev/sdb1 /root/sdb1
    NTFS signature is missing.
    Failed to mount '/dev/sdb1': Invalid argument
    The device '/dev/sdb1' doesn't seem to have a valid NTFS.
    Maybe the wrong device is used? Or the whole disk instead of a
    partition (e.g. /dev/sda, not /dev/sda1)? Or the other way around?
    mount: mounting /dev/sdb1 on /root/sdb1 failed: Invalid argument
    #
    # mount /dev/sdb2 /root/sdb2
    Failed to write lock '/dev/sdb2': Resource temporarily unavailable
    Error opening '/dev/sdb2': Resource temporarily unavailable
    Failed to mount '/dev/sdb2': Resource temporarily unavailable
    mount: mounting /dev/sdb2 on /root/sdb2 failed: Invalid argument
    

    I’ll see about updating to a newer version of GeexBox. Be back with news when that’s done.

    in reply to: SAMBA Network Share conundrum #11562

    Devlah
    Participant
    
    # opkg update && opkg install ntfs-3g
    Downloading http://download.geexbox.org/binaries/x86_64/latest/packages//Packages.
    Updated list of available packages in /var/lib/opkg//snapshots.
    Package ntfs-3g (2012.1.15-1) installed in root is up to date.
    

    If it wasn’t before, then it should be now. :/

    The results of DMESG: http://pastebin.com/bjEv7tkw

    • This reply was modified 2 years, 6 months ago by  Devlah. Reason: Using Pastebin
    in reply to: SAMBA Network Share conundrum #11560

    Devlah
    Participant

    Thanks for the reply. Here’s what we have:

    
    # cat /proc/mounts
    rootfs / rootfs rw 0 0
    /dev/sda1 / ext4 rw,relatime,data=ordered 0 0
    proc /proc proc rw,nosuid,nodev,noexec,relatime 0 0
    sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
    devtmpfs /dev devtmpfs rw,nosuid,size=1535572k,nr_inodes=383893,mode=755 0 0
    tmpfs /dev/shm tmpfs rw,nosuid,nodev 0 0
    devpts /dev/pts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 0 0
    tmpfs /run tmpfs rw,nosuid,nodev,mode=755 0 0
    tmpfs /sys/fs/cgroup tmpfs rw,nosuid,nodev,noexec,mode=755 0 0
    cgroup /sys/fs/cgroup/systemd cgroup rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd 0 0
    cgroup /sys/fs/cgroup/cpuset cgroup rw,nosuid,nodev,noexec,relatime,cpuset 0 0
    cgroup /sys/fs/cgroup/cpu,cpuacct cgroup rw,nosuid,nodev,noexec,relatime,cpuacct,cpu 0 0
    cgroup /sys/fs/cgroup/devices cgroup rw,nosuid,nodev,noexec,relatime,devices 0 0
    cgroup /sys/fs/cgroup/freezer cgroup rw,nosuid,nodev,noexec,relatime,freezer 0 0
    cgroup /sys/fs/cgroup/blkio cgroup rw,nosuid,nodev,noexec,relatime,blkio 0 0
    mqueue /dev/mqueue mqueue rw,relatime 0 0
    debugfs /sys/kernel/debug debugfs rw,relatime 0 0
    tmpfs /tmp tmpfs rw 0 0
    configfs /sys/kernel/config configfs rw,relatime 0 0
    fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0
    tmpfs /media tmpfs rw,relatime 0 0
    /dev/sda1 /mnt/SATA\040Disk\040#1\040GeeXboX\040(0) ext4 rw,relatime,data=ordered 0 0
    

    And

    
    # df -h
    Filesystem                Size      Used Available Use% Mounted on
    rootfs                  146.5G    878.4M    145.7G   1% /
    /dev/sda1               146.5G    878.4M    145.7G   1% /
    devtmpfs                  1.5G         0      1.5G   0% /dev
    tmpfs                     1.5G         0      1.5G   0% /dev/shm
    tmpfs                     1.5G    202.4M      1.3G  13% /run
    tmpfs                     1.5G         0      1.5G   0% /sys/fs/cgroup
    tmpfs                     1.5G     20.0K      1.5G   0% /tmp
    tmpfs                     1.5G         0      1.5G   0% /media
    /dev/sda1               146.5G    878.4M    145.7G   1% /mnt/SATA Disk #1 GeeXboX (0)
    

    Now curiously, it appears that the 5TB drive is not showing in the list of volumes above, however, when I navigate to /mnt it clearly shows up.

    
    # ls
    SATA_Disk_1_GeeXboX_0         SATA_Disk_2_WabashMedia5TB_0  USB_Disk_2_TOSHIBA_EXT_0      USB_Disk_2_UUI_0
    

    Does this mean I need to manually edit the FSTAB to include the “SATA_Disk_2_WabashMedia5TB_0” ?
    I’m not entirely ignorant of Linux, but I don’t use it enough to be as literate as I could be.

Viewing 12 posts - 1 through 12 (of 12 total)