March 26, 2017 at 09:12 #11578
so you are running 64 bits version.
My mistake ….
indeed, I pointed you the wrong directory
it should be :
src snapshots http://download.geexbox.org/snapshots/geexbox-kodi-x86_64-generic/latest/binaries.x86_64/packages/March 26, 2017 at 09:13 #11579
Now, the problem is not 32 bits arch for sure.
Maybe a kernel problem …March 26, 2017 at 09:19 #11580
CONFIG_EFI_PARTITION=y in kernel’s config
so you should have no problem to access device with partition > 2TB
March 26, 2017 at 09:34 #11582
- This reply was modified 2 months ago by tomlohave.
Well, that seemed to work, as far as doing…stuff….
Here’s what I got though…
I’m guessing I’m going to need to do a manual reboot perhaps…March 26, 2017 at 09:40 #11583
no, it won’t works I’m afraid … too much change, with symbolic links, and busybox seems to be removed.
Reinstall cleanly is the best solution.
I’m googling trying to understand your problem, I’m afraid you have to format your drive using linux tools (and not windows one)March 26, 2017 at 09:43 #11584
Oh well…Fresh install it is.
Incidentally, where would I find the Kernel config?March 26, 2017 at 09:48 #11585March 26, 2017 at 10:00 #11586
Alrighty then. Thanks for all the help.March 26, 2017 at 11:35 #11587
Before erasing everything on your usb hard drive, you can check that the problem is not from our distro.
Just test on a recent linux os like ubuntu (a live cd is sufficient for that) If your drive works then the problem is on our side.
And if it works, please post the result of
Good luckMarch 26, 2017 at 21:31 #11588
Will do.March 27, 2017 at 22:15 #11591
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.March 27, 2017 at 22:56 #11592
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.March 28, 2017 at 06:29 #11593
to be honest, I’ have no so much ideas…
everything should be present to have something working …
maybe I forget something :
can you post, from slitaz the results of
dmesg lsmod cat /proc/filesystems fdisk -l /dev/sdb
and the same from geexbox-3.1 ?
For the devel, need to look why it doesn’t work …
can you explain a little more ?
does the install script works ? ie , did you reboot after the installation and then rootfs wasn’t found ?
@rudi, do you think to something else ?
April 2, 2017 at 11:24 #11597
- This reply was modified 1 month, 4 weeks ago by tomlohave.
Just a little note : I tested x86-64 latest built iso and the installation is ok , using cdrom and internal sda disk. No error while installing nor while rebooting.
You must be logged in to reply to this topic.