New on LowEndTalk? Please Register and read our Community Rules.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.
Comments
de-dus2
Can't you install windows in the 200GB disk and leave the 10GB to local disk D? And the 10GB disk seems to be SSDs (@UltraVPS can you confirm?) or at least super fast disk arrays. My apt upgrades were as fast as most SSD providers, so I thought that was a plus side, compared to other storage providers
my setup is this .
Filesystem Size Used Avail Use% Mounted on
udev 3.9G 0 3.9G 0% /dev
tmpfs 798M 648K 798M 1% /run
/dev/vda1 7.3G 1.7G 5.6G 24% /
tmpfs 3.9G 0 3.9G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 3.9G 0 3.9G 0% /sys/fs/cgroup
/dev/vda15 105M 3.4M 102M 4% /boot/efi
/dev/vdb 196G 61M 186G 1% /mnt
tmpfs 798M 0 798M 0% /run/user/0
total 217G 1.8G 205G 1% -
will try and get vdb as home.. just not used to this type of setup and yes mainly a windows and mac user although i have setup a few linux systems with no problems so far
As I said above, the reason why vda1 shows 7.3G is because there's a swap partition. (And I see that there's also a /boot partition vda15.) What does
swapon -s
say?Resisted for so long.. Gave in in the end. It was indeed futile.
Thanks for the deal!
This is whats showing.
Filename Type Size Used Priority
/dev/vda2 partition 1996796 0 -2
So that's basically 2G for swap.
Somehow I doubt that this will work, at least not straightforwardly.
Back in December, when I set up NetBSD on my VPS, I tried to use the second (big) disk (vdb) as / and first (small) disk (vda) as a local disk, but NetBSD didn't want to boot from vdb. Admittedly, I didn't spend much effort on this, because using vda as the system disk was fine with me.
Linux is generally more flexible in this respect, so one could probably use vdb as / .
Basically i want to use the second disk as my home.
once i work out how to do that i will be fine.
guess i need some reading..
If someone knows of a walk through on how to do this i would appreciate it.
thanks
What I did was use their netinstall under boot image where u can install over VNC. Set the partitions as u like it. it's just not one click like others.
umount /mnt
fdisk /dev/vdb
g
w
fdisk /dev/vdb
n
w
mkfs.ext4 /dev/vdb1
nano /etc/fstab
/dev/vdb1 /home ext4 defaults 0 1
mount -a
reboot
simples.....
Yeah, this is basically it. Note that it's advisable to create a partition on vdb -- as shown by these instructions -- because there isn't a partition there by default.
this seems to depend on the OS you go with. I chose debian 8 and there the 200G disk has been partitioned by default with ext4 on top and mounted to /data
so it only is a think of unmounting, adjusting /etc/fstab and mounting again...
PS @magnoman if you need help fixing this, just PM me, drop me a tenner via paypal and I'll get it done for you.
I see. My experience was with the image for Ubuntu 16.04.
Thanks guys for the advice will try later other wise i will definately be in touch falzo.
Can I install an OS from a custom ISO?
@magnoman
I did boot into debian 9 netinstall and installed lvm vda as root/swap, vdb as home. Its very easy and there are tons of tutorials online. Just beware you will need to manually setup ipv6 coz the system dont detect them.
How can I install windows? I tried to use whatuptime image but i got Broken pipe error
No Los Angeles, Los Angeles is very friendly to me.
No, if you order a server with SAS storage, both virtual disks are SAS based.
You use linux
Fantastic worked perfectly and i have gained some more experience with linux.
Thanks Osaris and the rest of you that gave advice much appreciated.
You're most welcome @magnoman .
Great box you have from @UltraVPS - enjoy learning on it
will this work with ubuntu 18.04?
Yes.
it should - but really better if you know enough about the essential commands involved to recognize them as fundamental utilities on any linux (and other unixish) system.
Be prepared to do some work to learn about
fdisk
andmkfs
andmount
(etc) ...The first two especially are easy ways to mess up a working system if (for example) one specifies the wrong drive or partition. Maybe not such a big deal to screw something up when installing a fresh system - but in general "measure twice, cut once" when using these commands.
Also should note that the non-standard setup used in these default templates (that is, not using partition /dev/vda1 but rather the whole disk /dev/vda) presents some opportunity for confusion even for experienced users, so be aware of that possibility.
EDIT2:
tangential, but generally relevant to the UltraVPS dual-drive experience ...
installing Debian 9 from ISO onto 2nd (larger) drive didn't seem to want to boot directly (and I didn't bother to jump into grub to make it) so I reinstalled onto the 10 GB /dev/vda
Then - sure enough - just clicking through the easy LVM setup on the Debian installer had left me with 8 GB swap on that 10 GB drive, leaving a bit less than 2 GB for the root filesystem.
Fortunately resizing the swap "partition" setup in LVM is relatively painless.
The above is just setting an arbitrary variable ("swapname") to avoid typing and typos
(Maybe not the most straightforward way - just how I ended up doing it ... Worked for this specific setup, YMMV)
Still need to resize the root filesystem to use the other 7 GB now available - but actually want to keep it "small" for the time being since I'm planning to setup a ramdisk filesystem and try running the OS from there. (Lest my setup remain too simple to be sufficiently entertaining.)
Yes that is what i was using in this situation
nl-ams1
At first, unfortunately, the IPv4 address was blacklisted by SORBS since 2017.
So I asked UltraVPS to allocate new IPv4 address, they said the primary IP address can't be changed but they requested delisting.
About 90 minutes after that, I confirmed the IPv4 address is delisted from SORBS.
We wouldn't want that.
This confirms my experience with NetBSD, which I mentioned earlier in this thread.
Yeah, playing with Grub could probably make Debian boot from vdb, but then there's a potential issue of an update breaking the setup. Best to go with vda, which is what is intended.