bearcat

Members
  • Content Count

    548
  • Joined

  • Last visited

  • Days Won

    13

bearcat last won the day on January 8

bearcat had the most liked content!

Community Reputation

55 Excellent

3 Followers

About bearcat

  • Rank
    Guru

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Extremlym First thing first: your keyboard is BROKEN, then: your bootloader is installed on your USB bootstick, and has to stay plugged in and be the primary boot device all the time. Second, what hardware are you using? Third, why did you use the old DSM 5.x series, have you tried Jun's bootloader for DSM 6.1 (that would be a "safe" choice).
  2. @blue10 So nothing related to Xpenology at all I take it? (There might actually be other/better places to find help for this, believe it or not ) There are many HW guy's here, that is what I get payed for at work, but might be hard for any of us to do faultfinding for you with so little info. 1 - What's the backstory to this? Was the "setup" working all OK untill suddenly the backlight died? 2 - Have you verified that everything else work as it should, with signal output to the screen? (use the flashlight trick) 3 - How is this all put together, how is the LCD panel connected to the mainboard what interface is beeing used? 4 - From where did you get the info about the 3,3V to enable the LCD? Do you have a datasheet for the panel? 5 - Can you provide good pictures, of both the complete setup, and the "jumper" and the chip with the missing 3,3V. 6 - Do you have 3,3V from your PSU? How far have you traced it? Btw.: tracing signal/powerlines on a multilayer PCB can be a pain in the a*s ...
  3. @Pandadoo Based on the info found from your post, it looks like this might be the way (I might be wrong, as it has happend once or twice before so doublecheck, and if anything breaks, it's on you )
  4. @blue10 The first thing that comes to mind is: Why would you use a "bare" LCD panel connected to your NAS? The next thing, is why not just use the 3,3V you have from your PSU? The chip you are talkning about, is that on tne LCD panel, or on your mainboard? (if you can provide a good picture of it, it might help to identify the chip and find a datashet).
  5. @diqipib Well, that was new info ... from your post, it looked like a fresh install, using that mainboard for the first time with DSM. If it worked with 1.02b and 6.1.x, I would assume that drivers for your SATA controller was one of many "lost" in the newer releases. Doublecheck your controllers ID and driver (with a 1.02b loader and DSM 6.1.x, using a spare HDD if you have it). Then, try to search the "extra drivers" thread, to see if you fin it there. btw: To be honest, I was sure that you needed AHCI support on any SATA controller beeing used
  6. @diqipib It seems like there are many revisions of that mainboard... But, first thing first, have you identified the onboard SATA controller, and verified the ports are set to AHCI ? Edit: Nevermind .. It seems like your MB's chipset does not support AHCI. It has the ICH7 southbridge, not the ICH7R or ICH7M.
  7. @jitesh_88 and @CAExempt I guess you both might have a reading problem I did a quick test right now: On a computer, running Windows 10, version 1909 I downloaded Jun's Loader v1.03b DS3617xs, a file named "synoboot_3617.zip, linked on this page. Using WnRAR 5.70, i extracted the zip file to a new folder. Using OSFMount v1.5 I mounted the resulting file: "synoboot.img" the way shown below: The status window for OSFMount looks now like this: Using windows file explorer, I open the mounted drive (F:) I then navigate into the selected subfolder: Now, lets open the file in an editor: Lets make some changes, and save it as a new file just to make sure it is visable... Next we unmount it from OSFMount and exit the program. We now have a new and edited version of the file: "synoboot.img" that can be written to our USB boot device. So if you dont find the "grub.cfg" go back and read the Tutorials and the FAQ's once more, and then start again Happy Hacking and Happy Weekend
  8. A quick Q: did you manually load the .pat file (if so, what file did you use?) or was it downloaded during setup?
  9. @RangaWal Yes, the N40L has a Gb interface, make sure you have a good cable and that its well connected in both ends. Check the network status on your NAS: And also check any link LED's on your switch, to see if it says 1Gb active, might try another port?
  10. Are those bare-metal or ESXi (like on the one with a "problem")?
  11. @jitesh_88 Let me repeat to you, the same Q as I posted a year ago, and @CAExempt never replied to.. What bootloader (exact name) did you download, and where did you find it?
  12. Both the internal NIC and your Intel supports 1G, so if it has running 100Mb all the time, something "fishy" has been going on. As you found out, cables is the first thing to check. Do you use homemade cables, or verified cables bought from a store? They are plugged all the way in (in both ends) with a nice "click" as they lock in place? Do you still see the link-LED in both ends of the cables? Tried chancging back to the "old" ports on your USG? Using DHCP or static/reserved IP's on the NAS? If DHCP, any clues in the log? Any VLAN in use, or other configs on the USG that might add to the problems?
  13. @IG-88 <insert facepalm as needed> Actually, I did use a calculator but I missed to "insert" a few drives the first run, starting out with 8, and ending with 10 I guess I can blame it on either the eyesurgery I had before X-mas, or growing to old and confused @PrescottX Sorry for the confusion
  14. I did some math 10*8TB in RAID5 = 56TB storage + 8TB protection 10*8TB in RAID6 = 48TB storage + 16TB protection 12*8TB in RAID5 = 72TB storage + 8TB protection 12*8TB in RAID6 = 64TB storage + 16TB protection Does this add up?
  15. What version of ESXi are you using? And how is the drive added/connected to your VM?