Hello, I'm in the way of building a 42.2 server at home on a fiber line. I use a three disk raid mirror on lvm/mdadm it runs for three month without problem. still experimental, not in production. Yesterday I did a zypper up and had lot of updates. Some of them, specially grub and kernel ones didn't went well, some post install problem. "Control C" and zypper up again allowed the update to go to the end. but as could be expected, today I had to do a reboot (for other reasons) and the computer don't reboot. It stops on initial grub greetings and then error reading of first sector of disk 1, go to rescue mode (screen copy): http://dodin.org/owncloud/index.php/s/eUPZpVHG5QyPisn is this a hardware problem? I know pretty well how to test a single disk usual computer but never had to do this on raid. what may I do? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, 17 Mar 2017 09:43:13 +0100
jdd
Hello,
I'm in the way of building a 42.2 server at home on a fiber line.
I use a three disk raid mirror on lvm/mdadm
it runs for three month without problem. still experimental, not in production. Yesterday I did a zypper up and had lot of updates.
Some of them, specially grub and kernel ones didn't went well, some post install problem. "Control C" and zypper up again allowed the update to go to the end.
but as could be expected, today I had to do a reboot (for other reasons) and the computer don't reboot. It stops on initial grub greetings and then
error reading of first sector of disk 1, go to rescue mode (screen copy):
This application requires JavaScript for correct operation.
is this a hardware problem?
I know pretty well how to test a single disk usual computer but never had to do this on raid.
what may I do?
thanks jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Dave Howorth wrote:
On Fri, 17 Mar 2017 09:43:13 +0100, jdd
wrote: error reading of first sector of disk 1, go to rescue mode (screen copy): http://dodin.org/owncloud/index.php/s/eUPZpVHG5QyPisn This application requires JavaScript for correct operation.
Where did you see that? I went to the page, and saw a download link and a direct link box under it. The link pointed to by the download was the same as the direct link. I have scripts *blocked* from that site, so no javascript was required to download the picture. I just tried downloading it w/wget (outside my browser w/no javascript support), and it worked, so am wondering what displayed the message you saw. Looking at the code, I see that it displays an image if you have JS+SVG support (but I didn't see image w/JS disabled). I enabled JS for the site, and, sure enough, it displayed the image that was in the download. Still, w/o javascript it displayed the image download link & button, and no message in the text about needing javascript. Maybe your browser blocked it and displayed the JS-needed message? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 17/03/2017 à 22:57, L A Walsh a écrit :
Looking at the code, I see that it displays an image if (..)
notice that it's only plain owncloud app jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 18 Mar 2017 07:30:46 +0100
jdd
Le 17/03/2017 à 22:57, L A Walsh a écrit :
Looking at the code, I see that it displays an image if (..)
notice that it's only plain owncloud app
jdd
<body id="body-public"> <noscript> <div id="nojavascript"> <div> This application requires JavaScript for correct operation. Please <a href="http://enable-javascript.com/" target="_blank" rel="noreferrer">enable JavaScript</a> and reload the page. </div> </div> </noscript> -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 18/03/2017 à 09:23, Dave Howorth a écrit :
On Sat, 18 Mar 2017 07:30:46 +0100 jdd
wrote: Le 17/03/2017 à 22:57, L A Walsh a écrit :
Looking at the code, I see that it displays an image if (..)
notice that it's only plain owncloud app
jdd
<body id="body-public"> <noscript> <div id="nojavascript"> <div> This application requires JavaScript for correct operation. Please <a href="http://enable-javascript.com/" target="_blank" rel="noreferrer">enable JavaScript</a> and reload the page. </div> </div> </noscript>
javascript is probably one of the older and the less intrusive scripting system (not to be compared with java) looking at images makes it necessary anyway to have lot of things installed jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 18 Mar 2017 09:37:59 +0100
jdd
Le 18/03/2017 à 09:23, Dave Howorth a écrit :
On Sat, 18 Mar 2017 07:30:46 +0100 jdd
wrote: Le 17/03/2017 à 22:57, L A Walsh a écrit :
Looking at the code, I see that it displays an image if (..)
notice that it's only plain owncloud app
jdd
<body id="body-public"> <noscript> <div id="nojavascript"> <div> This application requires JavaScript for correct operation. Please <a href="http://enable-javascript.com/" target="_blank" rel="noreferrer">enable JavaScript</a> and reload the page. </div> </div> </noscript>
javascript is probably one of the older and the less intrusive scripting system (not to be compared with java)
Since its very name is trademarked from Java there was clearly an intent to be compared with Java. (and I understand perfectly well that they are different technologies)
looking at images makes it necessary anyway to have lot of things installed
Yes but that is all code I have deliberately chosen to install on my machine, not some random code that some random domain wants to download and run on my machine. And which is not necessary for the purpose of viewing an image. A simple hyperlink would suffice.
jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 18/03/2017 à 17:08, Dave Howorth a écrit :
On Sat, 18 Mar 2017 09:37:59 +0100 jdd
wrote:
javascript is probably one of the older and the less intrusive scripting system (not to be compared with java)
Since its very name is trademarked from Java there was clearly an intent to be compared with Java. (and I understand perfectly well that they are different technologies)
AFAIK, javascript was created by Netscape (https://en.wikipedia.org/wiki/JavaScript#Beginnings_at_Netscape), way before java existed - it may have changed since there :-)
and run on my machine. And which is not necessary for the purpose of viewing an image. A simple hyperlink would suffice.
it may be necessary to protect the image or allow browsing several images I don't challenge the right you have not to want javascript, but then better download the image jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Sat, 18 Mar 2017 19:06:00 +0100
jdd
Le 18/03/2017 à 17:08, Dave Howorth a écrit :
On Sat, 18 Mar 2017 09:37:59 +0100 jdd
wrote: javascript is probably one of the older and the less intrusive scripting system (not to be compared with java)
Since its very name is trademarked from Java there was clearly an intent to be compared with Java. (and I understand perfectly well that they are different technologies)
AFAIK, javascript was created by Netscape (https://en.wikipedia.org/wiki/JavaScript#Beginnings_at_Netscape), way before java existed - it may have changed since there :-)
https://www.w3.org/community/webed/wiki/A_Short_History_of_JavaScript http://www.oracle.com/technetwork/java/javase/overview/javahistory-index-198... Mocha was created at Netscape in 1995. Java development was started in 1991. Both the naming of the original version and the final popular name and the trademark licence clearly demonstrate which was first.
and run on my machine. And which is not necessary for the purpose of viewing an image. A simple hyperlink would suffice.
it may be necessary to protect the image or allow browsing several images
I'd love to see an example of how it can 'protect' an image. It's obvious that hyperlinks can allow people to browse several images, since that's how the web works!
I don't challenge the right you have not to want javascript, but then better download the image
If the page allowed me to do that, I wouldn't have bothered complaining. But it doesn't, it's designed in such a way that I can't access the download without first hacking around - in my case by disregarding your CSS. Basically at the point where a page requires me to take special action in order to access its content, I just stop and do something else instead. There are far too many things I could do in this world and fighting people who are intent on making my life difficult is not something I bother with unless I have a strong reason. So in this case I didn't look at your image or consider helping you. I only bothered to look (via the CSS hack) afterwards. I have no idea whether I could have contributed to helping you but in this case your choice of posting method meant I didn't even try. I just posted the javascript error as a courtesy to let you know you had that problem. I'm happy to allow Javascript where I need to trust the source - such as my bank - and where they have a good reason for using it - such as session management. I don't enable it simply to browse the web.
jdd
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 18/03/2017 à 20:06, Dave Howorth a écrit :
On Sat, 18 Mar 2017 19:06:00 +0100 jdd
wrote:
https://www.w3.org/community/webed/wiki/A_Short_History_of_JavaScript
http://www.oracle.com/technetwork/java/javase/overview/javahistory-index-198...
Mocha was created at Netscape in 1995. Java development was started in 1991. Both the naming of the original version and the final popular name and the trademark licence clearly demonstrate which was first.
on the link, both claim 1995. I've never seen java apps before long after this date - but of course I learned much with these links, thanks
and run on my machine. And which is not necessary for the purpose of viewing an image. A simple hyperlink would suffice.
it may be necessary to protect the image or allow browsing several images
I'd love to see an example of how it can 'protect' an image.
the link I provide is not to the image. AFAIK it's coded and have to be decoded. hence the javascript (just a guess, if I give you the simingly direct link to the image it asks you a passwd
I don't challenge the right you have not to want javascript, but then better download the image
If the page allowed me to do that, I wouldn't have bothered complaining. But it doesn't, it's designed in such a way that I can't access the download without first hacking around - in my case by disregarding your CSS.
did you succeed in doing so? I tried without success. Just a way to find how strong is the protection :-)
I'm happy to allow Javascript where I need to trust the source - such as my bank - and where they have a good reason for using it - such as session management. I don't enable it simply to browse the web.
you are welcome jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Fri, Mar 17, 2017 at 11:43 AM, jdd
Hello,
I'm in the way of building a 42.2 server at home on a fiber line.
I use a three disk raid mirror on lvm/mdadm
it runs for three month without problem. still experimental, not in production. Yesterday I did a zypper up and had lot of updates.
Some of them, specially grub and kernel ones didn't went well, some post install problem. "Control C" and zypper up again allowed the update to go to the end.
but as could be expected, today I had to do a reboot (for other reasons) and the computer don't reboot. It stops on initial grub greetings and then
error reading of first sector of disk 1, go to rescue mode (screen copy):
http://dodin.org/owncloud/index.php/s/eUPZpVHG5QyPisn
is this a hardware problem?
No necessary. Can you access your system from live media? Are all disks/filesystems intact? In this case the fastest way to fix it is probably to simply reinstall grub. Of course finding root cause could be helpful for the future, but this also requires you to not repair it until enough information is collected. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 17/03/2017 à 14:53, Andrei Borzenkov a écrit :
On Fri, Mar 17, 2017 at 11:43 AM, jdd
wrote:
is this a hardware problem?
No necessary. Can you access your system from live media? Are all disks/filesystems intact? In this case the fastest way to fix it is probably to simply reinstall grub. Of course finding root cause could be helpful for the future, but this also requires you to not repair it until enough information is collected.
yes... my problem is that I'm used to do so on single disk systems (from rescue or grub editor), but don't really know how to do with raid. I just did the same as usual and can access my "lvm-raid-system" disk, but on this disk I have no yast (!) at least not in /bin or /sbin, and /boot/grub2 is empty... well. I'm a bit stuck here. If I don't find a solution in a very short term, I will discard the raid and reinstall with a single disk... I begin to think dealing with raid and lvm was a bad choice, I have to keep it KISS thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
jdd composed on 2017-03-17 15:49 (UTC+0100):
my problem is that I'm used to do so on single disk systems (from rescue or grub editor), but don't really know how to do with raid.
I just did the same as usual and can access my "lvm-raid-system" disk, but on this disk I have no yast (!) at least not in /bin or /sbin, and /boot/grub2 is empty...
well. I'm a bit stuck here. If I don't find a solution in a very short term, I will discard the raid and reinstall with a single disk...
I begin to think dealing with raid and lvm was a bad choice, I have to keep it KISS
Run bootinfoscript: https://github.com/arvidjaar/bootinfoscript https://github.com/arvidjaar/bootinfoscript/archive/master.zip If it's not enough to help you figure out on your own where your bootloader is and what to do, share it and someone here should be able to help. I'm running two-disk RAID1 on this 42.1 system, though without LVM. I use md devices more or less the same as I would use partitions on a single disk. Grub on this multiboot along with TW, 13.2 and 13.1 system is 0.97 installed to several places, among which not to MBR: grub> find /boot/grub/stage1 (hd0,2) (hd0,8) (hd0,9) (hd0,10) (hd0,11) (hd1,2) (hd1,8) (hd1,9) (hd1,10) (hd1,11) # ls -1 /dev/md* /dev/md0 /dev/md1 /dev/md2 /dev/md3 /dev/md4 /dev/md5 /dev/md6 /dev/md7 /dev/md8 /dev/md9 The md devices are comprised of sdX[8-17]. Booting most times here is done from ext2 sda2, where I've installed 13.1's Grub 0.97, and which is never mounted to /boot. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
17.03.2017 17:49, jdd пишет:
Le 17/03/2017 à 14:53, Andrei Borzenkov a écrit :
On Fri, Mar 17, 2017 at 11:43 AM, jdd
wrote: is this a hardware problem?
No necessary. Can you access your system from live media? Are all disks/filesystems intact? In this case the fastest way to fix it is probably to simply reinstall grub. Of course finding root cause could be helpful for the future, but this also requires you to not repair it until enough information is collected.
yes...
my problem is that I'm used to do so on single disk systems (from rescue or grub editor), but don't really know how to do with raid.
I just did the same as usual and can access my "lvm-raid-system" disk, but on this disk I have no yast (!) at least not in /bin or /sbin, and /boot/grub2 is empty...
Are you using btrfs? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 17/03/2017 à 17:41, Andrei Borzenkov a écrit :
Are you using btrfs?
no, only ext4 by the way, thank you for your help, I will have very few time left on the week end and so may not be able to work on this before Monday. Too bad, I had a bounce problem on an other server and had to edit dns zone, and change the light switch of my server room not to work in the dark. when something goes bad, usually other things go bad at the same time. I guess you know that :-(( jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
17.03.2017 19:46, jdd пишет:
Le 17/03/2017 à 17:41, Andrei Borzenkov a écrit :
Are you using btrfs?
no, only ext4
Well, /sbin/yast(2) are links into /usr/sbin, so it is not clear what "no yast" means - no link or dangling link. Running bootinfoscript makes sense irrespectively - it collects some basic informatio that otherwise needs multiple round trips. But if some content of filesystem is lost, this smells like filesystem corruption, in which case restoring from backup is probably the most sensible route anyway. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Le 17/03/2017 à 17:57, Andrei Borzenkov a écrit :
17.03.2017 19:46, jdd пишет:
Le 17/03/2017 à 17:41, Andrei Borzenkov a écrit :
Are you using btrfs?
no, only ext4
Well, /sbin/yast(2) are links into /usr/sbin, so it is not clear what "no yast" means - no link or dangling link.
found the problem. For some unknown reason (may be a typo) the chroot didn't run correctly and I still was in the rescue system now I'm on my disk. running grub2-mkconfig gives lot of errors like lwm... not found, right now yast bootloader seems to run forever on "creating initrd" - no only long time. ended and after the reboot, the server is back in service again http://dodin.me/ (nothing fancy yet :-) so result: grub is very clever, yast also is (writes grub on the three disk, just in case :-)) and the procedure is exactly the same with raid or without (I was afraid to change only one disk and disturb raid) good, thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrei Borzenkov
-
Dave Howorth
-
Felix Miata
-
jdd
-
L A Walsh