--2018-08-16 05:11:16-- https://downloads.linux.hpe.com/repo/spp/rhel/6/x86_64/current/CP017004.scexe
Resolving downloads.linux.hpe.com (downloads.linux.hpe.com)... 184.108.40.206
Connecting to downloads.linux.hpe.com (downloads.linux.hpe.com)|220.127.116.11|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1525561 (1.5........
BootModuleConfig.sh echo host-ind nfcd ........
Just Press F9.
F11 gets you the boot Menu.........
#mount the VCSA DVD
mount /dev/sr0 /mnt/cd
#alternatively you could mount the iso directly
mount -o loop vcsa.iso /your/mount/path
#for this purpose we are using the CLI installer on Linux
#no it's not going to be that easy you can't just run vcsa-deploy like that you need to use a template or configured .json file
Usage: vcsa-deploy [-h] [--version] [--supported-deploymen........
It looks like this has something to do with APIC but I am not sure. I have similar CPUs with a different MB and BIOS that work fine on the same type of kernel. A lot of time the issue is because of the C-step setting in the BIOS.
The same thing happened on the 2.6 kernel with Centos 6 but this is a homebrew 4.4 kernel so I am not sure why it is happening when even Centos 7 (3.2) kernel works OK.
Solution - It comes down to the BIOS set........
Just type the command:
By default it will boot the first local drive "0". I believe you can specify a different number to boot a different device.
(will boot the 4th BIOS device)'........
yum -y install samba
mkdir syslinux;cd syslinux;unzip syslinux-6.03.zip
mkdir -p /tftpboot/libs/
cp bios/com32/modules/linux.c32 /tftpboot/libs/
cp bios/com32/libutil/libutil.c32 /tftpboot/libs/
cp bios/com32/lib/libcom32.c32 /tftpboot/libs/
#add lib path
echo "PATH libs" >> /tftpboot/pxeli........
tftp: client does not accept options
I spent the good portion of a late evening on this double checking settings that I know always worked right for tftp!
This error can also happen if you are trying to boot PXE in UEFI mode. Enter your BIOS and change it to "Legacy PXE" or non-UEFI PXE mode and you'll be good to go!........
Intel NUC J3455 vs Vorke V1 J3160
Both are excellent units but the J3160 is nicer if you require even lower power usage (6W vs the Intel 10W). The price is attractive on the Vorke V1 as well. It's been said that the Intel J3455 NUC has a buggy BIOS and some other issues that require attention.
The Intel J3455 is still nice because it has 2 RAM slots but it does get hotter due to lack of fan.
The Vorke V1 runs cooler, uses less power an........
When running cudaminer once it tries to initialize the card the entire screen freezes. The computer itself is still running but the Xorg is done for, you cannot even switch to another console window and must reboot (even an mdm or Xorg restart does not help).
At first cudaminer will give you these errors:
...retry after 15 seconds
GPU #0: Geforce 210 with compute ca........
1.) Replicate the number of partitions in your new drives.
I created 3 partitions of the same same size.
partition #1: +1G (/boot)
partition #2: +60G (swap)
partition #3: rest of it (/)
#note if you are using GPT/gdisk you need to create separate a partition at least 1MB in size (in my case I would a 4th partition and mark it type ef02).........
Cannot even "Browse Network" when clicking on "Windows Network"
Unable to mount location
Failed to retrieve share list from server: No such file or directory
[2017/02/14 00:16:44.271314, 0] ../source3/nmbd/nmbd.c:58(terminate)
Got SIGTERM: going down...
[2017/02/13 17:35:41.797944, 0] ../lib/util/become_daemon.c:124(daemon_ready)
At first my BIOS said the card may not work right because there is no more option ROM space.
I disabled the Option ROM for both LSI 1068 and 2008 chipsets, Network Boot ROM and most other PCI slots, Serial Port, etc... and the message went away but the card still does not work properly.
But it still cannot initialize the card properly (does not work):
[ 33.943272] NVRM: This PCI I/O region assigned to your NVIDIA device is invalid:........
Download from here http://www.avagotech.com/products/server-storage/host-bus-adapters/sas-9200-8e#downloads
sudo Installer_P20_for_Linux/sas2flash_linux_i686_x86-64_rel/sas2flash -listall
LSI Corporation SAS2 Flash Utility
Version 20.00.00.00 (2014.09.18)
Copyright (c) 2008-2014 LSI Corporation. All rights reserved
I will start by saying I think I know what caused this boot-time error on Linux Mint but should also apply to Debian and Ubuntu.
I changed my BIOS time to several hours in the past to match the current time, but this caused Linux to think there were incorrect filesystem times.
The problem is that it seems when you hit this I am not sure what is happening, it doesn't seem to be doing fsck and hangs without prompting the user.
What I have found is that........
Here is the scenario you or a client have a remote machine that was installed as a standard/default minimal Centos 6.x machine on a single disk with LVM for whatever reason. Often many people do not know how to install it to a RAID array so it is common to have this problem and why reinstall if you don't need to? In some cases on a remote system you can't easily reinstall without physical or KVM access.
So in this case you add a second physical or disk or already ha........
sudo apt-get install zoneminder
[sudo] password for one:
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
libuser-perl python-evince kdebase-apps kwrite unixodbc
libgnomeprint2.2-data python-soappy vgabios python-metacity hddtemp
If you remove the white label on the chip (near the CMOS battery) you will find the following details about it:
SST 49LF080A 33-4C-NHE
It is the PLCC32 type and can be pried and removed safely (but be very careful) with an eye glass flat head screw driver.
If you just have a bad flash you may be able to reprogram your original or just buy another one with the part# above and reprogram it.
This is great news for people who have bricked th........
Phoenix phlash error
Cannot flash when memory managers ( e.g. HIMEM) are present.
press any key to exit.
Use the "/x" option to get past the above
0000:00:00.0 RAM memory: NVIDIA Corporation MCP55 Memory Controller (rev a2)
0000:00:01.0 ISA bridge: NVIDIA Corporation MCP55 LPC Bridge (rev a3)
0000:00:01.1 SMBus: NVIDIA Corporation MCP55 SMBus (rev a3)
0000:00:02.0 USB controller: NVIDIA Corporation MCP55 USB Controller (rev a1)
0000:00:02.1 USB controller: NVIDIA Corporation MCP55 USB Controller (rev a2)
0000:00:05.0 IDE interface: NVIDIA Corporation MCP55 SATA Controller (rev a3)
Dell CS24SC Info
0000:00:00.0 Host bridge: Intel Corporation 5100 Chipset Memory Controller Hub (rev 90)
0000:00:02.0 PCI bridge: Intel Corporation 5100 Chipset PCI Express x8 Port 2-3 (rev 90)
0000:00:03.0 PCI bridge: Intel Corporation 5100 Chipset PCI Express x4 Port 3 (rev 90)
0000:00:04.0 PCI bridge: Intel Corporation 5100 Chipset PCI Express x16 Port 4-7 (rev 90)
0000:00:05.0 PCI bridge: Intel Corporation 5100 Chipset PCI Express x4 Port 5 (rev 90)........
0000:00:00.0 Host bridge: Intel Corporation 5000P Chipset Memory Controller Hub (rev b1)
0000:00:02.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 2-3 (rev b1)
0000:00:03.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4 Port 3 (rev b1)
0000:00:04.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x8 Port 4-5 (rev b1)
0000:00:05.0 PCI bridge: Intel Corporation 5000 Series Chipset PCI Express x4........
I'm not sure why I'm getting these but all memory modules are the exact same and all passed memtest successfully although they are ECC. I've heard that ECC RAM can't be tested as well and the kernel seems to indicate they are non-fatl recoverable errors. I wonder if the BIOS has aggressive RAM timing or maybe the controller or motherboard is bad.
[ 12.716515] EDAC MC: Ver: 2.1.0
[ 12.717771] EDAC MC0: Giving out device to........
Press F2, you wouldn't know this because like most new computers, it doesn't announce the required key unless you enable it from the BIOS.
#count=10000 makes an image of 10000MB make sure your image is at least the same as your existing
dd if=/dev/zero of=yourimage.img bs=1M count=10000
# losetup -fv newimage.raw
# fdisk -cu /dev/loop0
# kpartx -a /dev/loop0
# dd if=<xenimage> of=/dev/mapper/loop0p1
# e2fsck -f /dev/mapper/loop0p1
# resize2fs /dev/mapper/loop0p1
# a lot of guides tell you to edit /etc/fst........
Unusually the Virtualization was enabled when I got this server but all the NICs were diabled in the BIOS including PXE boot!
Advanced -> Advanced Chipset Control
PCI Slot 1 Option ROM: Enabled
Onboard LAN1 Control: Enabled
LAN1 Option ROM Scan: Enabled (you need it for PXE boot)
Onboard LAN2 Control: Enabled
LAN2 Option ROM Scan: Enabled
*you will need to reboot and........
./configure: cannot locate gcc 3.x. please install it or specify with --qemu-cc
yum -y install gcc make
./configure: cannot locate gcc 3.x. please install it or specify with --qemu-cc
yum -y install compat-gcc-*
Error: Could not find alsa
Make sure to have the alsa libs and headers installed.
yum -y install alsa-lib-devel
02:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08)
03:00.0 SCSI storage controller: LSI Logic / Symbios Logic SAS1068E PCI-Express Fusion-MPT SAS (rev 08)
Basically these cards are a stripped-down version of Dell Perc 6/i only they (SAS 6/ir) support JBOD.
The Dell Perc 6/i are basically useless because it doesn't have JBOD support and requires software or BIOS commands to add or remove........
I've got one of these for testing projects from work at home and got more than I bargained for with the time I've spent on it due to the storage handing/Perc 6/i cards.
My particular model came with the following:
2U Rack Mount Server with Rails
2xOpteron 2373 EE (Quad Core, there is a 6-core version that can be found at times)
2 x 250GB Seagate SATA
2 x Dell Perc 6/i (horrible and a nightmare to work........
I bricked one of my cards by following a guide from UNRAID.
Step #1 from them wipes out the BIOS, but guess what? The step where you restore the BIOS should have been done first, which is sas2flash but no version supports or is able to find my Perc 6/i. So now I'm a bit stuck.
I tried using megarec but it's funny that it can wipe the BIOS but can't forcefully reload it:
megarec -writesbr 0 mpt2sas.rom
Supports 1078 control........
One thing to remember is that you need MegaCli to do the flashing.
You also need the correct file, I tried at least 2 different Perc 6 firmwares from Dell that kept getting rejected as corrupt by MegaCli (they were really the wrong version). I have an external PCI-E Dell 6 Perc/I but I chose images from the 'Integrated" on motherboard version as it was all I could find. They are different, and below is my first time finding success.........
I flashed an LSI Logic firmware to it and it broke the BIOS (cannot do Ctrl+R) for booting purposes but allows other functionality to work normally.
I tried downgrading to a Dell firmware for Perc 6i but it won't work, not even with MegaCli
--2013-08-26 12:53:39-- http://downloads.dell.com/FOLDER00416606M/1/SAS-RAID_Firmware_W83M2_LN32_6.3.1-0003_A14.BIN
At first it was configured as a RAID 0, then I deleted the Virtual Disk Group.
I thought both drives would be shown and detected in Linux as sda and sdb but it actually shows nothing.
To make them work you have to hit Ctrl+R before the system boots (when prompted) and create a Virtual Disk Group. In my case I created each one as RAID 0 (with a single drive only) as I just wanted JBOD but there is no such option or default in these Dell Pe........
open /dev/kvm: No such file or directory
failed to initialize KVM: Operation not permitted
[ 96.084502] kvm: disabled by bios
Any of the above means that "Virtualization" is not enabled in your BIOS. Most servers and Desktops (non-mainstream) can do this no problem but leave it off by default. Note that some systems even though the CPU supports it, don't allow enabling of Virtualization for some reason (especially some lap........
I chose this because I heard a lot of stories about scams and that many providers I contacted said they can't unlock the Canadian I717s (one said "my Bell server" is down).
This method worked perfectly on my Bell I717M and should work for all I717 in Canada, I was able to insert a foreign SIM card. This will work abroad too but remember entering CWM mode is different for I717's in other countries (at least the US).
Step 1 - Root + CWM........
I've run into two issues with Lantronix based KVMs on various servers and here's how I solved them (with that said I like these units as they are Java based and OS independent and work very well, unike some other models like Startech).
1.) If you are connected by USB only and you're sure USB support from the BIOS is enabled, you just need to click the following in Lantronix
Interfaces -> Keyboard/Mouse
Check "Force USB Full Speed Mode", this fixed the issu........
[ 12.460014] ata1: SRST failed (errno=-16)
[ 17.626677] ata1: link is slow to respond, please be patient (ready=0)
[ 22.480011] ata1: SRST failed (errno=-16)
[ 27.646681] ata1: link is slow to respond, please be patient (ready=0)
[ 38.106817] ata1.01: failed to IDENTIFY (INIT_DEV_PARAMS failed, err_mask=0x80)
[ 48.266676] ata1: link is slow to respond, please be patient (ready=0)........
The first Hitachi Deskstar 2TB 5K3000 drive I bought arrived DOA for whatever reason (not recognized by the BIOS or OS). Perhaps it was shipping since I bought only 1 hard drive. When I bought 4 through another Vendor, all 4 checked out fine.
I was worried about the RMA process because a lot of people have complained about Hitachi taking weeks to send out their hard drive and almost implied the warranty is useless.
I'm happy to report that my experience was great a........
You'll see the following and the boot process will freeze:
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered (default)
I have struggled with this issue on vari........
NET: Registered protocol family 2
The above is the last thing that I ever saw, I tried pci=routeirq etc.. and it wouldn't work.
The solution is to enable IOAPIC in the VBOX Settings
Just enable "IOAPIC" in the settings for your Centos Guest and you'll find the kernel boots just fine. I wonder if a physical system might stall in this same way if the BIOS has IOAPIC disabled which many people do as a troubleshooting method.
smartctl -a -d ata -T permissive --smart=on /dev/sda
-d ata is usually required for most SATA drives or you get an error.
-T permissive is required if it's the first time you are running SMART on this device (it's not enough just to enable SMART in the BIOS)
--smart=on is also required for the first time........
It always worked fine before but no amount of power unplugging/cycling does any good. I can access one network share and that is one that I've already saved, but it can't see any workgroups.
One silly thing is why is there no option to manually connect to a netbios name or IP?
It seems there is a bug with the firmware and that the SMB client is not working properly. Hopefully it fixes itself at some point.
Between this and the lack of support for embedded s........
I'm not a fan of Asus and won't be buying another because of having to fight Asus over a bogus warranty denial (it's a long story but they only replied about how to RMA my unit weeks later on the EXACT day the warranty expired).
Anyway, it's just a matter of hitting F9 to do this, there's no need to worry about booting from USB or CD (unless of course you want a different OS eg. Windows XP Pro, Vista/7, or a flavor of Linux or Unix). Also remember that you need to fully/properl........
Linux Unix Xorg X Server Intel Extreme i810 Graphics Problem(EE) I810(0): No Video BIOS modes for chosen depth.
(EE) Screen(s) found, but none have a usable configuration.
I have a new Dell PC with one of the latest Intel Extreme Graphics on-board crap. From what I can see any Linux/Unix/FreeBSD versions running XFree86 or Xorg from years ago or the latest version today will have this problem.
It's easily corrected FOR MOST people. Go into your........
The New Chips on the BlockThe New Chips on the Block
By Bruce Gain
Story location: http://www.wired.com/news/infostructure/0,1377,67795,00.html
02:00 AM Jun. 13, 2005 PT
We have embarked upon a new era in x86 PC computing -- so say chip giants AMD and Intel following their launches of dual-core PC processors. So how will dual-core processing change your PC computing experience? Our FAQ should help you decide whether or when you sho........
Basic Port ListingHopefully someone finds this useful or at least interesting.
Name Port Protocol Description
Small services <20 tcp/udp small services
FTP 21 tcp file transfer
SSH 22 tcp login service
TELNET 23 tcp login service
SMTP 25 tcp mail
TIME 37 tcp/udp time synchronization
WINS 42 tcp/udp WINS replication
DNS 53 udp naming service........
I was starting to panic because suddenly my 1TB Seagate SATA drive wasn't working, I thought it was a BIOS issue because it seemed to have happened after I tried overclocking my Desktop too much.
I tried powering down and waiting, but I still couldn't hear the drive spin up at all. I tried a second 1TB hard drive and it wouldn't work either. I checked all power connections again and again until one of the pins in the MOLEX connector popped completely loose.
You can see the problem below, GRUB recognizes my hard drive and sees the partitions but cannot access them. This is from the GRUB boot disc I'm using.
What happened is that I had some power issues causing this system's power to be interrupted several times and basically an on/off on/off situation.
The system won't boot, I just get a flashing cursor and no message or error from GRUB. Obviously the problem is that my MBR seems corrupt or some other issue.
I never saved any of the logs, but basically no matter what OS (Linux) I used, I could not get my 1000GB hard drive to work (Seagate SATA). The BIOS recognizes the drive and fdisk -l shows the hard drive as it should.
The tricky thing is that different OS's will give you different results, but don't be fooled. You can't use these larger drives for long. I was getting all kinds of seek/IO errors and also messages that the port could not be read.........
I tried everything I could think of, and of course even with the NIC enabled in the BIOS nothing was working. The light would flash when you plugin the cable for a second, but that's all.
Due to another issue I'm about to post about (server is not compatible with 1TB/1000Gig Hard Drives), I updated the BIOS. I didn't even know the 100mbit NICs were not working until I decided I should test each NIC one by one.
I noticed that only 1 server out of........