Diskless Remote Boot in Linux (DRBL) Activity
Brought to you by:
steven_shiau
Activity for Diskless Remote Boot in Linux (DRBL)
-
Steven Shiau posted a comment on discussion DRBL for RedHat/Mandriva/SuSE
"Can I just drop in a newer version of BusyBox? " -> Absolutely. The busybox version we use in mkpxeinietrd-net is 1.36. The latest one is 1.37. Please let us know if 1.37 works for you or not. If so, we will try to update that in the near future. Thanks.
-
Max Baro posted a comment on discussion DRBL for RedHat/Mandriva/SuSE
Hey Steven. Thanks for the responses so far. I found the root cause of my deployment issue. I see you use BusyBox in the initrd image as the embeded linux for startup. BusyBox has added the vconfig applet to configure VLAN interfaces, but it is not found in the current image I am running. Can I just drop in a newer version of BusyBox? I checked the source for DRBL from this site and did not see this application, is it included in Clonezilla instead?
-
Thank you for the reply. We have been testing with iPXE with no success so far. I believe our base issue is there is not enough support for VLAN tagging in RH8.
-
"When the system pxe boots in clonezilla-se mode, during initrd-pxe.img is it executing the /initrd or /sbin/initrd?" -> It actually runs "/init" in the initrd.img. If you use "unmkinitramfs initrd.img initrd" to extract the files, it's located in "initrd/main/init" As for your 2nd question, actually I have no idea. AFAIK, the dhcp client in the initrd is quite simple. Hence it lacks the feature to deal with VLAN ID. Maybe you can try to give iPXE a try. Just try "iPXE VLAN ID" and maybe you can...
-
2 questions: When the system pxe boots in clonezilla-se mode, during initrd-pxe.img is it executing the /initrd or /sbin/initrd? I found the function 'config_drbl_live_network'. Is this what configures the network when booting in clonezilla-se? I see it does not grab the VLAN ID from DHCP and configures it. My DHCP is set as such: host lpsrv1 { hardware ethernet aa:bb:cc:11:22:33; fixed-address 10.0.0.1; option vlan-id "200"; option host-name "lpsrv1"; }
-
" I got the module 8021q into initrd-pxe by modifying mkpxeinitrd-net, but it does not appear to load." -> How did you do that? Or maybe you can manually edit initrd-pxe.img? e.g., 1. mkdir initrd 2. cd initrd 3. zcat /tftpboot/nbi_img/initrd-pxe.img | sudo cpio -idm 4. Put you 8021q kernel module in the corresponding path in the dir "initrd". E.g., sudo cp /lib/modules/<your-kernel-version>/kernel/net/8021q/8021q.ko ./lib/modules/<same-version>/kernel/net/8021q/ 5. sudo depmod -b . <kernel-version>...
-
" I got the module 8021q into initrd-pxe by modifying mkpxeinitrd-net, but it does not appear to load." -> How did you do that? Or maybe you can manually edit initrd-pxe.img? e.g., 1. mkdir initrd 2. cd initrd 3. zcat /tftpboot/nbi_img/initrd-pxe.img | sudo cpio -idm 4. Put you 8021q kernel module in the corresponding path in the dir "initrd". E.g., sudo cp /lib/modules/<your-kernel-version>/kernel/net/8021q/8021q.ko ./lib/modules/<same-version>/kernel/net/8021q/ 5. sudo depmod -b . <kernel-version>...
-
" I got the module 8021q into initrd-pxe by modifying mkpxeinitrd-net, but it does not appear to load." -> How did you do that? Or maybe you can manually edit initrd-pxe.img? e.g., 1. mkdir initrd 2. cd initrd 3. zcat /tftpboot/nbi_img/initrd-pxe.img | sudo cpio -idm 4. Put you 8021q kernel module in the corresponding path in the dir "initrd". E.g., sudo cp /lib/modules/<your-kernel-version>/kernel/net/8021q/8021q.ko ./lib/modules/<same-version>/kernel/net/8021q/ 5. sudo depmod -b . <kernel-version>...
-
Update, I got the module 8021q into initrd-pxe by modifying mkpxeinitrd-net, but it does not appear to load. How do I run drblsrv-offline to build the PXE kernel and initrd with the 8021q mod loading?
-
Thanks for that. I'm still running into issues getting PXE to work. We have determined the kernel module 8021q is required for VLAN tagging. The module is not being built into the initrd-pxe.. file. I have gone through the scripts starting with 'drblserv-offline' and followed the process through to mkpxeinitrd-net. I added the module name 8021q to /usr/lib/mkpxeinitrd-net/initrd-skel/etc/modules and recompiled. The module is still not getting into initrd. Is there a filter somewhere that limits what...
-
Can you point me towards the script that configures /tftpboot/mbi_img/grub/grub.cfg? -> Check this one: /usr/sbin/gen-grub-efi-nb-menu
-
Hi Steven. We use VLAN tagging in order to connect multiple networks to a single network interface. When the traffic is tagged, meaning the VLAN ID is transmitted in the packet it works like a control, in that the system will not receive packets that are not tagged. We found that the limitation was in the GRUB version in RH8, v2.02 does not support VLAN tagging. Version 2.12 does however and we are attempting to make that work, creating the bootx64.efi PXE file with the 2.12 version. If I can get...
-
Let's focus on this: https://sourceforge.net/p/clonezilla/discussion/Help/thread/545f402676
-
I am not familiar with VLAN tagging. Maybe you can tell me what you normally do so that we can find a solution for you.
-
ericxuo posted a comment on discussion Help
Hi, I think this forum is not the correct one. Let's forget about it. I've posted it again in the Clonezilla/Help forum. Sorry. Xuo.
-
We have tagged vlan configured across the servers in order to trunk multiple vlans over a single interface. The server BIOS is configured with the VLAN ID and the initial DHCP traffic is tagged, the initial boot64.efi file is downloaded, but subsequent connections are not tagged, so no other requests are tagged so the remaining files do not download. I looked through /sbin/drbl-gen-grub-efi-nb but do not see a way to enable vlan tagging. Using clonezilla-5.4.6-drbl1.noarch. Can we enable VLAN tagging...
-
Hi, Currently, when I create a disk image of my server, I get for ex : -rw------- 1 root root 599031765669 juil. 6 08:40 sdi1.ext4-ptcl-img.zst Is it possible (during the image creation), to create smaller files (of 50 or 100GB max each) which, concatenated together, will create the 600GB file as above ? It would be possible to split this big file after the image creation but : 1) it means I'll need 2 times the file size before I remove the original one. 2) before restoring, I'll have to create back...
-
Sometimes the bug is a bug... No reason... Not logical... I knew the frustration... Anyhow, so you mentioned you use RPI and is running Debian Linux. Maybe you can upgrade the samba package to newer version?
-
Russ Kubes posted a comment on discussion Help
I'm back to being puzzled and frustrated with this one. So, I reverted my configuration change to prevent oplocks (to allow them again), in order to ensure I could recreate the problem again. As expected, the problem was readily reproducible. I then tried the mount command that you suggested above, but oddly the problem still occurred. I then tried putting the "oplocks = no" configuration back into the smb.conf file and restarted Samba on the server again. I also unmounted the partimage and remounted...
-
From the manual of mount.cifs: "nolease" Do not request lease/oplock when openning a file on the server. This turns off local caching of IO, byte-range lock and read meta-data operations (see actimeo for more details about metadata caching). Requires SMB2 and above (see vers). Is this the one? Maybe you can mount your CIFS server like the following and do some tests: sudo mount.cifs //server/share /home/partimag -o nolease,username=<username>,password=<password>,vers=3.0</password></username>
-
I feel like I'm getting close on this one. I found this thread https://bugzilla.samba.org/show_bug.cgi?id=15261 It suggests that OpLocks are the potential cause of the leak specifically over 1gbe, or essentially when the source can read faster than the destination can write. Interestingly the default cache size for the "smbd2 credits" (where the excess is cached in RAM before written to disk) is exactly 500MB. And that's the exact size the leak kept growing by. So I do feel that this correlates the...
-
I feel like I'm getting close on this one. I found this thread https://bugzilla.samba.org/show_bug.cgi?id=15261 It suggests that OpLocks are the potential cause of the leak specifically over 1gbe, or essentially when the source can read faster than the destination can write. Interestingly the default cache size for the "smbd2 credits" (where the excess is cached in RAM before written to disk) is exactly 500MB. And that's the exact size the leak kept growing by. So I do feel that this correlates the...
-
I fee like I'm getting close on this one. I found this thread https://bugzilla.samba.org/show_bug.cgi?id=15261 It suggests that OpLocks are the potential cause of the leak specifically over 1gbe, or essentially when the source can read faster than the destination can write. Interestingly the default cache size for the "smbd2 credits" (where the excess is cached in RAM before written to disk) is exactly 500MB. And that's the exact size the leak kept growing by. So I do feel that this correlates the...
-
I couldn't find any related bugs. I did realize that device was actually still on Bullseye. So I reimaged it to Bookworm, but the issue still occurred. I then installed the backport version of Samba, which is the latest 4.22.3. Still the issue persists. It definitely seems like a memory leak that occurs with large files if you're able to sustain high speeds. I wonder if I'm somewhat an edge case by transmitting 1 gbps to a small Raspberry Pi CPU. Meaning i can't say whether 1gbps is the breaking...
-
I couldn't find any related bugs. I did realize that device was actually still on Bullseye. So I reimaged it to Bookworm, but the issue still occurred. I then installed the backport version of Samba, which is the latest 4.22.3. Still the issue persists. It definitely seems like a memory leak that occurs with large files if you're able to sustain high speeds. I wonder if I'm somewhat an edge case by transmitting 1 gbps to an small Raspberry Pi CPU. Meaning i can't say whether 1gbps is the breaking...
-
I couldn't find any related bugs. I did realize that device was actually still on Bullseye. So I reimaged it to Bookworm, but the issue still occurred. I then installed the backport version of Samba, which is the latest 4.22.3. Still the issue persists. It definitely seems like a memory leak thst occurs with large files if you're able to sustain high speeds. I wonder if I'm somewhat an edge case by transmitting 1 gbps to an small Raspberry Pi CPU. Meaning i can't say whether 1gbps is the breaking...
-
OK, got it. Thanks for sharing that. At least you have found a workaround for this. Maybe an updated version of cifs will fix this? Or did you try to find any related bugs?
-
Just posting a final update. I have what I feel is a successful solution to this. As noted in my previous post, there was a suggestion to use the split option. On my first attempt using this, I selected split size of 10240 MB (just around 10GB). Monitoring the receiving device, I see that the smbd process takes about 500MB of RAM for most of the transfer. With that said, once the "current file" is within the last 500MB to be written to disk, the RAM usage of smbd goes up to 1GB. Then once that file...
-
Alan Taylor posted a comment on discussion Help
Thank you for your reply. I will have a dig through the documentation and give it a try. Appreciate your time. Cheers, Alan
-
I looked into NFS and it's not one I'd be interested in setting up. I may give SSH a try again. I may need to see if I want to add a private key to the SquashFS, I sometimes boot from USB and sometimes from PXE. I remember it's slow, but I don't remember how slow. Maybe it's bearable if that's the option that works. I did just replace that NVMe with a 4TB unit. So far doing the restore over Samba has not had any issues. So, I do imagine it had something to do with how fast the writing was occurring....
-
I looked into NFS and it's not one I'd be interested in setting up. I may give SSH a try again. I may need to see if I want to add a private key to the SquashFS, I sometimes boot from USB and sometimes from PXE. I remember it's slow, but I don't remember how slow. Maybe it's bearable if that's the option that works. I did just replace that NVMe with a 4TB unit. So far doing the restore over Samba has not had any issues. So, I do imagine it had something to do with how fast the writing was occurring....
-
I looked into NFS and it's not one I'd be interested in setting up. I may give SSH a try again. I may need to see if I want to add a private key to the SquashFS, I sometimes boot from USB and sometimes from PXE. I remember it's slow, but I don't remember how slow. Maybe it's bearable if that's the option that works. I did just replace that NVMe with a 4TB unit. So far doing the restore over Samba has not had any issues. So, I do imagine it had something to do with how fast the writing was occurring....
-
I have never done this before. What I have done before is to use DHCP server to assign the fixed IP address to the specific MAC address. In your scenario, what need to be done is to pass the IP address in proper syntax from iPXE to the Linux system. Since they are in different stages, and the network configuration can not be passed automatically from early stage (ipxe) to the 2nd stage (GNU/Linux). So now you can try to pass the network configuration to the Linux kernel boot parameters, follow "ip"...
-
I can try to set up NFS and see how it does, if it's not too involved. I did try to use SSH before, but since there is also encyption in transit, it is very CPU intensive on the recieving end, and the transfer speed gets bottlenecked significantly buy the Pi's CPU.
-
OK. BTW, since you are running Debian on your RPi4, have you tried to run ssh server or NFS server? The issue is also reproducible?
-
I should be able to try that during the week at some point. I don't believe the other two devices I have handy have enough storage for the full backup, but as long as it lets me start it I can see if the behavior is the same. Or worst case I can temporarily move the USB drive over to one of the other devices, that shouldn't be too difficult for a short-term test. I was hoping someone else may have already had the same issue and could chime in - but I don't mind doing the additional testing eithe...
-
OK. So is this issue reproducible in different Samba server? Say, a MS Windows with its SAMBA service enabled?
-
Yes, that is the setting I was referring to when I mentioned with and without direct IO enabled. I couldn't remember the exact text of the setting. The behavior is essentially the same for both. With it enabled, it starts at about 13 GB/min, but then slowly tapers off until it gets down to 0 and stops - about 7% or so into the backup of that partition. If I disable that setting, the only difference is it only starts at around 10 GB/min, but then also slowly tapers off until it gets down to 0 GB/min...
-
oh, appears that the 'php' file got truncated; <?php $mac = $_GET['mac']; $pool = range(ip2long('x.211'), ip2long('x.220')); // File for storing leases $lease_file = '/var/www/leases.json'; $leases = file_exists($lease_file) ? json_decode(file_get_contents($lease_file), true) : []; // Assign new if not leased if (!isset($leases[$mac])) { $used_ips = array_values($leases); foreach ($pool as $ip_long) { $ip = long2ip($ip_long); if (!in_array($ip, $used_ips)) { $leases[$mac] = $ip; break; } } file_put_contents($lease_file,...
-
oh, appears that the 'php' file got truncated;
-
Hi there, Thanks for reading. on the back of the drbl and clonezilla integration I would like to accomplish a linux boot using drbl and clonezilla which does not run a 'dhcpdiscover' and instead uses an assigned address from a 'boot.php' embeded script. essentially my client should boot into ipxe, run a php script and then boot 'clonezilla' or 'distro-blah' (I did have the clonezilla menu and such working but fiddled and lost the config) essentially the php script assigned 'ip' should be used to...
-
Mm... Since you are talking about NVMe and RAM, maybe you can try to enter expert mode, and enable "-edio" to enable the direct IO. Not sure if this will ease this issue you encountered or not... Just a quick idea though.
-
I was hesitant to open this thread, since the problem seems to be with Samba - but I'm only having the issue when using Clonezilla, and when backing up my NVME. I have been using 3.2.2-5. I know there is a later version, but also don't see any specific Samba fixes in it. Also, I don't even know if Clonezilla is truly the issue, or if it's more on my remote device. So, I'm mainly looking for some guidance. My network is all gigabit Ethernet. I have a raspberry Pi 4 that has Debian Bookworm installed....
-
P. Bournias posted a comment on discussion DRBL Live
For those of you using Windows who want the ISO. Go to https://drbl.org/download/ Click Stable Releases to take you to https://drbl.org/download/download-sf.php?branch=stable 1. Select CPU architecture: x64 = AMD64 2. Select file type: ISO Then download Go here https://clonezilla.org/liveusb.php#windows-setup choose uEFI - GPT or Legacy MBR boot and follow instructions.
-
Jazz Yao-Tsung Wang posted a comment on discussion Help
The issue seems to be that our PXE phase uses legacy interface naming which makes the interfaces rather unpredictable, You're right. Based our experiment in 2009, it's the initrd-pxe which initialize all network devices (it's also when you see eth0 ... eth5). Your question reminds me that we tried to create eth0:1 for virtualization purpose (xen hypervisor) by modifing the initrd-pxe boot script. If you would like to know the booting steps of DRBL, here is a simplified animation: https://www.slideshare.net/jazzwang/08-06-24-drbl-introduction...
-
Eric posted a comment on discussion Help
The issue seems to be that our PXE phase uses legacy interface naming which makes the interfaces rather unpredictable, and like you said - disconnecting unnecessary ethernet cables can get around it. if you keep them all connected, and film the screen output with a phone or something - you can eventually figure out which interface corresponds to your onboard NIC for PXE booting. Once you figure that out, just go an modify /lib/mkpxeinitrd-net/initrd-skel/etc/netdev.conf and specify that interface....
-
Okay, so going off of my theory: networking seems to be set up during the PXE phase - which uses legacy interface naming, but the OS uses Predictable names. On the DRBL Server, I changed /etc/default/grub as follows: GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0" I made sure to follow up with update-grub and rebooted the DRBL Server. This made my DRBL Server stop recognizing the ethernet interfaces as ens18or ens19, and instead used the legacy interface naming eth0 and eth1 I then ran drblsrv -i...
-
Hey Steven, that was quite helpful, thank you for providing that. I think part of the problem is that networking seems to be set up during the PXE phase which uses legacy interface naming, but the OS uses Predictable names. I modified pxeinitrd/etc/linuxrc.conf by adding this at the end of the file: use_lag="yes" bond_master=bond0 bond_slaves="eth0 eth1 eth2 eth3" bond_mode=4 bond_miimon=100 bond_xmit_hash="layer2+3" Then I modified pxeinitrd/init around line 209 by adding this section: if [ "$use_lag"...
-
Hi Eric, Did you connect all NICs ( 6 NICs * 12 DRBL Client & 1 LAN NIC of DRBL Server ) to the same Network Switch/Hub? Let me try to answer each question in different threads. Q1. Why does the OS request DHCP on all interfaces? I'd like to understand: - Why does this happen after PXE has already configured the network via eth0? Quick answer: PXE only configure 1 NIC at a time. [PXE Phase] If you don't disable the PXE boot option of other 5 NICs, those 5 NICs will try to do DHCP and request PXE...
-
The initrd for your PXE client is actually the file on the server. Here we take this one as an example: /tftpboot/nbi_img/initrd-pxe.6.1.0-25-amd64.img You can unmkinitrd it first: sudo unmkinitramfs /tftpboot/nbi_img/initrd-pxe.6.1.0-25-amd64.img pxeinitrd Then you will have a dir "pxeinitrd" which contains all for the files. Then you can edit the file "pxeinitrd/etc/linuxrc.conf". Once you have done that, you can generate the initrd for your PXE client again: 1. cd pxeinitrd/ 2. find . | cpio --quiet...
-
Seems like modifying /lib/mkpxeinitrd-net/initrd-skel/etc/linuxrc.conf doesn't actually do anything. I had to tweak the settings in /sbin/mknic-dbi and then run drblsrv -i Which worked, finally it was only making 1 attempt to get an IP address per interface. But now I started getting a fatal error message immediately after attempting to get DHCP on eth0, it wasn't even trying the other interfaces. Then I remembered - back in the /lib/mkpxeinitrd-net/initrd-skel/linuxrc-or-init file where I tried...
-
I tried to modify /lib/mkpxeinitrd-net/initrd-skel/etc/linuxrc.conf # retry max times for udhcp in one ethernet port # iretry_max="5" iretry_max="1" # The time out to wait for NIC to be linked. Unit: 0.1 sec # link_detect_timeout="70" link_detect_timeout="10" I re-ran drblpush -i... then tried to boot the client. But that didn't seem to have any effect. - it still tries 5 times for each interface, and each attempt is no faster than it was previously... I changed /lib/mkpxeinitrd-net/initrd-skel/etc/netdev.conf...
-
I tried to modify /lib/mkpxeinitrd-net/initrd-skel/etc/linuxrc.conf # retry max times for udhcp in one ethernet port # iretry_max="5" iretry_max="1" # The time out to wait for NIC to be linked. Unit: 0.1 sec # link_detect_timeout="70" link_detect_timeout="10" I re-ran drblpush -i... then tried to boot the client. But that didn't seem to have any effect. - it still tries 5 times for each interface, and each attempt is no faster than it was previously... I changed /lib/mkpxeinitrd-net/initrd-skel/etc/netdev.conf...
-
Oversimplified setup DRBL Server = Ubuntu (22.04) VM WAN IP - 10.0.0.30/16 DRBL IP - 10.10.0.30/16 DRBL Clients (x12) = HP Z220 SFF (Each client has 6 NICs total) 1 NIC - onboard 1 NIC - PCI 33/32 card 4 NICs - PCIe 2.0 x1 card 1. Why does the OS request DHCP on all interfaces? PXE boot itself works fine: the client gets a DHCP lease on eth0, downloads the kernel, and starts booting the OS. 12 Client Nodes: 10.10.0.101 - 10.10.0.112 However, during the OS boot phase, the system seems to reinitialize...
-
OK, great. Thanks for your confirmation. We will move that to stable branch recently. Steven
-
Duplicated post. Let's focus on this: https://sourceforge.net/p/drbl/discussion/Help/thread/7fc749be08/ Steven
-
Could you please give unstable DRBL a try? Please let us know the results. Thanks. Steven
-
Simon Brahmst modified a comment on discussion DRBL for Debian/Ubuntu/B2D
EDIT: Reinstalled a couple of times and now it works. No clue why it didn't before but who cares. Hi Steven, first of all the Setup: I am running Ubuntu 22.04 Desktop in a virtual machine in a Proxmox VE. I am currently trying to setup DRBL for Clonezilla (drbl live won't do) and after configuring everything according to the guide until the step of doing "drblpush -i" I get the error "too many levels of symbolic links" everytime it tries to run "chmod /tftpboot/node_root /usr/sbin/update-rc.d" (no...
-
EDIT: Reinstalled a couple of times and now it works. No clue why it didn't before but who cares. Hi Steven, first of all the Setup: I am running Ubuntu 22.04 Desktop in a virtual machine in a Proxmox VE. I am currently trying to setup DRBL for Clonezilla (drbl live won't do) and after configuring everything according to the guide until the step of doing "drblpush -i" I get the error "too many levels of symbolic links" everytime it tries to run "chmod /tftpboot/node_root /usr/sbin/update-rc.d" (no...
-
Oxmel modified a comment on discussion DRBL for Debian/Ubuntu/B2D
I can confirm that DRBL unstable works fine on Ubuntu 24.04 with kernel 6.8.0-49-generic. The bug on DRBL stable seems easily reproducible as it appears right after lauching 'drblsrv -i'. I've attached a bug report with the exact error message in case it can help. By the way, DRBL stable (5.3.2) runs without issue on Debian 12 using kernel 6.1.0-28-amd64.
-
I can confirm that DRBL unstable works fine on Ubuntu 24.04 with kernel 6.8.0-49-generic. The bug on DRBL stable seems easily reproducible as it appears right after lauching 'drblsrv -i'. I've attached a bug report with the exact error message in case it can help. By the way, drbl stable runs without issue on Debian 12 using kernel 6.1.0-28-amd64.
-
Hi Steven, first of all the Setup: I am running Ubuntu 22.04 Desktop in a virtual machine in a Proxmox VE. I am currently trying to setup DRBL for Clonezilla (drbl live won't do) and after configuring everything according to the guide until the step of doing "drblpush -i" I get the error "too many levels of symbolic links" everytime it tries to run "chmod /tftpboot/node_root /usr/sbin/update-rc.d" (no matter the arguments after that). One thing I should add is that I manually had to recreate the...
-
Hi Steven, first of all the Setup: I am running Ubuntu 22.04 Desktop in a virtual machine in a Proxmox VE. I am currently trying to setup DRBL for Clonezilla (drbl live won't do) and after configuring everything according to the guide until the step of doing "drblpush -i" I get the error "too many levels of symbolic links" everytime it tries to run "chmod /tftpboot/node_root /usr/sbin/update-rc.d" (no matter the arguments after that). One thing I should add is that I manually had to recreate the...
-
Please give unstable DRBL a try. Please let us know the results. Thanks. Steven
-
Raphaël posted a comment on discussion DRBL for Debian/Ubuntu/B2D
Same problem here with Linux Mint 22 (6.8.0-49-generic)... :(
-
DHCP service is stochastic, i.e., its client will pick up the IP address stochastically in a LAN. You have an existing DHCP service, and DRBL server will start another one. That's the problem. Maye you can try to assign the tftp server in your primary DHCP server by setting the "next- server" option if it's ISC DHCP service. You can check the manual for dhcpd.conf. Steven
-
Joly Xavier posted a comment on discussion DRBL for Debian/Ubuntu/B2D
Bonjour, J'ai effectué un autre test j'ai 2 cartes reseaux sur le serveur, une carte qui est relié en lacp dans un vlan (.....99.X) et l'autre dans un autre lacp (Vlan ....90.X). J'ai desactiver le dhcp sur le vlan 90 et activer le dhcp sur le serveur drbl et ca fonctionne !!!! Donc quel serait la cause du probleme si j'active mon dhcp dans mon firewall et que je desactive celui du drbl? Je comprends pas tres bien ou ca pourrais venir tout n sachant que je recois bien une ip mais qu'il arrive pas...
-
The easiest way is you disable the existing, original DHCP server. If you can not, you have to replace the ISC dhcp server in DRBL server and tftp server with dnsmasq service. I suggest you check the Clonezilla lite server. After starting it, you can check /etc/dnsmasq.conf. Steven
-
Bonjour, merci pour votre réponse, je n'ai pas 2serveur dhcp sur ce réseau, mais il y en a deja un fonctionnel. Du coup les ordi recoivent bien une adresse ip mais n'arrive pas a recevoir le fichier du serveur pxe (tftp) car je sais pas quel fichier declarer, savez vous me dire quel fichier du serveur tftp je dois renseigner pour que les ordis boot? merci Hello, thank you for your answer, I do not have 2 dhcp servers on this network, but there is already a functional one. So the computers receive...
-
For PXE booting, there is only one DHCP server can exist in a LAN. You can use relay function of DHCP to do that. Do not put 2 DHCP servers in a LAN. Or you can try Clonezilla lite server: https://clonezilla.org//fine-print-live-doc.php?path=clonezilla-live/doc/11_lite_server By default it can use the existing DHCP server. Actually it uses the relay features mentioned previously. Steven
-
Bonjour, J'ai mis un fichier en annexe pour vous expliquer notre soucis. On a essayer le serveur sur une machine local et tout fonctionne tres bien. On essaie de l'améliorer en Vm sur un serveur Synology (voir schéma) On a pas activer le serveur dhcp sur debian drbl car on a deja un serveur dhcp dans le vlan, par contre on a fixer une plage dans le dhcp qui corresponds à la plage du fichier de config. Le pc dans un vlan 2 recoit bien une ip (dans le dhcp du vlan et dans le bon range du fichier de...
-
Bonjour, J'ai mis un fichier en annexe pour vous expliquer notre soucis. On a essayer le serveur sur une machine local et tout fonctionne tres bien. On essaie de l'améliorer en Vm sur un serveur Synology (voir schéma) On a pas activer le serveur dhcp sur debian drbl car on a deja un serveur dhcp dans le vlan, par contre on a fixer une plage dans le dhcp qui corresponds à la plage du fichier de config. Le pc dans un vlan 2 recoit bien une ip (dans le dhcp du vlan et dans le bon range du fichier de...
-
Jaime posted a comment on discussion DRBL for Debian/Ubuntu/B2D
Hi. I'm trying to install DRBL on Ubuntu server 24.04 but something is wrong when generating the tftpboot filesystem. I followed all the steps in the installation manual, which work perfectly on Ubuntu server 22.04: -Add DRBL key (ok, no errors) -Add deb repository http://free.nchc.org.tw/drbl-core drbl stable (ok, no errors) -drblsrv -i (ok, no errors) -drblpush -i (generates errors, attached console output) The first error of the drblpush -i command is: Running: chroot /tftpboot/node_root /usr/sbin/update-rc.d...
-
Not sure. Did you check the log files, e.g., /var/log/syslong? Maybe you can find some clues. BTW, if what you need DRBL is for Clonezilla massive deployment function, you can also try this mode: https://clonezilla.org//clonezilla-SE/use_clonezilla_live_in_drbl.php i.e., use Clonezilla live as the client's OS when deploying. In addition, you can also use Clonezilla lite server: https://clonezilla.org///fine-print-live-doc.php?path=clonezilla-live/doc/11_lite_server Steven
-
Edwin posted a comment on discussion DRBL for Debian/Ubuntu/B2D
i have executed all commands successfully in clonezilla server i have reached the last step for my image to deploy to my client computers i keep getting stuck on this page. what do i do?
-
ponge posted a comment on discussion DRBL for Debian/Ubuntu/B2D
received thank you
-
You still can find the archived files here: http://free.nchc.org.tw/drbl-live/testing/ Actually due to some technical issues, we do not create newer DRBL live. It's recommended to use Clonezilla lite server if you need Clonezilla server functions. For more info, please check: https://clonezilla.org//fine-print-live-doc.php?path=clonezilla-live/doc/11_lite_server Steven
-
hello to the address : https://sourceforge.net/projects/drbl/files/drbl_live_testing/ I can't find version 2.6.2-1 for amd64 iso do you have the link for this architecture? thanks
-
hello to the address : https://sourceforge.net/projects/drbl/files/drbl_live_testing/ I can't find version 2.6.2-1 for amd64 do you have the link for this architecture? thanks
-
Santi posted a comment on discussion DRBL for Debian/Ubuntu/B2D
Hi Steven, thank you very much for your reply. Now the USB to ethernet adapter works. There is a small problem that is that when the image finishes restoring then I choose the restart option but the computer does not restart, it stays blocked with the black screen and the cursor, I have to hold down the power button until the computer turns off . If instead of choosing to restart I choose to turn off, it has the same result. Comment that during the drblpush -i configuration I choose the option "Use...
-
If you use DRBL is for Clonezilla SE purpose, I suggest you can try this mode: https://clonezilla.org//clonezilla-SE/use_clonezilla_live_in_drbl.php In addition, give different versions of Clonezilla live a try, e.g., the latest testing one, 20240625-oracular: https://clonezilla.org/downloads.php Steven
-
Good afternoon, I am using drbl installed on an Ubuntu 22.04 server, so far I have had no problems. I have a batch of HP 840 G8 laptops, these laptops do not have a ethernet card so I use a USB to ethernet adapter. The problem is that when I start from the USB it starts to load, it is automatically assigned an IP but it stays frozen in "mounting /proc filesystem". I have tried 2 adapters, one adapter with RTL8153 chipset and another with RTL8156 but the result is the same in both. Attachment screenshot....
-
Basically what you are doing is correct. However, there is the command from Clonezilla "create-ocs-tmp-img" you can try, it will save disk space. Please run "create-ocs-tmp-img -h" to know how to do it. Steven
-
Good afternoon Alexis, If you deploy an image with a SATA interface, you cannot restore that same image on a PC with an NVME interface, even if the source PC and the destination PC are the same model. What I do is implement two images of the same PC model, one image with a SATA interface and the other image with an NVME interface. This is what I do, any other solution?
-
Next time you can refer to this FAQ: https://drbl.org/fine-print.php?path=./faq/2_System/26_resize.faq#26_resize.faq Since you have finished the cloning, you can use GParted live to resize the partition: https://gparted.org/download.php Steven
-
Bo Frazer posted a comment on discussion Help
relative noob here, used the goof-proof default menu option. I simply wanted to go ssd for better speed, and went for 1T instead of my old 500M. Eventually the Clonezilla seemed to work well, but Winderz is still showing 500M as my drive size. Any ideas?
-
" Will it be possible to use USB type-C Ethernet Network Adapter on an ultra-flat notebook that does not have a LAN port to be able to clone with Clenezilla server?" -> It should work if the Linux kernel supports that. Or you can actually boot Clonezilla live on that machine to deploy the image for the image repository. Steven
-
Alexis Ozuna modified a comment on discussion DRBL for Debian/Ubuntu/B2D
Greetings… I don't remember if I tried clonezilla live (usb), for image deployment, I remember that I had a problem and I was forced to do a two-server project with debian 11.1 with DRBL / Clonezilla server, I explain that I work in a company where Windows is installed On new or refurbished computers, everything works great, but SATA interface, now I have this problem with NVMe SSDs. I only have to do the installation of Debian 11.9 again, perhaps it has compatibility, but the strangest thing is...
-
Greetings… I don't remember if I tried clonezilla live (usb), for image deployment, I remember that I had a problem and I was forced to do a two-server project with debian 11.1 with DRBL / Clonezilla server, I explain that I work in a company where Windows is installed On new or refurbished computers, everything works great, but SATA interface, now I have this problem with NVMe SSDs. I only have to do the installation of Debian 11.9 again, perhaps it has compatibility, but the strangest thing is...
-
It seems the Linux kernel from Debian 11 does not support your hardware (NVMe SSD). Have you tried Clonezilla live? e.g., 3.1.2-20 or 20240327-noble? https://clonezilla.org/downloads.php If it works for you, and you can try this mode: https://clonezilla.org/clonezilla-SE/use_clonezilla_live_in_drbl.php Actually it's recommended to use Clonezilla lite server: https://clonezilla.org//fine-print-live-doc.php?path=clonezilla-live/doc/11_lite_server Steven
-
Greetings to everyone..., I don't speak English, please I need your help, I have Debian 11 installed as a server without a graphical environment with DRBL Server / Clonezilla in local mode, it does not have an internet connection, for Windows operating system image deployment. The error is that I cannot clone or restore image on NVNe SSD. The server is configured to clone in legacy mode, I have no problem with mechanical hard drives, Sata SSDs and m2 SSDs. Sata, I have no problem restoring image...
-
Greetings to everyone..., I don't speak English, please I need your help, I have Debian 11 installed as a server without a graphical environment with DRBL Server / Clonezilla in local mode, it does not have an internet connection, for Windows operating system image deployment. The error is that I cannot clone or restore image on NVNe SSD. The server is configured to clone in legacy mode, I have no problem with mechanical hard drives, Sata SSDs and m2 SSDs. Sata, I have no problem restoring image...
-
Missing support for en_US.UTF-8 locale despite defaulting to it
-
Thanks for your patch. It's applied in the git repository. We will use it in the next release. Steven
-
Francy2007 posted a comment on discussion Help
Ok, thank you very much. Best regards. Vincent
-
Anton Samsonov created ticket #24
Missing support for en_US.UTF-8 locale despite defaulting to it
-
If you clone your dual boot systems to an external disk, remember to remove the original source disk if you want to boot from your external disk. Put two identical OSes or file systems on a same machine will confuse your OS, and it might damage its booting mechanism. Steven
-
Aguero Pablo Daniel posted a comment on discussion DRBL for Debian/Ubuntu/B2D
Hi, I found a solution by using "mount.exfat-fuse" instead of "mount -t exfat". By using FUSE I had no problem to perform saves or restores. https://packages.debian.org/buster/exfat-fuse Thank you. Pablo.
1 >