Wayne_Emter Posted September 25, 2018 Posted September 25, 2018 I will start off by saying I know nothing about Linux. I went to up grade to 6.6. It downloaded and did it's thing then said to reboot, so I pushed the reboot button and it said it was rebooting. I waited and tried to log to Tower and it wouldn't, so I tried going to 10.0.0.191 and it wouldn't. I waited a while longer and still no luck. So I cycled the power and it still wouldn't come up. I put a Monitor on the server and rebooted. A bunch of text scrolled by ending with: floppy0: no floppy controlers found VFS: cannot open root devise "(null)" or unknown-block(0,0): error -6 Please append a correct "root=" boot option; here are the available partitions: 0800 7816704 sda driver: sd 0801 7814144 sda1 00000000-01 Kernal panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0) CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.8-unraid #1 Hardware name: Gigabyte Technology Co., Ltd. To be filled by O.E.M./F2A88X-D3HP, BIOS F2 12/24/2015 Call Trace: dump_stack+0x5d/0x79 panic+0xe5/0x224 mount_block_root+0x278/0x29c ? do_early_param+0x89/0x89 prepare_namespace+0x12b/0x161 kernal_init+0x5/0xf5 ret_from_fork+0x22/0x40 Kernal Offset: disabled ---[ end Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-blo ck(0,0) }--- On the flash drive under logs, the most recent file is dated Feb 18, 2018. Is there a way to refresh the flash drive without losing the files on the array and recover my license information? Any help would be greatly appreciated. Quote
stealth12 Posted September 25, 2018 Posted September 25, 2018 Same issue on both mine and a friends server. Quote
trurl Posted September 25, 2018 Posted September 25, 2018 The previous version should be on your flash in the previous folder. Just move its contents to the top folder of flash and reboot. Quote
limetech Posted September 26, 2018 Posted September 26, 2018 If @trurl's suggestion doesn't work, there could be something corrupted on the USB boot flash. Suggest these steps: Plug flash into PC and make a backup: create a folder somewhere, eg, desktop, open flash device, select everything there and drag to the folder. Use the USB Flash Creator tool to reformat/reinstall 6.6.0 to your flash device. From your backup, drag 'config' folder to your newly prepared flash device, replacing the 'config' folder created there. Eject flash and boot server. Quote
Wayne_Emter Posted September 26, 2018 Author Posted September 26, 2018 Using the contents of the previous folder, I was able to get the server back up and running on 6.5.3. Thank you! I've got a lot going on in the next week or two, so I will wait to try to upgrade to 6.6. So if I use the flash creator tool to install 6.6 on my flash drive, copying the config folder will keep all my shares and licensing info? If that's the case I will definitely keep current backups. Thanks again for the help. Quote
JorgeB Posted September 26, 2018 Posted September 26, 2018 3 minutes ago, Wayne_Emter said: So if I use the flash creator tool to install 6.6 on my flash drive, copying the config folder will keep all my shares and licensing info? Correct. Quote
trurl Posted September 26, 2018 Posted September 26, 2018 You can download a zipped backup of flash at anytime from Main - Boot Device - Flash - Flash Backup. Quote
rymalco Posted January 9, 2019 Posted January 9, 2019 I'm having the same issue as OP. Trying to upgrade from 6.5.3 to 6.6.6. Followed Admin's suggested 4 steps Quote Plug flash into PC and make a backup: create a folder somewhere, eg, desktop, open flash device, select everything there and drag to the folder. Use the USB Flash Creator tool to reformat/reinstall 6.6.0 to your flash device. From your backup, drag 'config' folder to your newly prepared flash device, replacing the 'config' folder created there. Eject flash and boot server. No dice. Tried installing 6.6.6 on several other USB drives same issue. Fresh install of 6.5.3 on same USB drives works fine. I suppose there is an issue with 6.6.6... Quote
trurl Posted January 9, 2019 Posted January 9, 2019 39 minutes ago, rymalco said: No dice. Have you tried another USB port on your server? Preferably USB2. Quote
rymalco Posted January 9, 2019 Posted January 9, 2019 (edited) 27 minutes ago, trurl said: Have you tried another USB port on your server? Preferably USB2. Thanks for replying trurl! I'm rocking a GA - MA74GMT - S2 board so only USB2 available 😕 Edited January 9, 2019 by rymalco typo/spelling Quote
Wayne_Emter Posted January 9, 2019 Author Posted January 9, 2019 On my system, I had 7 files on my flash drive named FSCK0000.REC, FSCK0001.REC, etc. which I believe were corrupt files and also when I ran the ram test on bootup I had an error. So, I replaced the flash drive and replaced the ram and now everything is working great. Quote
JorgeB Posted January 9, 2019 Posted January 9, 2019 2 hours ago, rymalco said: Tried installing 6.6.6 on several other USB drives same issue. Fresh install of 6.5.3 on same USB drives works fine. I suppose there is an issue with 6.6.6... Try this, it worked for me for an identical error, on the flash drive edit syslinux/syslinux.cfg and add root=sda to the boot option you're using after initrd=/bzroot, e.g.: label Unraid OS menu default kernel /bzimage append initrd=/bzroot root=sda 1 1 Quote
limetech Posted January 9, 2019 Posted January 9, 2019 15 minutes ago, johnnie.black said: Try this, it worked for me for an identical error, on the flash drive edit syslinux/syslinux.cfg and add root=sda to the boot option you're using after initrd=/bzroot, e.g.: label Unraid OS menu default kernel /bzimage append initrd=/bzroot root=sda I don't see how that works at all - there is no 'root' device in Unraid. What is /dev/sda referring to after you boot? OP: you could also try UEFI boot. Quote
JorgeB Posted January 9, 2019 Posted January 9, 2019 Just now, limetech said: I don't see how that works at all - there is no 'root' device in Unraid. What is /dev/sda referring to after you boot? Don't ask me how it works, I can only tell you that it worked for me on a netbook that without that wouldn't boot any release after 6.4 Quote
rymalco Posted January 10, 2019 Posted January 10, 2019 34 minutes ago, johnnie.black said: Don't ask me how it works, I can only tell you that it worked for me on a netbook that without that wouldn't boot any release after 6.4 Well...it worked for me too! 😮 Version 6.6.6 now up and running. Thanks to all of you for your input, much appreciated. What a great community! Quote
limetech Posted January 10, 2019 Posted January 10, 2019 2 hours ago, rymalco said: Well...it worked for me too! 😮 Version 6.6.6 now up and running. Thanks to all of you for your input, much appreciated. What a great community! Please post diagnostics.zip Tools/Diagnostics I'd like to see what's going on, probably it's going to be, "ahh right, that's what's happening"... thx Quote
rymalco Posted January 10, 2019 Posted January 10, 2019 (edited) On 1/10/2019 at 3:38 PM, limetech said: Please post diagnostics.zip Tools/Diagnostics I'd like to see what's going on, probably it's going to be, "ahh right, that's what's happening"... thx Here you you. Edited June 5, 2024 by rymalco Quote
limetech Posted January 10, 2019 Posted January 10, 2019 13 minutes ago, rymalco said: Here you you. tower-diagnostics-20190109-1845.zip Thank you. One more request? Please post output of this command: cat /proc/mounts Quote
rymalco Posted January 10, 2019 Posted January 10, 2019 4 minutes ago, limetech said: Thank you. One more request? Please post output of this command: cat /proc/mounts rootfs / rootfs rw 0 0 proc /proc proc rw,relatime 0 0 sysfs /sys sysfs rw,relatime 0 0 tmpfs /run tmpfs rw,nosuid,nodev,noexec,relatime,size=32768k,mode=755 0 0 devtmpfs /dev devtmpfs rw,relatime,size=458304k,nr_inodes=114576,mode=755 0 0 devpts /dev/pts devpts rw,relatime,gid=5,mode=620,ptmxmode=000 0 0 tmpfs /dev/shm tmpfs rw,relatime 0 0 fusectl /sys/fs/fuse/connections fusectl rw,relatime 0 0 cgroup_root /sys/fs/cgroup tmpfs rw,relatime,size=8192k,mode=755 0 0 cpuset /sys/fs/cgroup/cpuset cgroup rw,relatime,cpuset 0 0 cpu /sys/fs/cgroup/cpu cgroup rw,relatime,cpu 0 0 cpuacct /sys/fs/cgroup/cpuacct cgroup rw,relatime,cpuacct 0 0 blkio /sys/fs/cgroup/blkio cgroup rw,relatime,blkio 0 0 memory /sys/fs/cgroup/memory cgroup rw,relatime,memory 0 0 devices /sys/fs/cgroup/devices cgroup rw,relatime,devices 0 0 freezer /sys/fs/cgroup/freezer cgroup rw,relatime,freezer 0 0 net_cls /sys/fs/cgroup/net_cls cgroup rw,relatime,net_cls 0 0 perf_event /sys/fs/cgroup/perf_event cgroup rw,relatime,perf_event 0 0 pids /sys/fs/cgroup/pids cgroup rw,relatime,pids 0 0 tmpfs /var/log tmpfs rw,relatime,size=131072k,mode=755 0 0 /dev/sda1 /boot vfat rw,noatime,nodiratime,fmask=0000,dmask=0000,allow_utime=0022,codepage=437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro 0 0 /dev/loop0 /lib/modules squashfs ro,relatime 0 0 /dev/loop1 /lib/firmware squashfs ro,relatime 0 0 rootfs /mnt rootfs rw 0 0 /dev/md1 /mnt/disk1 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0 /dev/md2 /mnt/disk2 reiserfs rw,noatime,nodiratime,user_xattr,acl 0 0 shfs /mnt/user fuse.shfs rw,nosuid,nodev,noatime,user_id=0,group_id=0,allow_other 0 0 /dev/loop2 /var/lib/docker btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 /dev/loop3 /etc/libvirt btrfs rw,relatime,space_cache,subvolid=5,subvol=/ 0 0 Quote
limetech Posted January 10, 2019 Posted January 10, 2019 Well that look a-ok. How about output of: cat /boot/syslinux/syslinux.cfg Quote
rymalco Posted January 10, 2019 Posted January 10, 2019 1 minute ago, limetech said: Well that look a-ok. How about output of: cat /boot/syslinux/syslinux.cfg default menu.c32 menu title Lime Technology, Inc. prompt 0 timeout 50 label Unraid OS menu default kernel /bzimage append initrd=/bzroot root=sda label Unraid OS GUI Mode kernel /bzimage append initrd=/bzroot,/bzroot-gui label Unraid OS Safe Mode (no plugins, no GUI) kernel /bzimage append initrd=/bzroot unraidsafemode label Unraid OS GUI Safe Mode (no plugins) kernel /bzimage append initrd=/bzroot,/bzroot-gui unraidsafemode label Memtest86+ kernel /memtest Quote
limetech Posted January 10, 2019 Posted January 10, 2019 Thanks for the debugging help. I can't explain why this works at this time. If the issue gets reported more often we'll have to dive into kernel source to see what's going on. It appears you have only 1GB RAM, that's right at the minimum we recommend. Probably related to this. Quote
JorgeB Posted January 10, 2019 Posted January 10, 2019 It appears you have only 1GB RAM, that's right at the minimum we recommend. Probably related to this. The netbook I had the same problem also had little RAM, just can't be certain now if it was 1 or 2GB, but most likely only 1GB also. Quote
trurl Posted January 10, 2019 Posted January 10, 2019 8 hours ago, limetech said: It appears you have only 1GB RAM Interesting. 1G RAM, no cache, no parity, but apparently running dockers. @rymalco What dockers do you run? Quote
rymalco Posted January 10, 2019 Posted January 10, 2019 14 hours ago, limetech said: Thanks for the debugging help. I can't explain why this works at this time. If the issue gets reported more often we'll have to dive into kernel source to see what's going on. It appears you have only 1GB RAM, that's right at the minimum we recommend. Probably related to this. No problem - appreciate you looking into this. 6 hours ago, trurl said: Interesting. 1G RAM, no cache, no parity, but apparently running dockers. @rymalco What dockers do you run? All the debug info from a fresh install of 6.6.6 - explains invalid parity. Cache not assigned, and not running dockers - it would be challenging with the RAM limitations! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.