Jump to content

topscoder

Members
 View Profile  See their activity

  • Posts

    7

  • Joined

  • Last visited

topscoder's Achievements

Noob

Noob (1/14)

0

Reputation

  1. topscoder
    That's a bummer... worked like a charm for a long time. Can you maybe point me in the right direction what I need to do to move to a new machine without losing data? Never looked at alternative hardware, but would appreciate advice
  2. topscoder
    Thanks for your tip. I've spent multiple hours fiddling around and at least got a step further. I've found out adding 'debug' to the append line in syslinux.cfg, the boot process prints some more info. Which is helpful in my case. I added 'root=/dev/sda1' to syslinux.cfg and found out the drive is found and is mounted during boot. [sda] Attached SCSI removable disk VFS: Mounted root (vfat filesystem) readonly on device 8:1. devtmpfs: error mounting -2 rodata_tests: all tests were successful Run /sbin/init as init process with arguments: /sbin/init with environment: HOME=/ TERM=linux BOOT_IMAGE=/bzimage ... same for /etc/init, /bin/init, /bin/sh ... Kernel panic - not syncing: No working init found. Try passing init= option to kernel. See Linux Documentation/admin-guide/init.rst for guidance. At least it tells me it *found* the usb disk. It mounted the device readonly and throws an error 'devtmpfs: error mounting'. To me it's unclear if devtmpfs related directly to failed mounting of the usb disk. 'No working init found'; I've read the documentation at https://www.kernel.org/doc/Documentation/admin-guide/init.rst which makes me believe the issue is either; 1) disk is available in boot process, but root FS cannot be mount (due to partition failure? /dev/sda1 isn't pointing to the right partition maybe?) 2) init binary doesn't exit on rootfs. I've tried to mount / open / inspect and bzcat bzimage, bzroot etc, but couldn't find a hint. 3) Binary cannot be loaded due to either architecture mismatch (i386 cs x86_64) OR maybe the current shipped kernel dropped driver(s) / support for the hardware in my Mac Mini Server??
  3. topscoder
    Thanks for you update. Unfortunately "My Servers" states: "Flash backup unavailable"
  4. topscoder
    I directly tried it using Windows 10 (native). - diskpart - clean - format fat32 - copy backup files to usb stick - run make_bootable.bat as admin (all of the above went ok without errors) Booting... /dev/root: Can't open blockdev VFS: Cannot open root device "sda" or unknown-block(0,0): error -6 Also tried formatting using balenaEtcher (FAT32), but also without luck. 16GB USB Stick isn't a problem is it?
  5. topscoder
    Just tried to create USB stick on Windows (used macOS before). Same issue. Beats me.. anyone with insights or help?
  6. topscoder
    It was either 6.9.2 or 6.10.0/6.10.1. 6.10.1 is the only version I did not verify. Will do it right now. --- 6.10.1 - Same issue. 6.10.0 - Additional error information displayed. scsi 0:0:0:0: Direct-Access Generic Flash Disk 8.01 PQ: 0 ANSI: 6 sd 0:0:0:0: Attached scsi generic sg0 type 0 sd 0:0:0:0: [sda] Attached SCSI removable disk List of all partitions: 0800 61849600 sda driver: sd 0801 61848576 sda1 00000000-01 No filesystem could mount root, tried: squashfs vfat msdos iso9660 fuseblk udf btrfs Kernel panic - not syncing: VFS: Unable to mount root fs on unknown0block(8,0) Still doesn't boot though...
  7. topscoder
    Situation Server ran for a long time without issues. Upgraded Unraid OS to 6.10.3. Rebooted but never came back online again. Booting the server gets stuck at Kernel Panic. /dev/root: Can't open blockdev VCS: Cannot open root device "(null)" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: Kernel panic - not syncing VFS: Unable to mount root rs on unknown-block(0,0) CPU: 3 PID: 1 Comm: swapper/0 Not tainted 5.15.46-Unraid #1 Hardware name: Apple Inc. Macmini5,3/Mac-ZUYXYZDF8234, BIOS MM51.88Z.0080.B00.1804091930 04/09/2018 Call Trace: <TASK> dump_stack_lvl+0x46/0x5a panic+0xf6/0x2a1 mount_block_root+0x1de/0x1ed ? rest_init+0xbb/0xbb prepare_namespace+0x136/0x165 ? rest_init+0xbb/0xbb kernel_init+0x16/0x11 ret_from_fork+0x22/0x30 </TASK> Kernel Offset: disabled --[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) ]-- What I tried I tried several things to find a solution, but without success until now. What I've done so far: - I've created a new Unraid USB stick using a new USB stick. Same issue. - Created new Unraid USB stick using 6.10.2. Same issue. - Created new Unraid USB stick using 6.10.0. Same issue. - Created new Unraid USB stick using 6.9.2. Same issue. - Created new Unraid USB stick using 6.10.3 and copied /bz* files to the errornous USB stick. Same issue. - Added "root=" boot option in syslinux.cfg; -- root=/dev/sda -> Same issue. -- root=/dev/sda1 -> Same issue. -- Tried to add root= boot option at the end of the lines in syslinux.cfg and also at the beginning of the lines (according to syslinux docs). Still same issue. -- Tried another USB port. Same issue. So: - USB Stick died? Guess not. New USB stick also won't boot. - Server hardware/software died? Nothing updated or upgraded. Only Unraid OS on USB. Server runs. It's Unraid that won't boot. - Wrong Unraid OS version? I've tried to downgrade to 6.9.2 without success. Also 6.10.0-6.20.3 without success. - Current kernel can't deal with USB stick (location?). I tried adding root= boot options without success. Well, I guess it's the kernel (config) what bugs here, but I don't know how I'm able to - at least - get my server up and running again. Someone who can help (with ideas)?
×
×
  • Create New...